Description of problem: With the BPMS ER5 [1] unpackinging to EAP 6.1.1[2], I hit error when deploy the mortgage-demo which is available at [3] The error screenshot and server.log is attached. [1]:http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER5/jboss-bpms-6.0.0-redhat-5-deployable-eap6.x.zip [2]: http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.1.1/jboss-eap-6.1.1.zip [3]: http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER5/jboss-bpm-example-dist-1.0.0-redhat-1.zip Version-Release number of selected component (if applicable): ER5 (upstream tag: sync.2013.11.19) How reproducible: Steps to Reproduce: 1. Run BPMS ER5 2. unzip bpm-example-dist.zip ([3]) and follow the README Actual results: Expected results: Additional info:
Ryan, it seems you forgot to attach the server log / error screenshot.
Created attachment 829535 [details] server.log
Created attachment 829540 [details] screenshot
Sorry! I have uploaded the attachement now. (In reply to Kris Verlaenen from comment #3) > Ryan, it seems you forgot to attach the server log / error screenshot.
This is a known product issue: http://post-office.corp.redhat.com/archives/bpm-smes/2013-October/msg00034.html Kris, is there a bugzilla for it?
Michael, see server log, it seems there's an issue unmarshalling what seems to be a guided decision table, the xstream format is basically referencing older classes that have been refactored (to different packages). Any way to get this to work again? Or should the decision table be recreated from scratch?
The bpm-example-dist.zip contains an out of date information. org.kie.commons.java.nio.base.Properties no longer exists following the merge of org.kie.common to org.uberfire. See https://bugzilla.redhat.com/show_bug.cgi?id=1034253 for an identical report of this issue. The fix needs to be made in the bpm-example-dist.zip repository as detailed in the above BZ.
Thanks for the analyse. We still need to open this ticket to trace the changes which is required in jboss-bpm-example. Since we don't have a component in BZ list for jboss-bpm-example list, so I have to use "jbpm Bussiness Central"(which is incorrect). I would assign this to Babak.
In addition to the hidden files requiring an update, all Data Modeler Java classes also needed to be changed to stop using the "org.kie.workbench.common.services.datamodeller.annotations.Label" annotation and instead use "org.kie.api.definition.type.Label". Despite these two changes, the error persists. It is clearly the guided decision table as deleting the table removes the error. Recreating the decision table won't be easy. Back to Michael please, for an answer to what Kris asked!
The data models annotations are currently in a different package. The changes to do are simply replacing @org.kie.workbench.common.services.datamodeller.annotations.Label ---> @org.kie.api.definition.type.Label That should be enough to be able to open the data model from the tool itself, otherwise it'll fail.
OK, I scrolled down further in the log; and in addition to the Properties problem there was another error (doh!). You need to change the following:- 1) org.drools.guvnor.client.modeldriven.dt52.auditlog.DecisionTableAuditLogFilter --> org.drools.workbench.models.guided.dtable.shared.auditlog.DecisionTableAuditLogFilter 2) org.drools.workbench.models.commons.shared.rule.FreeFormLine ---> org.drools.workbench.models.datamodel.rule.FreeFormLine I've performed these changes locally and confirm the guided decision table can then be opened.
Thanks for your information! I think Babak will take over the fix. ( Michael, please don't move the status to "MODIFIED" before this is fixed in jboss-bpm-example code.) (In reply to manstis from comment #13) > OK, I scrolled down further in the log; and in addition to the Properties > problem there was another error (doh!). You need to change the following:- > > 1) > org.drools.guvnor.client.modeldriven.dt52.auditlog. > DecisionTableAuditLogFilter --> > org.drools.workbench.models.guided.dtable.shared.auditlog. > DecisionTableAuditLogFilter > > 2) org.drools.workbench.models.commons.shared.rule.FreeFormLine ---> > org.drools.workbench.models.datamodel.rule.FreeFormLine > > I've performed these changes locally and confirm the guided decision table > can then be opened.
I made the change but the same error persists.
I ended up recreating the decision table to get us moving forward. I am now able to open the decision table and build the project successfully. Not that I had to remove the Log column where I used to do a "sysout". I no longer see an option for free-form DRL in the action columns of a web decision table. If this feature has gone away, that's ok... however we should get confirmation on this. I have also not done a thorough and complete review of the various artifacts.
Can you please clarify "I no longer see an option for free-form DRL in the action columns of a web decision table"? You would need to select "Advanced" option from the new column popup and use a BRL Fragment that supports free-format DRL. We have no removed the feature. (In reply to Babak Mozaffari from comment #16) > I ended up recreating the decision table to get us moving forward. I am now > able to open the decision table and build the project successfully. > > Not that I had to remove the Log column where I used to do a "sysout". I no > longer see an option for free-form DRL in the action columns of a web > decision table. If this feature has gone away, that's ok... however we > should get confirmation on this. > > I have also not done a thorough and complete review of the various artifacts.
Yes, I can also build the project successfully in business-central console. But When I run the mortgage-demo-client to create new instance, I got the following error: [rzhang@/lab/1brms6/ER5/bpm-example-dist]$java -jar jboss-mortgage-demo-client.jar rzhang '$mypassword' Exception in thread "main" java.lang.NoClassDefFoundError: org/jbpm/process/audit/AuditLogService at org.kie.services.client.api.RemoteRestRuntimeFactory.newRuntimeEngine(RemoteRestRuntimeFactory.java:17) at com.redhat.bpms.examples.mortgage.CreateProcesses.getRuntimeEngine(CreateProcesses.java:111) at com.redhat.bpms.examples.mortgage.CreateProcesses.populateSamples(CreateProcesses.java:52) at com.redhat.bpms.examples.mortgage.CreateProcesses.main(CreateProcesses.java:47) Caused by: java.lang.ClassNotFoundException: org.jbpm.process.audit.AuditLogService at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 4 more (In reply to Babak Mozaffari from comment #16) > I ended up recreating the decision table to get us moving forward. I am now > able to open the decision table and build the project successfully. > > Not that I had to remove the Log column where I used to do a "sysout". I no > longer see an option for free-form DRL in the action columns of a web > decision table. If this feature has gone away, that's ok... however we > should get confirmation on this. > > I have also not done a thorough and complete review of the various artifacts.
Michael, When I tried "BRL Fragment", I did not get an option to type anything. I tried again just now and the decision table would not open at all. I get a blank screen in the editor and no errors in the log. I wiped my environment (from bin: rm -rf repositories .niogit .index) and restarted a fresh server and tried to create a web decision table in the sample repository and it was still a blank page. Any thoughts on what can happen to one's environment to cause this problem and how to fix it?
Ryan, I just tried the client jar file with the new build and I can't get that far. It complains of missing Apache LogFactory. Can you verify whether this is needed and not being bundled with the new build versions? Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.http.impl.client.AbstractHttpClient.<init>(AbstractHttpClient.java:187) at org.apache.http.impl.client.DefaultHttpClient.<init>(DefaultHttpClient.java:141) at org.kie.services.client.api.command.RemoteConfiguration.createPreemptiveAuthHttpClient(RemoteConfiguration.java:165) at org.kie.services.client.api.command.RemoteConfiguration.createAuthenticatingRequestFactory(RemoteConfiguration.java:150) at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:106) at org.kie.services.client.api.command.RemoteConfiguration.<init>(RemoteConfiguration.java:100) at org.kie.services.client.api.RemoteRestRuntimeFactory.<init>(RemoteRestRuntimeFactory.java:13) at com.redhat.bpms.examples.mortgage.CreateProcesses.getRuntimeEngine(CreateProcesses.java:110) at com.redhat.bpms.examples.mortgage.CreateProcesses.populateSamples(CreateProcesses.java:52) at com.redhat.bpms.examples.mortgage.CreateProcesses.main(CreateProcesses.java:47) Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 10 more
Yep, I have fixed the above error and moved forward to get the new error [1]. Please updated the code. [1]: [rzhang@/home/rzhang/workspace/3jboss-bpm-example-app/mortgage-demo-client/target]$java -jar mortgage-demo-client-1.0.0.jar rzhang $mypassword Exception in thread "main" java.lang.UnsupportedOperationException: Unsupported JAXB Class during initialization: 2 counts of IllegalAnnotationExceptions at org.kie.services.client.serialization.JaxbSerializationProvider.initializeJaxbContext(JaxbSerializationProvider.java:55) at org.kie.services.client.serialization.JaxbSerializationProvider.<init>(JaxbSerializationProvider.java:48) at org.kie.services.client.api.command.RemoteConfiguration.getJaxbSerializationProvider(RemoteConfiguration.java:395) at org.kie.services.client.api.command.AbstractRemoteCommandObject.executeRestCommand(AbstractRemoteCommandObject.java:296) at org.kie.services.client.api.command.AbstractRemoteCommandObject.execute(AbstractRemoteCommandObject.java:132) at org.drools.core.command.impl.CommandBasedStatefulKnowledgeSession.startProcess(CommandBasedStatefulKnowledgeSession.java:232) at com.redhat.bpms.examples.mortgage.CreateProcesses.populateSamples(CreateProcesses.java:57) at com.redhat.bpms.examples.mortgage.CreateProcesses.main(CreateProcesses.java:47) Caused by: com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions java.util.Map is an interface, and JAXB can't handle interfaces. this problem is related to the following location: at java.util.Map at private java.util.Map org.kie.services.client.serialization.jaxb.impl.process.JaxbWorkItem.parameters at org.kie.services.client.serialization.jaxb.impl.process.JaxbWorkItem java.util.Map does not have a no-arg default constructor. this problem is related to the following location: at java.util.Map at private java.util.Map org.kie.services.client.serialization.jaxb.impl.process.JaxbWorkItem.parameters at org.kie.services.client.serialization.jaxb.impl.process.JaxbWorkItem at com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:91) at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:436) at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:277) at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(JAXBContextImpl.java:1100) at com.sun.xml.internal.bind.v2.ContextFactory.createContext(ContextFactory.java:143) at com.sun.xml.internal.bind.v2.ContextFactory.createContext(ContextFactory.java:110) 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 javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:202) at javax.xml.bind.ContextFinder.find(ContextFinder.java:376) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522) at org.kie.services.client.serialization.JaxbSerializationProvider.initializeJaxbContext(JaxbSerializationProvider.java:53) ... 7 more (In reply to Babak Mozaffari from comment #20) > Ryan, > > I just tried the client jar file with the new build and I can't get that > far. It complains of missing Apache LogFactory. Can you verify whether this > is needed and not being bundled with the new build versions? > > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/logging/LogFactory > at > org.apache.http.impl.client.AbstractHttpClient.<init>(AbstractHttpClient. > java:187) > at > org.apache.http.impl.client.DefaultHttpClient.<init>(DefaultHttpClient.java: > 141) > at > org.kie.services.client.api.command.RemoteConfiguration. > createPreemptiveAuthHttpClient(RemoteConfiguration.java:165) > at > org.kie.services.client.api.command.RemoteConfiguration. > createAuthenticatingRequestFactory(RemoteConfiguration.java:150) > at > org.kie.services.client.api.command.RemoteConfiguration. > <init>(RemoteConfiguration.java:106) > at > org.kie.services.client.api.command.RemoteConfiguration. > <init>(RemoteConfiguration.java:100) > at > org.kie.services.client.api.RemoteRestRuntimeFactory. > <init>(RemoteRestRuntimeFactory.java:13) > at > com.redhat.bpms.examples.mortgage.CreateProcesses. > getRuntimeEngine(CreateProcesses.java:110) > at > com.redhat.bpms.examples.mortgage.CreateProcesses. > populateSamples(CreateProcesses.java:52) > at > com.redhat.bpms.examples.mortgage.CreateProcesses.main(CreateProcesses.java: > 47) > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.logging.LogFactory > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 10 more
Thanks Ryan, After getting your build changes, I am able to run the client and it successfully starts a process. However after reading the 3rd node of the process when it tries to call the web service, it fails, due to apparent changes in what BPMS expects. Please see if you can find what's changed and how we should adapt (would have to do with work item handler configuration and what seemed to be set up by default before). I have very limited bandwidth to maintain this and would need to pass it on if more effort is required. Caused by: org.drools.core.WorkItemHandlerNotFoundException: Could not find work item handler for WebService at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.throwWorkItemNotFoundException(JPAWorkItemManager.java:63) [drools-persistence-jpa-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.internalExecuteWorkItem(JPAWorkItemManager.java:58) [drools-persistence-jpa-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:124) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:155) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6]
The only remaining issue appears to be https://bugzilla.redhat.com/show_bug.cgi?id=1035256 Ready to be tested with ER6
Fixed issue with decision table: https://github.com/jboss-integration/jboss-bpm-example-app/commit/4514ad256564d922d5376e4baed6dfacfbe12559 Babak, could you please verify it is working as expected now?
It now gets past the rules but fails to create a human task... please remember that it's invoked from a client (API/REST): ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] (http-localhost/127.0.0.1:8080-4) Wed Dec 11 11:07:37 EST 2013: Error when creating task on task server for work item id 2. Error reported by task server: JBAS016071: Singleton not set for java.net.URLClassLoader@e1364dd. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.: java.lang.IllegalStateException: JBAS016071: Singleton not set for java.net.URLClassLoader@e1364dd. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:76) at org.jboss.weld.Container.instance(Container.java:54) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] at org.jbpm.services.task.impl.TaskServiceEntryPointImpl$Proxy$_$$_WeldClientProxy.addTask(TaskServiceEntryPointImpl$Proxy$_$$_WeldClientProxy.java) at org.jbpm.runtime.manager.impl.task.SynchronizedTaskService.addTask(SynchronizedTaskService.java:459) [jbpm-runtime-manager-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.services.task.wih.LocalHTWorkItemHandler.executeWorkItem(LocalHTWorkItemHandler.java:65) [jbpm-human-task-workitems-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.internalExecuteWorkItem(JPAWorkItemManager.java:56) [drools-persistence-jpa-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:124) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:155) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:337) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6] at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:352) [jbpm-flow-6.0.0-redhat-6.jar:6.0.0-redhat-6]
@Babak: After fixing the decision table, I believe I am able to successfully run the demo now. Both just starting a process in business-central and running through it till completion or running the script to create some instances. Could you clarify how to reproduce those? What steps should I take to encounter this issue?
Kris, I got the latest off your new repo and did a build. I installed a fresh EAP 6.1 with BPMS ER5 on top of it, deployed the web app, went to KIE WB, did a build, and ran the client. Same issue with the classloader as above. Are you running ER5/EAP or the master branch, where something may have changed?
I wasn't able to find any issue while doing another test run on the latest version (ER7), so marking this as MODIFIED for verification.
Reopened as there's still an issue executing the process with modules.
The issue with modules has been fixed. The problem was due to code lines like "this.getClass().getClassLoader()" in classes located into an EAP static module. Weld singletons are stored in a Map collection using the webapp classloader as the entry key, so using the current class classloader to obtain the singletions was failing. I have reviewed in whole drools&jbpm modules potential code errors like this one and I have fixed all of them that apply. These are all modified sources: - jbpm/jbpm-workitems/src/main/java/org/jbpm/process/workitem/webservice/WebServiceWorkItemHandler.java - jbpm/jbpm-workitems/src/main/java/org/jbpm/process/workitem/bpmn2/ServiceTaskHandler.java - jbpm/jbpm-workitems/src/main/java/org/jbpm/process/workitem/webservice/WebServiceCommand.java - jbpm/jbpm-flow/src/main/java/org/jbpm/process/instance/ProcessRuntimeImpl.java jbpm/jbpm-services/jbpm-executor/src/main/java/org/jbpm/executor/impl/ExecutorRunnable.java - drools/drools-core/src/main/java/org/drools/core/util/BinaryRuleBaseLoader.java Commits for master ================== - https://github.com/droolsjbpm/jbpm/commit/bc29778f588721a8fd5292af9b1f67076aab6d76 - https://github.com/droolsjbpm/drools/commit/5ae6560d8aa37d07e862477d6c52052ac515c35a Commits for 6.0.x ================= - https://github.com/droolsjbpm/jbpm/commit/884110ec82507bbaf5f649d4013200bfb5f0026d - https://github.com/droolsjbpm/drools/commit/eedc866e6e1eb3c0080f6de75d6f5bd8a8998871
Hi Ryan, The exception that I fixed was not this one.... it was a classnotfound exception. It happened when trying to execute a jboss-mortgage-demo-client process task. So I think this issue will not be solved with my fix. By the other hand, this fix I think it was not included in lastest release... but Kris told me he was going to send the war, if you want I can ask him. Anyway, we must resolve the exception you just sent. Let me take a look at it! :) Some questions: - Are you using EAP static modules distribution or the war without static bpms modules dependencies? - How did you get to reproduce it? Do you know the step to reproduce it? Would be helpful.. - Where can I obtain the release which you are testing? Thanks in advance, Roger
Roger, I experience the issue as follows: From http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER7/, set up: - jboss-bpms-6.0.0-redhat-7-deployable-eap6.x.zip on top of EAP 6.1.1 - jboss-bpm-example-dist-1.0.0-redhat-3.zip: Deploy xxx-ws.war Start server, set up appropriate users, build project. Restart server to get a clean log. Run the client jar from the downloaded example dist zip. The first attempt to create a human task results in an error: 12:08:34,952 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] (http-localhost/127.0.0.1:8080-1) Thu Jan 02 12:08:34 PST 2014: Error when creating task on task server for work item id 2. Error reported by task server: JBAS016071: Singleton not set for java.net.URLClassLoader@269e30. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.: java.lang.IllegalStateException: JBAS016071: Singleton not set for java.net.URLClassLoader@269e30. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:76) at org.jboss.weld.Container.instance(Container.java:54) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] The full log is attached. Now more interesting, log in to business-central and start a process from there. It runs successfully and creates the task. At this point, presumably, a required class has been loaded. Going back to the client jar and running it again (without restarting the server) is successful.
Created attachment 844704 [details] ModuleGroupSingletonProvider error from client jar
Hi, Thanks. I have reproduced the issue. Currently working on it.. Regards, (In reply to Babak Mozaffari from comment #33) > Roger, I experience the issue as follows: > > From http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER7/, set > up: > > - jboss-bpms-6.0.0-redhat-7-deployable-eap6.x.zip on top of EAP 6.1.1 > - jboss-bpm-example-dist-1.0.0-redhat-3.zip: Deploy xxx-ws.war > > Start server, set up appropriate users, build project. Restart server to get > a clean log. Run the client jar from the downloaded example dist zip. The > first attempt to create a human task results in an error: > > 12:08:34,952 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] > (http-localhost/127.0.0.1:8080-1) Thu Jan 02 12:08:34 PST 2014: Error when > creating task on task server for work item id 2. Error reported by task > server: JBAS016071: Singleton not set for java.net.URLClassLoader@269e30. > This means that you are trying to access a weld deployment with a Thread > Context ClassLoader that is not associated with the deployment.: > java.lang.IllegalStateException: JBAS016071: Singleton not set for > java.net.URLClassLoader@269e30. This means that you are trying to access a > weld deployment with a Thread Context ClassLoader that is not associated > with the deployment. > at > org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton. > get(ModuleGroupSingletonProvider.java:76) > at org.jboss.weld.Container.instance(Container.java:54) > [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > > > The full log is attached. > > Now more interesting, log in to business-central and start a process from > there. It runs successfully and creates the task. At this point, presumably, > a required class has been loaded. Going back to the client jar and running > it again (without restarting the server) is successful.
Hi Babak, Sorry, I was using and old local tag.. This exception that you comment is already fixed in my last comment #30. I have tested the latest 6.0.2-SNAPHOST, where I pushed the fix, and this exception is not happening (following your steps). So I will modify the state to MODIFIED. Thanks (In reply to Babak Mozaffari from comment #33) > Roger, I experience the issue as follows: > > From http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER7/, set > up: > > - jboss-bpms-6.0.0-redhat-7-deployable-eap6.x.zip on top of EAP 6.1.1 > - jboss-bpm-example-dist-1.0.0-redhat-3.zip: Deploy xxx-ws.war > > Start server, set up appropriate users, build project. Restart server to get > a clean log. Run the client jar from the downloaded example dist zip. The > first attempt to create a human task results in an error: > > 12:08:34,952 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] > (http-localhost/127.0.0.1:8080-1) Thu Jan 02 12:08:34 PST 2014: Error when > creating task on task server for work item id 2. Error reported by task > server: JBAS016071: Singleton not set for java.net.URLClassLoader@269e30. > This means that you are trying to access a weld deployment with a Thread > Context ClassLoader that is not associated with the deployment.: > java.lang.IllegalStateException: JBAS016071: Singleton not set for > java.net.URLClassLoader@269e30. This means that you are trying to access a > weld deployment with a Thread Context ClassLoader that is not associated > with the deployment. > at > org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton. > get(ModuleGroupSingletonProvider.java:76) > at org.jboss.weld.Container.instance(Container.java:54) > [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1] > > > The full log is attached. > > Now more interesting, log in to business-central and start a process from > there. It runs successfully and creates the task. At this point, presumably, > a required class has been loaded. Going back to the client jar and running > it again (without restarting the server) is successful.
Thanks, Roger, I'll look for it in BPMS ER8, hoping it makes that release.
This still failed to deploy in CR1. I tested both the version I built based on the latest version of jboss bpmp example and the binary in http://people.redhat.com/bmozaffa/jboss-bpm-example-dist-1.0.0.zip, they all shows the same error : 17:57:46,577 ERROR [org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl] (http-localhost/127.0.0.1:8080-10) Deployment of unit com.redhat.bpms.examples:mortgage:1 failed: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException: org.jbpm.console.ng.bd.exception.DeploymentException: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploy(DeploymentManagerEntryPointImpl.java:117) [jbpm-console-ng-business-domain-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploy(DeploymentManagerEntryPointImpl.java:101) [jbpm-console-ng-business-domain-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.process(DeploymentManagerEntryPointImpl.java:243) [jbpm-console-ng-business-domain-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.process(DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.java) [jbpm-console-ng-business-domain-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.guvnor.common.services.builder.BuildServiceImpl.buildAndDeploy(BuildServiceImpl.java:104) [guvnor-project-builder-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.guvnor.common.services.builder.BuildServiceImpl$Proxy$_$$_WeldClientProxy.buildAndDeploy(BuildServiceImpl$Proxy$_$$_WeldClientProxy.java) [guvnor-project-builder-6.0.2-redhat-1.jar:6.0.2-redhat-1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_43] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.jboss.errai.bus.server.io.AbstractRPCMethodCallback.invokeMethodFromMessage(AbstractRPCMethodCallback.java:48) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.io.ValueReplyRPCEndpointCallback.callback(ValueReplyRPCEndpointCallback.java:22) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.io.RemoteServiceCallback.callback(RemoteServiceCallback.java:54) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.cdi.server.CDIExtensionPoints$3.callback(CDIExtensionPoints.java:499) [errai-weld-integration-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.DeliveryPlan.deliver(DeliveryPlan.java:47) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.ServerMessageBusImpl.sendGlobal(ServerMessageBusImpl.java:284) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.SimpleDispatcher.dispatchGlobal(SimpleDispatcher.java:46) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:92) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:109) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:140) [errai-bus-2.4.3.Final-redhat-3.jar:2.4.3.Final-redhat-3] at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:155) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:288) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:59) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:197) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [solder-impl-3.2.1.Final.jar:3.2.1.Final] at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) [:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:236) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:59) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:197) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) [solder-impl-3.2.1.Final.jar:3.2.1.Final] at sun.reflect.GeneratedMethodAccessor175.invoke(Unknown Source) [:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:236) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:59) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:197) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jbpm.designer.web.filter.impl.PluggableFilter.doFilter(PluggableFilter.java:70) [jbpm-designer-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source) [:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:236) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:59) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:197) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.uberfire.security.server.UberFireSecurityFilter.doFilter(UberFireSecurityFilter.java:266) [uberfire-security-server-0.3.2-redhat-1.jar:0.3.2-redhat-1] at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source) [:1.6.0_43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_43] at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) [rt.jar:1.6.0_43] at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:236) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:59) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:197) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_43] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:499) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:408) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_43] Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.jbpm.kie.services.impl.AbstractDeploymentService.commonDeploy(AbstractDeploymentService.java:98) [jbpm-kie-services-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.kie.services.impl.KModuleDeploymentService.deploy(KModuleDeploymentService.java:152) [jbpm-kie-services-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.kie.services.impl.KModuleDeploymentService$Proxy$_$$_WeldClientProxy.deploy(KModuleDeploymentService$Proxy$_$$_WeldClientProxy.java) [jbpm-kie-services-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploy(DeploymentManagerEntryPointImpl.java:111) [jbpm-console-ng-business-domain-backend-6.0.2-redhat-1.jar:6.0.2-redhat-1] ... 110 more Caused by: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.buildCommandService(KnowledgeStoreServiceImpl.java:143) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.newKieSession(KnowledgeStoreServiceImpl.java:67) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.newKieSession(KnowledgeStoreServiceImpl.java:36) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.kie.internal.persistence.jpa.JPAKnowledgeService.newStatefulKnowledgeSession(JPAKnowledgeService.java:121) [kie-internal-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.runtime.manager.impl.factory.JPASessionFactory.newKieSession(JPASessionFactory.java:41) [jbpm-runtime-manager-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.runtime.manager.impl.SingletonRuntimeManager.init(SingletonRuntimeManager.java:95) [jbpm-runtime-manager-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.runtime.manager.impl.RuntimeManagerFactoryImpl.newSingletonRuntimeManager(RuntimeManagerFactoryImpl.java:71) [jbpm-runtime-manager-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.runtime.manager.impl.RuntimeManagerFactoryImpl$Proxy$_$$_WeldClientProxy.newSingletonRuntimeManager(RuntimeManagerFactoryImpl$Proxy$_$$_WeldClientProxy.java) [jbpm-runtime-manager-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.jbpm.kie.services.impl.AbstractDeploymentService.commonDeploy(AbstractDeploymentService.java:83) [jbpm-kie-services-6.0.2-redhat-1.jar:6.0.2-redhat-1] ... 113 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_43] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_43] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_43] at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_43] at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.buildCommandService(KnowledgeStoreServiceImpl.java:129) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] ... 121 more Caused by: java.lang.IllegalArgumentException: Timer service 'new org.jbpm.process.core.timer.impl.RegisteredTimerServiceDelegate("com.redhat.bpms.examples:mortgage:1-timerServiceId")' not found at org.drools.core.SessionConfiguration.newTimerService(SessionConfiguration.java:489) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.time.TimerServiceFactory.getTimerService(TimerServiceFactory.java:27) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.common.AbstractWorkingMemory.<init>(AbstractWorkingMemory.java:358) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.common.AbstractWorkingMemory.<init>(AbstractWorkingMemory.java:261) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.common.PhreakWorkingMemoryFactory.createWorkingMemory(PhreakWorkingMemoryFactory.java:15) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.reteoo.ReteooRuleBase.newStatefulSession(ReteooRuleBase.java:1124) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.reteoo.ReteooRuleBase.newStatefulSession(ReteooRuleBase.java:1109) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.impl.KnowledgeBaseImpl.newStatefulKnowledgeSession(KnowledgeBaseImpl.java:179) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.core.impl.KnowledgeBaseImpl.newKieSession(KnowledgeBaseImpl.java:380) [drools-core-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.persistence.SingleSessionCommandService.initNewKnowledgeSession(SingleSessionCommandService.java:147) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] at org.drools.persistence.SingleSessionCommandService.<init>(SingleSessionCommandService.java:114) [drools-persistence-jpa-6.0.2-redhat-1.jar:6.0.2-redhat-1] ... 126 more (The full server.log is also attached) I will still pass this on ON_QA for futher confirm.
Created attachment 851499 [details] server_Jan17.log
Please, let me know if you and maciej have resolved the issue... if I can close it or it has to be reassigned or whatever... :) Thx. (In reply to Ryan Zhang from comment #39) > Created attachment 851499 [details] > server_Jan17.log
Yes, after a disucssion with maciej, this error is caused by using the seurity policy which requested by https://bugzilla.redhat.com/show_bug.cgi?id=1053321. For some reason, it stops some calling/class loading when mortgage-demo get deployed. Futher action is still in investigation.
If removed the last line(ie disable the security policy files in JAVA_OPTS), it can pass.
Created separate issue to keep track of the deploy issue: https://bugzilla.redhat.com/show_bug.cgi?id=1054834
I have run the mortage-demo in [1] based on CR1 after disable the security policies. However after deploy the repo and deploy the -ws.war, I still got the same error in https://bugzilla.redhat.com/show_bug.cgi?id=1033590#c31 It seems to me the mortage-client still can't be running. Needs Roger and Babak's attention on this.
Thanks for Kris's reply on email.. It turns out the root cause of the error I reported in Comment 45 is the JRE version. From my testing, JDK 1.7.0_05 and any JDK 1.6.0_xx version will fail with the reported error. JDK 1.7.0_17 will pass on mortage demo client. Does this need documentation to describe ?
However the minimor JDK version requires by the mortgage demo is still unknown. This might need to investigate before we point this out in documentation. (In reply to Ryan Zhang from comment #46) > Thanks for Kris's reply on email.. > > > It turns out the root cause of the error I reported in Comment 45 is the JRE > version. > > From my testing, JDK 1.7.0_05 and any JDK 1.6.0_xx version will fail with > the reported error. > > JDK 1.7.0_17 will pass on mortage demo client. > > Does this need documentation to describe ?
Hi Ryan, I think i'm not in copy of Kris' email.. let me clarify please. So the exception is Comment 45 it's still happening when using any of JDK 1.7.0_05 or JDK 1.6.0_xx?? Thanks (In reply to Ryan Zhang from comment #47) > However the minimor JDK version requires by the mortgage demo is still > unknown. > > This might need to investigate before we point this out in documentation. > > (In reply to Ryan Zhang from comment #46) > > Thanks for Kris's reply on email.. > > > > > > It turns out the root cause of the error I reported in Comment 45 is the JRE > > version. > > > > From my testing, JDK 1.7.0_05 and any JDK 1.6.0_xx version will fail with > > the reported error. > > > > JDK 1.7.0_17 will pass on mortage demo client. > > > > Does this need documentation to describe ?
Added additional commit to fix jaxb issue as described in comment #31. https://github.com/jboss-integration/jboss-bpm-example-app/commit/12f192c2ee3f4eee560126da203ffd3e0c9c49ee
Ok, as discussed in email. We will pick up the fix for jaxb issues for 6.0.1 instead of 6.0.0. (In reply to Kris Verlaenen from comment #49) > Added additional commit to fix jaxb issue as described in comment #31. > > https://github.com/jboss-integration/jboss-bpm-example-app/commit/ > 12f192c2ee3f4eee560126da203ffd3e0c9c49ee
Yes. And as Kris fix this jaxb issues, the dependency on JRE versions is not necessary any more. But before that, higher version JRE is required. (In reply to Roger Martínez from comment #48) > Hi Ryan, > > I think i'm not in copy of Kris' email.. let me clarify please. So the > exception is Comment 45 it's still happening when using any of JDK 1.7.0_05 > or JDK 1.6.0_xx?? > > Thanks > > (In reply to Ryan Zhang from comment #47) > > However the minimor JDK version requires by the mortgage demo is still > > unknown. > > > > This might need to investigate before we point this out in documentation. > > > > (In reply to Ryan Zhang from comment #46) > > > Thanks for Kris's reply on email.. > > > > > > > > > It turns out the root cause of the error I reported in Comment 45 is the JRE > > > version. > > > > > > From my testing, JDK 1.7.0_05 and any JDK 1.6.0_xx version will fail with > > > the reported error. > > > > > > JDK 1.7.0_17 will pass on mortage demo client. > > > > > > Does this need documentation to describe ?
Most of this issues reported in this BZ are fixed in BPMS 6.0.0 CR1, but as a whole, this BZ cannot yet be verified, as there is still one outstanding issue for which fix will be available only in CR2 build (JAXB dependency problem). Setting as MODIFIED for now
Note that the jaxb fix will not be available in CR2, it should be in 6.0.1.
Setting this to ON_QA for CR2. Can you open a separate bz for the outstanding jaxb issue targeted for 6.0.1?
Separate bug 1058168 was opened to track the JAXB issue. All the other issues have been resolved in BPMS 6.0.0 CR2 - marking this bz as verified.