[JBoss jBPM] - problem with examples and ant deploy.examples on jbpm-4.0-CR
by jwerkmeister
Hi
why does the ant file (deploy.examples) included with the examples exclude all these project?
| <jar destfile="${jbpm.home}/examples/target/examples.bar">
| <fileset dir="${jbpm.home}/examples/src">
| <include name="**/*.jpdl.xml" />
| <exclude name="org/jbpm/examples/task/swimlane/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/task/candidates/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/concurrency/graphbased/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/timer/repeat/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/script/text/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/decision/handler/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/mail/template/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/script/expression/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/task/assignee/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/mail/inline/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/mail/template/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/eventlistener/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/timer/event/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/task/assignmenthandler/process.jpdl.xml" />
| <exclude name="org/jbpm/examples/java/JavaInstantiateTest.java" />
| </fileset>
| </jar>
|
I deleted the eventlistener process exclusion and after running the ant file I cannot see the process list on the console anymore. It shows error:
| org.jbpm.api.JbpmException:
| error: couldn't interpret the dom model: couldn't create object: couldn't load class org.jbpm.examples.eventlistener.LogListener : org.jbpm.pvm.internal.wire.WireException: couldn't create object: couldn't load class org.jbpm.examples.eventlistener.LogListener
| xml validation error: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'on'. [line=10 column=43 ]: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'on'.
| xml validation error: cvc-complex-type.2.4.a: Invalid content was found starting with element 'custom'. One of '{"http://jbpm.org/4.0/jpdl":swimlane, "http://jbpm.org/4.0/jpdl":on, "http://jbpm.org/4.0/jpdl":timer, "http://jbpm.org/4.0/jpdl":start, "http://jbpm.org/4.0/jpdl":end, "http://jbpm.org/4.0/jpdl":end-cancel, "http://jbpm.org/4.0/jpdl":end-error, "http://jbpm.org/4.0/jpdl":state, "http://jbpm.org/4.0/jpdl":decision, "http://jbpm.org/4.0/jpdl":fork, "http://jbpm.org/4.0/jpdl":join, "http://jbpm.org/4.0/jpdl":script, "http://jbpm.org/4.0/jpdl":hql, "http://jbpm.org/4.0/jpdl":sql, "http://jbpm.org/4.0/jpdl":java, "http://jbpm.org/4.0/jpdl":task, "http://jbpm.org/4.0/jpdl":sub-process}' is expected. [line=11 column=26 ]: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'custom'. One of '{"http://jbpm.org/4.0/jpdl":swimlane, "http://jbpm.org/4.0/jpdl":on, "http://jbpm.org/4.0/jpdl":timer, "http://jbpm.org/4.0/jpdl":start, "http://jbpm.org/4.0/jpdl":end, "http://jbpm.org/4.0/jpdl":end-cancel, "http://jbpm.org/4.0/jpdl":end-error, "http://jbpm.org/4.0/jpdl":state, "http://jbpm.org/4.0/jpdl":decision, "http://jbpm.org/4.0/jpdl":fork, "http://jbpm.org/4.0/jpdl":join, "http://jbpm.org/4.0/jpdl":script, "http://jbpm.org/4.0/jpdl":hql, "http://jbpm.org/4.0/jpdl":sql, "http://jbpm.org/4.0/jpdl":java, "http://jbpm.org/4.0/jpdl":task, "http://jbpm.org/4.0/jpdl":sub-process}' is expected.
| xml validation error: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'java'. [line=13 column=24 ]: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'java'.
| xml validation error: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'java'. [line=21 column=25 ]: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'continue' is not allowed to appear in element 'java'.
| org.jbpm.pvm.internal.xml.ProblemList.getJbpmException(ProblemList.java:169)
| org.jbpm.pvm.internal.xml.ProblemList.getJbpmException(ProblemList.java:142)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239194#4239194
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239194
17 years
[JBossWS] - Cannot find child element: parameters
by klowtherjr
Hi all,
I'm working with wsdl2java generated classes making an rpc call in JBoss 4.2.3 to a WSDL on another platform.
This seems to work fine until the response comes back to the client. The response comes back as follows.
| <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
| <soapenv:Body>
| <wmscr:SubmitPirepResponse xsi:schemaLocation="urn:faa:nas:wmscr:1:0 SubmitPirep.xsd" xmlns:aw="urn:faa:nas:swim:aviationwx:1:0" xmlns:swim="urn:bhmi:wmscr:swim:1:0" xmlns:wmscr="urn:faa:nas:wmscr:1:0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
| </soapenv:Body>
| </soapenv:Envelope>
|
My client errors out with the following message that I'll truncate to keep the post short(er):
Exception Stack Trace:javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Cannot find child element: parameters
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
... (truncated here)
Caused by: org.jboss.ws.WSException: Cannot find child element: parameters
at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:917)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
... 105 more
(truncated here as well)
This indicates to me that the response is not sending a tag when the client clearly expects it.
I can see a tag in the inbound request when the request gets to the web service. My question is where does the requirement for this tag come from (SOAP?, JAXB?).
I cannot find a mention of it anywhere in any of the specs I've been looking at. It's probably right in front of my face and I'm just not seeing it.
Thank you for any light you can shed on this issue.
Ken
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239188#4239188
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239188
17 years
[JBoss Cache: Core Edition] - Re: BerkeleyDB Deadlock Exception from JBoss Cache Loader: B
by niuxuetao_fiserv
Maybe something useful to give:
Now I use 20 threads doing the same job (setting ockAcquisitionTimeout="4294967", all the rest configuration is the same as I pasted before), I experience a phenonemen which seems to be a "true deadlock" since no threads are running (jobs in the Threadpool Executor's queue are undone) and the cpu usage is zero. Then after a while, like 1 minute, one of the threads threw this:
| org.jboss.cache.pojo.PojoCacheException: attach failed /RTDE/time-distance-analysis-tdm/4207
| at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:111)
| at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
| at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:88)
| at com.fiserv.detection.eventcache.jboss.JBossPojoCacheStorage.update(JBossPojoCacheStorage.java:50)
| at com.fiserv.detection.eventcache.statemachine.CacheAccessor.save(CacheAccessor.java:117)
| at com.fiserv.detection.eventcache.statemachine.CacheAccessor.matchOne(CacheAccessor.java:84)
| at com.fiserv.detection.tda.TimeDistanceAnalysis.doDetection(TimeDistanceAnalysis.java:71)
| ... 53 more
| Caused by: java.lang.IllegalStateException: Cache not in STARTED state!
| at org.jboss.cache.invocation.CacheInvocationDelegate.cacheStatusCheck(CacheInvocationDelegate.java:660)
| at org.jboss.cache.invocation.CacheInvocationDelegate.get(CacheInvocationDelegate.java:446)
| at org.jboss.cache.pojo.impl.InternalHelper.get(InternalHelper.java:100)
| at org.jboss.cache.pojo.impl.InternalHelper.getPojoReference(InternalHelper.java:47)
| at org.jboss.cache.pojo.impl.InternalHelper.getPojo(InternalHelper.java:141)
| at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:104)
| at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
| ... 59 more
|
Have you seen anything like this?
Regards,
Xuetao
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239186#4239186
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239186
17 years
[JBoss Cache: Core Edition] - Re: BerkeleyDB Deadlock Exception from JBoss Cache Loader: B
by niuxuetao_fiserv
Hi Galder,
Thanks for the hints to probe the problem!
The size of a Pojo is between 5k and 100k by estimate.
I did not track the lock-holder thread's behavior, cuz I do not know how to do it, could you give some tips on this?
I disabled the preloading and I haven't seen the berkeleyDb deadlock exception, but often see jboss cache lock exception as below if I set the lockAcquisitionTimeout to smaller values.
| org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn [/RTDE/pattern-matching-threshold/663330655] after [100] milliseconds for requestor [GlobalTransaction:<null>:2]! Lock held by [GlobalTransaction:<null>:1]
| at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:170)
| at org.jboss.cache.mvcc.MVCCNodeHelper.wrapNodeForWriting(MVCCNodeHelper.java:203)
| at org.jboss.cache.interceptors.MVCCLockingInterceptor.handlePutKeyValueCommand(MVCCLockingInterceptor.java:98)
| at org.jboss.cache.interceptors.base.PrePostProcessingCommandInterceptor.visitPutKeyValueCommand(PrePostProcessingCommandInterceptor.java:88)
| at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
| at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
| at org.jboss.cache.interceptors.CacheLoaderInterceptor.visitPutKeyValueCommand(CacheLoaderInterceptor.java:130)
| at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
| at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
| at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:131)
| at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
| at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
| at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
| at org.jboss.cache.interceptors.TxInterceptor.attachGtxAndPassUpChain(TxInterceptor.java:284)
| at org.jboss.cache.interceptors.TxInterceptor.handleDefault(TxInterceptor.java:271)
| at org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
| at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
| at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
| at org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:178)
| at org.jboss.cache.interceptors.InvocationContextInterceptor.visitPutKeyValueCommand(InvocationContextInterceptor.java:82)
| at org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
| at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:265)
| at org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:560)
| at org.jboss.cache.pojo.impl.InternalHelper.lockPojo(InternalHelper.java:342)
| at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:101)
| at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
|
What I am also wondering are these:
- Does the lockAcquisitionTimeout configuration of jboss cache also change Berkeley DB's such configuration?
- If I set the lockAcquisitionTimeout to a the largest available figure, is there a true deadlock possibility in JBoss cache (when using either of the READ_COMMITED or REPEATABLE_READ isolation levels)? By "true deadlock" I mean even if someone can let the lock requester wait for any amount of longer time, the requester will NEVER get the lock.
Thanks a lot!
Xuetao
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239181#4239181
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239181
17 years
![img]http://www.powerconsultantsinc.com/knots/jsf_new_project.jpg[/img](http://img]http://www.powerconsultantsinc.com/knots/jsf_new_project.jpg[/img){kind=link}
