[jBPM Development] - JBPM MultipleHuman Task..Task server restart not propagate the flow to next human task
by Deepraj Sawalkar
Deepraj Sawalkar [https://community.jboss.org/people/deepraj] created the discussion
"JBPM MultipleHuman Task..Task server restart not propagate the flow to next human task"
To view the discussion, visit: https://community.jboss.org/message/819826#819826
--------------------------------------------------------------
I have created one multiple human task in JBPM 5. The first human Task is "Financial Accounting Approval Task" having ActorId "#{finApprover}" and the second one is "Manger Approval Task" having ActorId "#{manager}".
When I run the MibBpmServiceProvider.java it successfully run the process and Task is shiowing as pending to FinancialApprover. Then complete the task then it is shiowing as pending to Manager. Then Manager can complete the task. It goes fine in this scenario.
Now the problem occours
1. I run the MibBpmServiceProvider.java it successfully run the process and Task is shiowing as pending to FinancialApprover.
2. *Now I stop the server which means stops the MinaTaskServer*.
3. Now I start the Task server again.
4. Check from Human Task View Editor there I found it is pending to FinancialApprover.
5. Start the task -> Complete the task for FinancialApprover.
6. Now Task is not in queue for FinancialApprover. *When I check the same task for Manager then I am not finding that task in Manager queue.*
*The issue occurs only when the task is pending to first human task and then stop the task server and start the task server and trying to exceute the first human task not propagate the flow to the next human task.*
**
I am attaching the bpmn file along with the bpmn image and java class. Can you please help me to sort out this issue.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/819826#819826]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 8 months
[JBoss Web Services Development] - WS-Adresssing not working in Jboss-5 webservice client
by Arun Kumar
Arun Kumar [https://community.jboss.org/people/arun.m] created the discussion
"WS-Adresssing not working in Jboss-5 webservice client"
To view the discussion, visit: https://community.jboss.org/message/832161#832161
--------------------------------------------------------------
Am using java webservice client. I ran the below code as a main program and it is working fine
VASWCF vas = new VASWCF();
System.out.println(" Trying to get contract ") ;
IRequestUnifiedVASContract contract = vas
.getWSHttpBindingIRequestUnifiedVASContract(new AddressingFeature(true,true));
System.out.println(" Trying to send SOAP request ") ;
contract.notify(inputXml, null);
System.out.println(" SOAP message sent successfully ");
But when i run the same code in Jboss-5, exceptions are occuring
2013-08-09 19:09:35,264 WARN [org.jboss.ws.tools.wsdl.WSDL11Reader] (http-127.0.0.1-8080-1) UsingAddressing extensibility element not supported yet.
2013-08-09 19:09:35,317 INFO [STDOUT] (http-127.0.0.1-8080-1) Trying to get VAS contract
2013-08-09 19:09:35,581 INFO [STDOUT] (http-127.0.0.1-8080-1) Trying to send SOAP request
2013-08-09 19:09:35,797 ERROR [org.jboss.ws.core.CommonClient] (http-127.0.0.1-8080-1) Exception caught while (preparing for) performing the invocation:
javax.xml.ws.soap.SOAPFaultException: The message with To '' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree.
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
at org.jboss.ws.core.jaxws.binding.SOAP12BindingJAXWS.throwFaultException(SOAP12BindingJAXWS.java:115)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy276.notify(Unknown Source)
at com.arun.sartest.LogTestMbean.kickStartSMS(LogTestMbean.java:57)
at com.arun.sartest.LogTestMbean.getLogValue(LogTestMbean.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
When the same code runs as main program, it works fine. Wondering how it is not working in jboss-5 . *I suspect that Jboss's JAXWS jar files are causing this*. If so how to avoid that and make Jboss-5 use Java's classpath ?
Please help me on this
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/832161#832161]
Start a new discussion in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 8 months