[jBPM] - Subprocess transition in a fork is not working
by Felix Jose
Felix Jose [http://community.jboss.org/people/FelixKJose] created the discussion
"Subprocess transition in a fork is not working"
To view the discussion, visit: http://community.jboss.org/message/546097#546097
--------------------------------------------------------------
Hi All,
I am having a main JBPM process(helloworld.jpdl.xml) and in that having a fork of that one transition to a sub process and the other to a state node. And these to should transition to a join join1 node. When I started the process it sucessfully reaching the fork and both two transitions are reached. But As the subprocess contains a state node "*printHelloWorld*" the execution will wait in that. And meanwhile as the other transition node in the fork is a state node (*Being1*) it also wait in that node.
*snippet of Main process(helloworld.jpdl.xml)*
<fork g="101,278,80,40" name="printHelloWorld">
<transition g="56,193:-39,-18" name="Being1" to="Being1"/>
<transition g="137,177:24,8" name="review" to="review"/>
</fork>
<join g="855,204,80,40" name="join1">
<transition to="printHelloWorld2"/>
</join>
<state name="Being1" g="0,0,80,40">
<transition to="join1" g="877,666:"/>-*-------Other execution is active at this node. Waiting for an external signal*
</state>
<sub-process name="review" sub-process-key="SubProc" g="0,0,80,40">
<transition to="join1" g="877,666:"/>
</sub-process>
*subporcess (SubPoc.jpdl.xml)*
<process name="SubProc" xmlns=" http://jbpm.org/4.3/jpdl http://jbpm.org/4.3/jpdl">
<start g="372,19,80,40">
<transition to="printHelloWorld"/>
</start>
<state name="printHelloWorld" g="0,0,80,40">------*Subprocess execution is waiting in This node. Waiting for an external signal.*
<transition name="printHelloWorld1" to="printHelloWorld1" g="877,666:"/>
</state>
<java g="539,206,138,40" method="printHelloWorld" name="printHelloWorld1">
<transition g="606,516:-39,-18" name="theEnd" to="theEnd"/>
</java>
<end g="369,491,80,40" name="theEnd"/>
</process>
I have used *processInstance.getExecutions()* which gives the active executions and the result is:
*[execution[helloWorld.13.Being1], execution[helloWorld.13.review]]*
Then by using *openExecutio.getSubProcessInstance().getId();* I find out the subprocess instance id and is *[SubProc.21].*
Then I signaled the subprocess using *executionService.signalExecutionById(id,"printHelloWorld1");* And it sucessfully transitioned and it prints :
*<---------------->*
* HELLO FELIX!*
*<---------------->*
So the subprocess sucessfully *completed*. But when I check activeactivity name in the subprcess it still shows *printHelloWorld state node (*by using *openExecutio.getSubProcessInstance().findActiveActivityNames()---o/p is --[printHelloWorld])*
And also when I checked active executions using *processInstance.getExecutions() it still gives:*
*[execution[helloWorld.13.Being1], execution[helloWorld.13.review]]* that means both two forked transitions are in *wait* state.
So my doubt is how can I transition the subprocess fron one state to another instead of using *executionService.signalExecutionById(id,"printHelloWorld1");?*
I have attached the sample application with this. Can you please give a solution as soon as possible?
*Thank You and Regards,*
*Felix K Jose*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546097#546097]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 1 month
[JBoss Microcontainer] - "Duplicate" deployment exception logging detracts from JBoss AS usability
by Lincoln Baxter III
Lincoln Baxter III [http://community.jboss.org/people/lincolnthree] created the discussion
""Duplicate" deployment exception logging detracts from JBoss AS usability"
To view the discussion, visit: http://community.jboss.org/message/546092#546092
--------------------------------------------------------------
When using JBoss AS (6 M{X} in this case) - deployment errors can be critical for debugging botched configurations in web-applications. In fact, looking through the stack trace the only way to find out what's wrong, and why your app isn't deploying.
That's fine. The problem comes when the exception message is duplicated or even hidden by numerous exceptions that pile up in the log, effectively turning the next minute or so into a duck hunt, weeding through exceptions until you find the one line that you're really looking for.
I think JBoss AS/MC should be more selective when displaying exceptions.
For example: http://pastebin.com/NjjXLuiF http://pastebin.com/NjjXLuiF - In this case, I don't even want to see an exception. I've simply got a Servlet that can't be resolved to a class, and all really I care about is:
`
DEPLOYMENTS IN ERROR: Deployment "vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/" is in error due to the following reason(s): java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@1e05df6d `
It would be even nicer if I were told that I had a bad Servlet definition in web.xml, but instead, I get all of this... which isn't really helpful to an end-user. (Granted, in this case all of the exceptions actually contain the same root cause, but in some cases that doesn't happen - I certainly don't want duplicate exceptions.)
I'd like to open a JIRA for this. It's relatively low-hanging fruit that could help smoothe the developer experience.
`11:56:14,884 INFO org.jboss.web.tomcat.service.deployers.TomcatDeployment org.jboss.web.tomcat.service.deployers.TomcatDeployment undeploy, ctxPath=/pretty-blog
11:56:17,425 ERROR org.jboss.kernel.plugins.dependency.AbstractKernelController org.jboss.kernel.plugins.dependency.AbstractKernelController Error installing to PreReal: name=vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/ state=PostClassLoader mode=Manual requiredState=PreReal: org.jboss.deployers.spi.DeploymentException: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@5b20a97e
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:112)
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.internalDeploy(ResteasyScannerDeployer.java:57)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:918)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:633)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@5b20a97e
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:498)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:108)
... 28 more
11:56:17,430 WARN org.jboss.system.server.profileservice.hotdeploy.HDScanner org.jboss.system.server.profileservice.hotdeploy.HDScanner Failed to process changes: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/ -> org.jboss.deployers.spi.DeploymentException: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@5b20a97e
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/" is in error due to the following reason(s): java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@5b20a97e
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1198)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1144)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:848)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
11:56:18,504 SEVERE javax.enterprise.resource.webcontainer.jsf.config javax.enterprise.resource.webcontainer.jsf.config Unable to access url jndi:/localhost/pretty-blog/WEB-INF/faces-config.xml. Monitoring for this resource will no longer occur.
11:56:44,856 ERROR org.jboss.kernel.plugins.dependency.AbstractKernelController org.jboss.kernel.plugins.dependency.AbstractKernelController Error installing to PreReal: name=vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/ state=PostClassLoader mode=Manual requiredState=PreReal: org.jboss.deployers.spi.DeploymentException: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@1e05df6d
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:112)
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.internalDeploy(ResteasyScannerDeployer.java:57)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1660)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1378)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1319)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:378)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2029)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1050)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1289)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1213)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1107)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:918)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:633)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:898)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:677)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@1e05df6d
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:498)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:108)
... 28 more
11:56:44,861 WARN org.jboss.system.server.profileservice.hotdeploy.HDScanner org.jboss.system.server.profileservice.hotdeploy.HDScanner Failed to process changes: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/ -> org.jboss.deployers.spi.DeploymentException: java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@1e05df6d
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/Users/lbaxter/dev/jboss-6/server/default/deploy/pretty-blog.war/" is in error due to the following reason(s): java.lang.ClassNotFoundException: com.sun.FooServlet from BaseClassLoader@1e05df6d
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1198)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1144)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:848)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)`
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546092#546092]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 1 month
Re: [jboss-user] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Flavia Rainone
Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] replied to the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/546078#546078
--------------------------------------------------------------
> Ales Justin wrote:
>
> Why the rush? :-)
> If you ask me, I would do it lazily aka on_demand.
>
> Scanning the whole common/lib is gonna be slow,
> and imo, people should not be using libs to deploy Weld components -- simply put them in deploy/.
>
> Or why would you do it upfront?
I've been thinking about correctness all this time. If somebody places a jar in lib and expects that the beans are created upfront when AS starts, then this would not work using your approach.
Thinking about performance, though, I think that we should trade that by better performance, i.e., we should use the suggested lazy approach.
And I don't see any useful scenario where somebody would want to have a bean deployed to lib dir loaded at startup, specially if no other bean deployed in deploy dir has a dependency towards it.
Pete, does the lazy approach fullfills the Weld prerequisites regarding lib jars?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546078#546078]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 1 month
Re: [jboss-user] [jBPM] - JBPM Scalability and support
by Tej jbpm
Tej jbpm [http://community.jboss.org/people/tejJBPM] replied to the discussion
"JBPM Scalability and support"
To view the discussion, visit: http://community.jboss.org/message/546073#546073
--------------------------------------------------------------
Oh..I am getting very concerned where I stand now. We have used JBPM 4.2. I cant move back to JBPM 3 for the reason that I need html support in emails and few other features which were released in 4.2.. Without any deadline for JBPM 5 , I feel like standing on a wall.......
I am surpised to know that they withdrew the support.......My client is quite specific he needs to understand the knitty gritty of how it will be supported in future........if jbpm 5 is so different from jbpm 4 i am goin to be stormed with the problem of rewriting the whole thing in 5!!
Anybody else, any other better suggestions........one of the question I was asked is what happens if JBoss withdrew its support - that seems to be kind of happening now !!!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546073#546073]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 1 month
Re: [jboss-user] [JBoss Remoting] - Need help in configuring JMS with JBoss Messaging in JBoss 4.2.3
by Prabhu Natarajan
Prabhu Natarajan [http://community.jboss.org/people/prabhun] replied to the discussion
"Need help in configuring JMS with JBoss Messaging in JBoss 4.2.3"
To view the discussion, visit: http://community.jboss.org/message/546070#546070
--------------------------------------------------------------
Hi Ron,
Sorry, I was busy chasing for the ports to get opened from service personnel.
I could get the following ports opened for testing from my system (Bangalore) to JBoss server (UK) as there is a Firewall
4457 - serverBindPort
14000 - secondaryBindPort
14001 - secondaryConnectPort
However I got the same error as below
2010-06-03 20:18:23,709 ERROR org.jboss.remoting.transport.bisocket.BisocketServ
*erInvoker [] - unable to create control connection after 10 retries*
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
Then I did the following,
Tried a telnet command from my box for 4457, 14000 and 14001. The telnet opened only for 4457 and 14000 and not for *14001*.
And I found that the JBoss Server is not listening at all on the 14001 port.
netstat -an|grep 4457, gave me,
*.4457 *.* 0 0 49152 0 LISTEN
and netstat -an|grep 14000, gave me,
*.14000 *.* 0 0 49152 0 LISTEN
But for 14001 there is no result.
Any thoughts?
Thanks,
Prabhu
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546070#546070]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 1 month