Petals BC SOAP

Provide SAs are corrupted at Petals restart

Details

  • Type: Bug Bug
  • Status: Inaccurate Inaccurate
  • Resolution: Incomplete
  • Affects Version/s: 4.1
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When Petals is restarted with BC-SOAP + a "provide" SA deployed, the following error occurs (whatever the status of the web service imported: started or not): see stack trace below.

    If I remove and reinstall the SA, it works fine (like at 1st deployment).

    [Petals.JBI-Management.SystemRecoveryServiceImpl]-SEVERE 2011-01-21 15:35:33,694 org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide
    Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide'
    Its state changes to UNKNOWN
    Please check the repository consistency
    java.util.concurrent.ExecutionException: org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide
    Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide'
    Its state changes to UNKNOWN
    Please check the repository consistency
    at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:233)
    at java.util.concurrent.FutureTask.get(FutureTask.java:94)
    at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllServiceAssembly(SystemRecoveryServiceImpl.java:364)
    at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllEntities(SystemRecoveryServiceImpl.java:177)
    at org.objectweb.fractal.julia.generated.C290d4ec8_0.recoverAllEntities(INTERCEPTOR[SystemRecoveryService])
    at org.objectweb.fractal.julia.generated.Ca30db3f3_0.recoverAllEntities(INTERFACE[SystemRecoveryService])
    at org.ow2.petals.kernel.server.PetalsServerImpl.recoverSystem(PetalsServerImpl.java:590)
    at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:186)
    at org.ow2.petals.launcher.AbstractLauncher.start(AbstractLauncher.java:190)
    at org.ow2.petals.launcher.AbstractLauncher.launch(AbstractLauncher.java:147)
    at org.ow2.petals.distribution.platform.Main.main(Main.java:42)
    Caused by: org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide
    Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide'
    Its state changes to UNKNOWN
    Please check the repository consistency
    at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:320)
    at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:1)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
    at java.util.concurrent.FutureTask.run(FutureTask.java:149)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
    at java.util.concurrent.FutureTask.run(FutureTask.java:149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
    at java.lang.Thread.run(Thread.java:736)

    Show
    When Petals is restarted with BC-SOAP + a "provide" SA deployed, the following error occurs (whatever the status of the web service imported: started or not): see stack trace below. If I remove and reinstall the SA, it works fine (like at 1st deployment). [Petals.JBI-Management.SystemRecoveryServiceImpl]-SEVERE 2011-01-21 15:35:33,694 org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide' Its state changes to UNKNOWN Please check the repository consistency java.util.concurrent.ExecutionException: org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide' Its state changes to UNKNOWN Please check the repository consistency at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:233) at java.util.concurrent.FutureTask.get(FutureTask.java:94) at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllServiceAssembly(SystemRecoveryServiceImpl.java:364) at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl.recoverAllEntities(SystemRecoveryServiceImpl.java:177) at org.objectweb.fractal.julia.generated.C290d4ec8_0.recoverAllEntities(INTERCEPTOR[SystemRecoveryService]) at org.objectweb.fractal.julia.generated.Ca30db3f3_0.recoverAllEntities(INTERFACE[SystemRecoveryService]) at org.ow2.petals.kernel.server.PetalsServerImpl.recoverSystem(PetalsServerImpl.java:590) at org.ow2.petals.kernel.server.PetalsServerImpl.start(PetalsServerImpl.java:186) at org.ow2.petals.launcher.AbstractLauncher.start(AbstractLauncher.java:190) at org.ow2.petals.launcher.AbstractLauncher.launch(AbstractLauncher.java:147) at org.ow2.petals.distribution.platform.Main.main(Main.java:42) Caused by: org.ow2.petals.jbi.management.ManagementException: A service assembly consistency is corrupted: sa-SOAP-HelloWorldService-provide Caused by: JBI descriptor entry was not found in repository for JBI artefact 'sa-SOAP-HelloWorldService-provide' Its state changes to UNKNOWN Please check the repository consistency at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:320) at org.ow2.petals.jbi.management.recovery.SystemRecoveryServiceImpl$2.call(SystemRecoveryServiceImpl.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:736)
  • Environment:
    BC-SOAP 4.1-SNAPSHOT (compiled from trunk). Petals 3.1.1, Linux Ubuntu.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
noddoux added a comment - Mon, 24 Jan 2011 - 13:26:24 +0100 - edited

Was there a problem when Petals ESB stopped ? For example, cf PETALSBCSOAP-67.
Does the problem occur at each restart of Petals ?

Show
noddoux added a comment - Mon, 24 Jan 2011 - 13:26:24 +0100 - edited Was there a problem when Petals ESB stopped ? For example, cf PETALSBCSOAP-67. Does the problem occur at each restart of Petals ?
Hide
Permalink
Pierre-Yves Gibello added a comment - Mon, 24 Jan 2011 - 14:50:45 +0100

No problem at Petals stop, and problem occurs at each petals startup (I have to undeploy then redeploy the sa).

Show
Pierre-Yves Gibello added a comment - Mon, 24 Jan 2011 - 14:50:45 +0100 No problem at Petals stop, and problem occurs at each petals startup (I have to undeploy then redeploy the sa).
Hide
Permalink
Pierre-Yves Gibello added a comment - Wed, 26 Jan 2011 - 11:32:14 +0100

Well, the problem seemed to be related to an inconsistent state of Petals: I could reproduce it... without any SA deployed (sic).
I then shutdown Petals, removed repository/system-state.xml, repository/lost+found/, and work/ .
The issue seems to be solved. But... Petals can get to inconsistent state, then produce errors on redeployment of (properly working !) deployed SA at startup.
Redeployment of the "corrupt" SA solves the problem temporarily... the definitive solution being to cleanup/reinstall everything by hand !
This does not seem to be related to the BC-SOAP component, at least I'm not sure.

Show
Pierre-Yves Gibello added a comment - Wed, 26 Jan 2011 - 11:32:14 +0100 Well, the problem seemed to be related to an inconsistent state of Petals: I could reproduce it... without any SA deployed (sic). I then shutdown Petals, removed repository/system-state.xml, repository/lost+found/, and work/ . The issue seems to be solved. But... Petals can get to inconsistent state, then produce errors on redeployment of (properly working !) deployed SA at startup. Redeployment of the "corrupt" SA solves the problem temporarily... the definitive solution being to cleanup/reinstall everything by hand ! This does not seem to be related to the BC-SOAP component, at least I'm not sure.

People

Dates

  • Created:
    Fri, 21 Jan 2011 - 15:41:49 +0100
    Updated:
    Wed, 26 Jan 2011 - 11:32:14 +0100
    Resolved:
    Mon, 24 Jan 2011 - 13:26:24 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.