3 Replies Latest reply on Jan 22, 2009 9:33 AM by karluqs

DeploymentDescriptor not setted on IntegrationControl after

karluqs Jan 22, 2009 8:20 AM

Hi,

I deployed a BPEL process on jBPM. This process has an invoke node to a WS then an wait node and after that another invoke. Everything was working fine, i tested a few times. So for crash recovery test, i shutdown jboss when reached the wait node. After the restart, i waited for the process to continue. It restarted ok but an error ocurred when the second invoke WS was reached.

java.lang.NullPointerException
org.jbpm.bpel.integration.jms.IntegrationControl.getPartnerCatalog(IntegrationControl.java:293)
org.jbpm.bpel.integration.jms.IntegrationControl.createCaller(IntegrationControl.java:261)
org.jbpm.bpel.integration.jms.JmsIntegrationService.invoke(JmsIntegrationService.java:162)
org.jbpm.bpel.integration.def.InvokeAction.execute(InvokeAction.java:75)
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

I put a debug on it, so i discovered the following, the property deploymentDescriptor (org.jbpm.bpel.integration.server.DeploymentDescriptor) was not setted on org.jbpm.bpel.integration.jms.IntegrationControl. This property is only setted on org.jbpm.bpel.integration.server.IntegrationConfigurator.contextInitialized(... that it's called when the process is deployed.

When i restart JBoss all my process already deployed can't call WS because the IntegrationControl related to the process don't receive the deploymentDescriptor object on JmsIntegrationServiceFactory.getIntegrationControl(

And another problem, since this deploymentDescriptor is only read from the current deployed process, the old version from the same process will fail after a JBoss restart, because the deployment file don't exist anywhere.

This is a bug, right?

Anybody has a workround for this?

Thanks,

1. Re: DeploymentDescriptor not setted on IntegrationControl af

dhanushgopinath Jan 22, 2009 8:34 AM (in response to karluqs)
Carlos,

As a workaround You may try setting the deployment descriptor again on the integration control after checking if it has a deployment descriptor. Like this may be
IntegrationControl integControl = factory .getIntegrationControl(bpelProcDef); // Create DeploymentDescriptor instance DeploymentDescriptor deployDesc = new DeploymentDescriptor(); // Create InputSource InputSource is = new InputSource(deploymentDescriptorContent input stream ); // Read the deployment descriptor into the deployDesc object DeploymentDescriptorReader reader = new DeploymentDescriptorReader(); reader.read(deployDesc, is); integControl.setDeploymentDescriptor(deployDesc);

Hope this helps. I faced this issue (integration control not holding deploy descriptor) in a different way, a code like this help it fix.
Actions
2. Re: DeploymentDescriptor not setted on IntegrationControl af

karluqs Jan 22, 2009 9:32 AM (in response to karluqs)

Thanks Danush!
Actions
3. Re: DeploymentDescriptor not setted on IntegrationControl af

karluqs Jan 22, 2009 9:33 AM (in response to karluqs)

"karluqs" wrote:
Thanks Danush!

Thanks Dhanush!, not Danush =D
Actions

Go to original post