[jBPM Development] - org.jbpm.api.JbpmException: couldn't get resource urls for jbpm.user.wire.bindings.xml
by Chaitanya Desai
Chaitanya Desai [http://community.jboss.org/people/chaitanya_d6%40yahoo.com] created the discussion
"org.jbpm.api.JbpmException: couldn't get resource urls for jbpm.user.wire.bindings.xml"
To view the discussion, visit: http://community.jboss.org/message/561436#561436
--------------------------------------------------------------
I have a sample Hello project with following structure
C:\jbpmTrial\Hello is my workspace : Hello is the project within jbpmTrial workspace
*Hello
------src
------org.example.sample.greeting
-----Hello.java
-----hello.jpdl.xml
------hello.png
------review.ftl
------- jbpm.cfg.xml
------- jbpm.hibernate.cfg.xml
jBPM Libraries
jbpm installation: C:\jbpm-4.4
Jboss: C:\jboss-5.1.0.GA
jdk:C:\jdk1.6.0_21
I modified the ant build file provided with sample examples to deploy Hello project. I am able to see deployment on jbpm console and even the task forms and view the sample println outputs produced from another function in Hello.java file using cmd.
However when i try to access the processEngine and program/code certain logic in the main method I get an error
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jbpm.pvm.internal.cfg.ConfigurationParser.<init>(ConfigurationParser.java:46)
at org.jbpm.pvm.internal.cfg.ConfigurationParser.<clinit>(ConfigurationParser.java:49)
at org.jbpm.pvm.internal.cfg.ConfigurationImpl.parse(ConfigurationImpl.java:137)
at org.jbpm.pvm.internal.cfg.ConfigurationImpl.setResource(ConfigurationImpl.java:116)
at org.jbpm.pvm.internal.cfg.ConfigurationImpl.setResource(ConfigurationImpl.java:50)
at org.jbpm.api.Configuration.setResource(Configuration.java:79)
at org.example.sample.greeting.Hello.main(Hello.java:26)
Caused by: org.jbpm.api.JbpmException: couldn't get resource urls for jbpm.user.wire.bindings.xml
at org.jbpm.pvm.internal.wire.xml.WireParser.<clinit>(WireParser.java:284)
... 7 more
Caused by: java.lang.NullPointerException
at org.jbpm.pvm.internal.wire.xml.WireParser.<clinit>(WireParser.java:281)
... 7 more
The error is observed @ line:
ProcessEngine processEngine = new Configuration().setResource("C:/jbpmTrial/Hello/src/jbpm.cfg.xml").buildProcessEngine();
The main method that i am trying to run is :
public static void main(String args[])
{
String location="C:/jbpmTrial/Hello/src/jbpm.cfg.xml";
URL u = ClassLoader.getSystemResource(location);
ProcessEngine processEngine = new Configuration().setResource("C:/jbpmTrial/Hello/src/jbpm.cfg.xml").buildProcessEngine();
System.out.println("Hello world, Starting the flow");
System.out.println("Ending the flow");
}
jbpm.cfg.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.businesscalendar.cfg.xml" />
<import resource="jbpm.tx.hibernate.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.bpmn.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<!-- Job executor is excluded for running the example test cases. -->
<!-- To enable timers and messages in production use, this should be included. -->
<!--
<import resource="jbpm.jobexecutor.cfg.xml" />
-->
<string name="jbpm.mail.smtp.host" value="smtp.gmail.com" />
<string name="resource.mail.properties" value="jbpm.mail.properties" />
</jbpm-configuration>
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.businesscalendar.cfg.xml" />
<import resource="jbpm.tx.hibernate.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.bpmn.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<!-- Job executor is excluded for running the example test cases. -->
<!-- To enable timers and messages in production use, this should be included. -->
<!--
<import resource="jbpm.jobexecutor.cfg.xml" />
-->
<string name="jbpm.mail.smtp.host" value="smtp.gmail.com" />
<string name="resource.mail.properties" value="jbpm.mail.properties" />
</jbpm-configuration>
Can anyone please explain me What is the root cause and give me pointers in appropriate direction to solve this. I am starting with Jbpm.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/561436#561436]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
[JBoss AS7 Development] - Re: AS 7 Deployment APIs
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] created the discussion
"Re: AS 7 Deployment APIs"
To view the discussion, visit: http://community.jboss.org/message/561145#561145
--------------------------------------------------------------
I want to simplify the rollback handling a bit.
Right now there are a number levels at which a user can specify that they want rollback in case of failure:
1) At the level of an individual action within a larger set of actions (Example: my plan deploys 3 apps, and if #2 fails I want it rolled back, but don't roll back #1 or #3)
2) Within a set of actions that apply to a server. If any action in the set fails, all roll back. For a standalone server, this is specified with the withGlobalRollback() call shown above.
And, for the domain controller use case only (irrelevant to standalone server case):
3) For a set of servers in a server group, whether failure on one or more trigger rollback across the group.
4) For a set of servers groups to which the same set of changes is being applied, whether failure of one server group triggers rollback of the others. (Example: multiple servers running same app, divided into multiple server groups to facilitate a rolling upgrade)
5) For a large complex plan where different sets of changes are applied to different server groups, whether failure of one set triggers rollbacks of other sets. (Example: in a multi-tier topology, roll out some deployments to server-groups in tier A, and then roll out different deployments to servers in tier B.)
I want to get rid of 1). It complicates the implementation and I don't think it adds a lot of benefit. If people want different behavior for different deployments, they can be executed separately without much trouble.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/561145#561145]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
[EJB 3.0 Development] - Deployment to JBoss unsuccessful: EJB3 VMID is already registered
by Csaba Toth
Csaba Toth [http://community.jboss.org/people/tothc] created the discussion
"Deployment to JBoss unsuccessful: EJB3 VMID is already registered"
To view the discussion, visit: http://community.jboss.org/message/561193#561193
--------------------------------------------------------------
I'm modifing an open-source project's code to implement special system for academic research.
See OpenEMPI: http://www.openempi.org/ http://www.openempi.org/
It uses PostgreSQL, Spring, and it exposes some functionality through EJB3 interfaces.
I deploy the ear into a JBoss 4.2.3 GA-jdk6, I use 1.6.0_21 Java JDK, Windows 7 x64 operating system (+ Ubuntu machines, right now my developer machine has Windows 7, but I'll move soon to Ubuntu.
I made several changes to OpenEMPI, and now I want to set up a scheme where OpenEMPI communicates with another one through the EJB3 interfaces.
More than 3 weeks ago I achieved that and I moved the other component to the Ubuntu machines.
Then I also wanted to make the communication secure, so I made several configuration changes to JBoss to leverage SSL.
Things started to go wrong. The test code managed to get the EJB3 Service interface 2 weeks ago, but when I called actual functions on it, the communication stopped. I ran the server in SSL debug mode, but couldn't figure out why it didn't work. I ruled out all firewalls, so that cannot be the problem. Things still worked on my developer machine, if I deployed all componenets to the same JBoss.
I decided to move back to the non SSL configuration, but now I'm totally stuck, because I couldn't even deploy my modified OpenEMPI to my local JBoss.
I have no idea why. It must be some simple configuration problem, but I don't know what it is and I hope you can help.
Error message:
14:37:55,953 INFO [EARDeployer] Init J2EE application: file:/C:/jboss/server/default/deploy/openempi-2.0.5.ear
14:38:10,594 WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=openempi-ejb-2.0.5.jar
java.lang.IllegalStateException: Container jboss.j2ee:ear=openempi-2.0.5.ear,jar=openempi-ejb-2.0.5.jar,name=PersonManagerService,service=EJB3,VMID=1be0395c8ac2f5a9:-a9218d4:12af800b119:-7f8e + is already registered
at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:114)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:494)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:442)
at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:423)
at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:384)
at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:327)
at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy33.create(Unknown Source)
at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:492)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:76)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy34.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
14:38:11,181 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class: com.google.gwt.junit.server.JUnitHostImpl
14:38:11,195 INFO [EJB3Deployer] Deployed: file:/C:/jboss/server/default/tmp/deploy/tmp603717587478542091openempi-2.0.5.ear-contents/openempi-ejb-2.0.5.jar
14:38:11,204 INFO [TomcatDeployer] deploy, ctxPath=/openempi-admin, warUrl=.../tmp/deploy/tmp603717587478542091openempi-2.0.5.ear-contents/openempi-webapp-web-2.0.5-exp.war/
14:38:19,778 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionFactoryFactory.buildTransactionFactory(34) | Transaction strategy: org.springframework.orm.hibernate3.SpringTransactionFactory
14:38:20,100 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionManagerLookupFactory.getTransactionManagerLookup(33) | No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
14:38:22,749 INFO [STDOUT] UserManagerImpl constructed
14:38:23,354 INFO [STDOUT] PersonManagerServiceImpl constructed
14:38:23,471 INFO [STDOUT] PersonQueryServiceImpl constructed
14:38:23,784 INFO [STDOUT] PersonManagerRemoteServiceImpl constructed
14:38:23,841 INFO [STDOUT] PersonQueryRemoteServiceImpl constructed
14:38:23,892 INFO [STDOUT] KeyServiceLocatorImpl constructed
14:38:23,912 INFO [STDOUT] TransformationServiceImpl constructed
14:38:24,362 INFO [STDOUT] Configuration constructed
14:38:26,180 INFO [STDOUT] ValidationServiceImpl constructed
14:38:26,199 INFO [STDOUT] ProbabilisticMatchingService constructed
14:38:26,228 INFO [STDOUT] BlockingServiceImpl constructed
14:38:26,277 INFO [STDOUT] BlockingBypassServiceImpl constructed
14:38:26,292 INFO [STDOUT] StringComparisonServiceImpl constructed
14:38:27,080 INFO [STDOUT] AuditEventServiceImpl constructed
14:38:27,244 INFO [STDOUT] DEBUG - org.hibernate.jdbc.AbstractBatcher.log(401) | select this_.audit_event_type_cd as audit1_1_0_, this_.audit_event_type_code as audit2_1_0_, this_.audit_event_type_description as audit3_1_0_, this_.audit_event_type_name as audit4_1_0_ from audit_event_type this_
14:38:27,245 INFO [STDOUT] Hibernate: select this_.audit_event_type_cd as audit1_1_0_, this_.audit_event_type_code as audit2_1_0_, this_.audit_event_type_description as audit3_1_0_, this_.audit_event_type_name as audit4_1_0_ from audit_event_type this_
14:38:29,341 INFO [STDOUT] KeyServerServiceImpl constructed
14:38:30,001 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionFactoryFactory.buildTransactionFactory(34) | Transaction strategy: org.springframework.orm.hibernate3.SpringTransactionFactory
14:38:30,003 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionManagerLookupFactory.getTransactionManagerLookup(33) | No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
14:38:30,304 INFO [STDOUT] UserManagerImpl constructed
14:38:30,348 INFO [STDOUT] PersonManagerServiceImpl constructed
14:38:30,379 INFO [STDOUT] PersonQueryServiceImpl constructed
14:38:30,392 INFO [STDOUT] PersonManagerRemoteServiceImpl constructed
14:38:30,404 INFO [STDOUT] PersonQueryRemoteServiceImpl constructed
14:38:30,413 INFO [STDOUT] KeyServiceLocatorImpl constructed
14:38:30,416 INFO [STDOUT] TransformationServiceImpl constructed
14:38:30,453 INFO [STDOUT] Configuration constructed
14:38:30,486 INFO [STDOUT] ValidationServiceImpl constructed
14:38:30,742 INFO [STDOUT] ProbabilisticMatchingService constructed
14:38:30,816 INFO [STDOUT] BlockingServiceImpl constructed
14:38:30,826 INFO [STDOUT] BlockingBypassServiceImpl constructed
14:38:30,829 INFO [STDOUT] StringComparisonServiceImpl constructed
14:38:30,869 INFO [STDOUT] AuditEventServiceImpl constructed
14:38:30,875 INFO [STDOUT] DEBUG - org.hibernate.jdbc.AbstractBatcher.log(401) | select this_.audit_event_type_cd as audit1_42_0_, this_.audit_event_type_code as audit2_42_0_, this_.audit_event_type_description as audit3_42_0_, this_.audit_event_type_name as audit4_42_0_ from audit_event_type this_
14:38:30,875 INFO [STDOUT] Hibernate: select this_.audit_event_type_cd as audit1_42_0_, this_.audit_event_type_code as audit2_42_0_, this_.audit_event_type_description as audit3_42_0_, this_.audit_event_type_name as audit4_42_0_ from audit_event_type this_
14:38:30,906 INFO [STDOUT] KeyServerServiceImpl constructed
14:38:32,415 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionFactoryFactory.buildTransactionFactory(34) | Transaction strategy: org.springframework.orm.hibernate3.SpringTransactionFactory
14:38:32,421 INFO [STDOUT] INFO - org.hibernate.transaction.TransactionManagerLookupFactory.getTransactionManagerLookup(33) | No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
14:38:32,765 INFO [STDOUT] UserManagerImpl constructed
14:38:32,846 INFO [STDOUT] PersonManagerServiceImpl constructed
14:38:32,871 INFO [STDOUT] PersonQueryServiceImpl constructed
14:38:32,884 INFO [STDOUT] PersonManagerRemoteServiceImpl constructed
14:38:33,002 INFO [STDOUT] PersonQueryRemoteServiceImpl constructed
14:38:33,008 INFO [STDOUT] KeyServiceLocatorImpl constructed
14:38:33,011 INFO [STDOUT] TransformationServiceImpl constructed
14:38:33,036 INFO [STDOUT] Configuration constructed
14:38:33,068 INFO [STDOUT] ValidationServiceImpl constructed
14:38:33,070 INFO [STDOUT] ProbabilisticMatchingService constructed
14:38:33,078 INFO [STDOUT] BlockingServiceImpl constructed
14:38:33,309 INFO [STDOUT] BlockingBypassServiceImpl constructed
14:38:33,312 INFO [STDOUT] StringComparisonServiceImpl constructed
14:38:33,351 INFO [STDOUT] AuditEventServiceImpl constructed
14:38:33,357 INFO [STDOUT] DEBUG - org.hibernate.jdbc.AbstractBatcher.log(401) | select this_.audit_event_type_cd as audit1_83_0_, this_.audit_event_type_code as audit2_83_0_, this_.audit_event_type_description as audit3_83_0_, this_.audit_event_type_name as audit4_83_0_ from audit_event_type this_
14:38:33,357 INFO [STDOUT] Hibernate: select this_.audit_event_type_cd as audit1_83_0_, this_.audit_event_type_code as audit2_83_0_, this_.audit_event_type_description as audit3_83_0_, this_.audit_event_type_name as audit4_83_0_ from audit_event_type this_
14:38:33,365 INFO [STDOUT] KeyServerServiceImpl constructed
14:38:33,482 INFO [EARDeployer] Started J2EE application: file:/C:/jboss/server/default/deploy/openempi-2.0.5.ear
14:38:33,483 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:service=EJB3,module=openempi-ejb-2.0.5.jar
State: FAILED
Reason: java.lang.IllegalStateException: Container jboss.j2ee:ear=openempi-2.0.5.ear,jar=openempi-ejb-2.0.5.jar,name=PersonManagerService,service=EJB3,VMID=1be0395c8ac2f5a9:-a9218d4:12af800b119:-7f8e + is already registered
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:service=EJB3,module=openempi-ejb-2.0.5.jar
State: FAILED
Reason: java.lang.IllegalStateException: Container jboss.j2ee:ear=openempi-2.0.5.ear,jar=openempi-ejb-2.0.5.jar,name=PersonManagerService,service=EJB3,VMID=1be0395c8ac2f5a9:-a9218d4:12af800b119:-7f8e + is already registered
14:38:33,850 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
14:38:34,018 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
14:38:34,142 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 1m:14s:646ms
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/561193#561193]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
[jBPM Development] - Does jBPM include sequence workflow and state machine workflow like window workflow foundation ?
by Dennis Chang
Dennis Chang [http://community.jboss.org/people/raindrop2010] created the discussion
"Does jBPM include sequence workflow and state machine workflow like window workflow foundation ?"
To view the discussion, visit: http://community.jboss.org/message/561037#561037
--------------------------------------------------------------
Does jBPM include sequence workflow and state machine workflow like window workflow foundation ?
If someone is familiar with windows workflow foundation, please have a look at the following problem:
WorkflowRuntime workflowRuntime = new WorkflowRuntime();
ExternalDataExchangeService dataExchangeService;
dataExchangeService = new ExternalDataExchangeService();
workflowRuntime.AddService(dataExchangeService);
PaymentProcessingService paymentProcessing;
paymentProcessing = new PaymentProcessingService();
dataExchangeService.AddService(paymentProcessing);
With the code above, our application can use paymentProcessing.RaiseXXXXEvent to interactive with the workflow instance. My question is : What's the principle to implement such a mechanism. I think this is a kind of *Event Driven Pattern*, but how can I implement this mechanism and why ? Please point me the direction or any references are appreciated. Any similar implemented in jBPM ?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/561037#561037]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
[JBoss ESB Development] - Message loss during shutdown or JMX stop of JMS Listener
by Dave Siracusa
Dave Siracusa [http://community.jboss.org/people/davesiracusa] created the discussion
"Message loss during shutdown or JMX stop of JMS Listener"
To view the discussion, visit: http://community.jboss.org/message/560276#560276
--------------------------------------------------------------
I'm looking into JMS message loss issues during shutdown. I enqueued several thousand mesages into an ESB application. While the messages were being processed I toggle(stop/start) lifecycle state for the jms listeners via JMX in order to simulate shutdown. I noticed periodic warnings in the serverlog (listing 1). The final tally indicated message loss. I believe I found a bug in ESB. Basically when a doStop (JMXConsole) is called it sets state to STOPPING and immediately terminates the executor thread (MessageAwareListener.java). If the thread was currently processing a mesage bad things happen. I use transcated queues and it appears the JMS message transaction evaporates and the message is lost. I added some code to AbstractThreadedManagedLifecycle.java to remedy the issue.
AbstractThreadedManagedLifecycle.java
---------------------------------------
protected void doStop()
throws ManagedLifecycleException
{
runningLock.lock() ;
try
{
if (isRunning())
{
setRunning(ManagedLifecycleThreadStatae.STOPPING) ;
}
// Dave Siracusa -start
if (!waitUntilStopped())
{
throw new ManagedLifecycleException("Thread still active!") ;
} // Dave Siracusa - end
}
finally
{
runningLock.unlock() ;
}
}
MessageAwareListener.java
---------------------------
protected void doStop()
throws ManagedLifecycleException
{
super.doStop();
_execService.shutdown() ;
}
Listing 1
----------
2010-09-01 15:04:40,924 WARN [org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle] (Thread-200) Unexpected error from doRun()
java.util.concurrent.RejectedExecutionException
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecutionThreadPoolExecutor.java:1768)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:359)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:253)
at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
at java.lang.Thread.run(Thread.java:619)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560276#560276]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months