[Design of JBoss jBPM] - Re: slf4j linking error ?
by thomas.diesler＠jboss.com
This is the 'mvn dependency:tree' I used to run the test
| [INFO] ------------------------------------------------------------------------
| [INFO] Building JBoss jBPM3 - Core
| [INFO] task-segment: [dependency:tree]
| [INFO] ------------------------------------------------------------------------
| [INFO] [dependency:tree]
| [INFO] org.jbpm.jbpm3:jbpm-core:jar:3.3.0-SNAPSHOT
| [INFO] +- bsh:bsh:jar:1.3.0:compile
| [INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
| [INFO] +- dom4j:dom4j:jar:1.6.1:compile
| [INFO] +- javax.jcr:jcr:jar:1.0.1:provided
| [INFO] +- javax.mail:mail:jar:1.4:provided
| [INFO] | \- javax.activation:activation:jar:1.1:provided
| [INFO] +- javax.servlet:servlet-api:jar:2.5:provided
| [INFO] +- junit:junit:jar:3.8.1:compile
| [INFO] +- org.apache.ant:ant:jar:1.7.0:compile
| [INFO] | \- org.apache.ant:ant-launcher:jar:1.7.0:compile
| [INFO] +- org.apache.jackrabbit:jackrabbit-core:jar:1.4.5:compile
| [INFO] | +- concurrent:concurrent:jar:1.3.4:compile
| [INFO] | +- commons-collections:commons-collections:jar:3.1:compile
| [INFO] | +- org.apache.jackrabbit:jackrabbit-api:jar:1.4:compile
| [INFO] | +- org.apache.jackrabbit:jackrabbit-jcr-commons:jar:1.4:compile
| [INFO] | +- org.apache.jackrabbit:jackrabbit-spi-commons:jar:1.4:compile
| [INFO] | +- org.apache.jackrabbit:jackrabbit-spi:jar:1.4:compile
| [INFO] | +- org.apache.jackrabbit:jackrabbit-text-extractors:jar:1.4:compile
| [INFO] | | +- org.apache.poi:poi:jar:3.0.2-FINAL:compile
| [INFO] | | +- pdfbox:pdfbox:jar:0.6.4:compile
| [INFO] | | +- org.textmining:tm-extractors:jar:0.4:compile
| [INFO] | | +- nekohtml:nekohtml:jar:0.9.4:compile
| [INFO] | | \- xerces:xercesImpl:jar:2.6.2:compile
| [INFO] | | \- xml-apis:xml-apis:jar:1.3.02:compile
| [INFO] | +- org.apache.lucene:lucene-core:jar:2.2.0:compile
| [INFO] | \- org.apache.derby:derby:jar:10.2.1.6:compile
| [INFO] +- org.hibernate:hibernate:jar:3.2.6.ga:compile
| [INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
| [INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
| [INFO] | +- asm:asm-attrs:jar:1.5.3:compile
| [INFO] | +- antlr:antlr:jar:2.7.6:compile
| [INFO] | +- cglib:cglib:jar:2.1_3:compile
| [INFO] | \- asm:asm:jar:1.5.3:compile
| [INFO] +- org.slf4j:slf4j-api:jar:1.5.5:compile
| [INFO] +- dumbster:dumbster:jar:1.6:test
| [INFO] +- jaxen:jaxen:jar:1.1.1:test
| [INFO] | +- jdom:jdom:jar:1.0:test
| [INFO] | \- xom:xom:jar:1.0:test
| [INFO] | +- xerces:xmlParserAPIs:jar:2.6.2:test
| [INFO] | +- xalan:xalan:jar:2.6.0:test
| [INFO] | \- com.ibm.icu:icu4j:jar:2.6.1:test
| [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.5:test
| [INFO] +- hsqldb:hsqldb:jar:1.8.0.7:test
| [INFO] \- log4j:log4j:jar:1.2.14:test (scope not updated to runtime)
| [INFO] ------------------------------------------------------------------------
| [INFO] BUILD SUCCESSFUL
| [INFO] ------------------------------------------------------------------------
|
Note, it uses sl4j-1.5.5
| [tdiesler@tdvaio trunk]$ svn log -v -r2585
| ------------------------------------------------------------------------
| r2585 | thomas.diesler(a)jboss.com | 2008-10-22 16:09:27 +0200 (Wed, 22 Oct 2008) | 1 line
| Changed paths:
| M /jbpm3/trunk/modules/core/pom.xml
| M /jbpm3/trunk/pom.xml
|
| [JBPM-1720] update to sl4j-1.5.5
|
With sl4j-1.5.5 in place the issue does not show any more - for me.
Also see
https://jira.jboss.org/jira/browse/JBPM-1720
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183889#4183889
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183889
16 years
[Design of JBoss jBPM] - slf4j linking error ?
by tom.baeyens＠jboss.com
I'm going to fix the JcrDbTest. This is the exception it currently generates:
Did anyone see such a problem before? It seems like a library incompatibility problem to me between slf4j and log4j.
java.lang.NoSuchFieldError: name
| at org.slf4j.impl.Log4jLoggerAdapter.<init>(Log4jLoggerAdapter.java:75)
| at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:75)
| at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:92)
| at org.apache.jackrabbit.core.config.RepositoryConfig.<clinit>(RepositoryConfig.java:64)
| at org.jbpm.jcr.jackrabbit.JackrabbitJcrServiceFactory.getRepository(JackrabbitJcrServiceFactory.java:48)
| at org.jbpm.jcr.impl.AbstractJcrServiceFactory.openService(AbstractJcrServiceFactory.java:46)
| at org.jbpm.svc.Services.getService(Services.java:156)
| at org.jbpm.jcr.JcrDbTest.testJcrNodeStorageAndRetrieval(JcrDbTest.java:55)
| 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:585)
| at junit.framework.TestCase.runTest(TestCase.java:154)
| at org.jbpm.AbstractJbpmTestCase.runTest(AbstractJbpmTestCase.java:57)
| at junit.framework.TestCase.runBare(TestCase.java:127)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:118)
| at junit.framework.TestSuite.runTest(TestSuite.java:208)
| at junit.framework.TestSuite.run(TestSuite.java:203)
| at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
| at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
| at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183883#4183883
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183883
16 years
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Ordering Group -- Transaction Scenario Analysis (Typical
by timfox
"gaohoward" wrote :
| Message grouping guarantee all the messages in a group goes to one consumer.
| But ordering group is different, it guarantees messages being sent out one by one, it doesn't really care who receives the message.
|
|
[Just discussed with Howard on IRC]
I think they're very closely related.
With message grouping, then all messages with the same group_id go to the same consumer as long as the consumer is not closed. If that consumer is closed the server will choose another consumer.
So it seems to me that message groups already provide ordering groups functionality.
The slight difference with message groups is all messages for that group go to the same consumer as long as that consumer is not closed.
Where, with the ordering groups, you would only need to send messages to the same consumer as long as there are no unacked for that consumer, so you could end up round robining.
Although in practice, the latter would not be strictly necessary to fulfil the requirements.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183831#4183831
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183831
16 years
[Design of EJB 3.0] - @EJB injection in Service uses incorrect business interface
by jaikiran
I have been trying to come up with a test case for this user reported issue https://jira.jboss.org/jira/browse/EJBTHREE-1530
I noticed that we already have a similar testcase in our testsuite org.jboss.ejb3.test.service.unit.ServiceUnitTestCase.testCreationOrder
While trying to setup this up (with the latest EJB3 1.0.0 Beta5 which was released), i noticed that the service-test.jar fails to deploy resulting in 5 ERRORS and 1 FAILURE as can been seen in Hudson http://jboss.hudson.alrubinger.com/job/EJB3_Integration_TestSuite_AS_TRUN...
On debugging, i found that one of the issues is in the @EJB injection in
| package org.jboss.ejb3.test.service
|
| @Service (objectName = "jboss.ejb3:management=interface,with=customName,is=serviceThree")
| @Management(ServiceThreeManagement.class)
| @Depends ({"jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3","jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3,type=ManagementInterface"})
| public class ServiceThree implements ServiceThreeManagement
| {
| @EJB
| private ServiceOneRemote serviceOne;
| ....
|
| }
|
For some reason, the injection module is trying to inject an object from remote-org.jboss.ejb3.test.service.ServiceOneRemote instead of ServiceOne/remote-org.jboss.ejb3.test.service.ServiceOneRemote. As a result, the deployment of the jar file fails with
2008-10-22 15:13:33,438 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.ejb3.test.service.ServiceThree/serviceOne into property org.jboss.ejb3.test.service.ServiceThree.serviceOne: remote-org.jboss.ejb3.test.service.ServiceOneRemote not bound
| 2008-10-22 15:13:33,454 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:82)
| 2008-10-22 15:13:33,454 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:99)
| 2008-10-22 15:13:33,454 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:89)
| 2008-10-22 15:13:33,470 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:61)
| 2008-10-22 15:13:33,470 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.ejb3.service.ServiceContainer.injectDependencies(ServiceContainer.java:531)
| 2008-10-22 15:13:33,470 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.ejb3.service.ServiceContainer.lockedStart(ServiceContainer.java:252)
| 2008-10-22 15:13:33,470 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:869)
| 2008-10-22 15:13:33,485 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| 2008-10-22 15:13:33,485 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| 2008-10-22 15:13:33,485 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| 2008-10-22 15:13:33,485 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at java.lang.reflect.Method.invoke(Method.java:585)
| 2008-10-22 15:13:33,501 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at
|
| .....
|
| 2008-10-22 15:13:34,126 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) Caused by: javax.naming.NameNotFoundException: remote-org.jboss.ejb3.test.service.ServiceOneRemote not bound
| 2008-10-22 15:13:34,126 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jnp.server.NamingServer.getBinding(NamingServer.java:764)
| 2008-10-22 15:13:34,142 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at org.jnp.server.NamingServer.getBinding(NamingServer.java:772)
| 2008-10-22 15:13:34,142 ERROR [STDERR] (RMI TCP Connection(6)-172.21.16.102) at
|
|
|
Here's the deployment time logs which shows that the ServiceOne supplies ServiceOne/remote-org.jboss.ejb3.test.service.ServiceOneRemote whereas ServiceThree demands remote-org.jboss.ejb3.test.service.ServiceOneRemote:
| 2008-10-22 17:05:22,772 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Created KernelDeployment for: service-test.jar
| 2008-10-22 17:05:22,772 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceFive,service=EJB3
| 2008-10-22 17:05:22,772 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:22,788 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:22,788 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.j2ee:jar=service-test.jar,name=ServiceFour,service=EJB3,type=ManagementInterface
| 2008-10-22 17:05:22,788 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb3:is=serviceThree,management=interface,with=customName
| 2008-10-22 17:05:22,788 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:22,804 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:22,804 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceFive/remote
| 2008-10-22 17:05:22,804 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceFiveManagement
| 2008-10-22 17:05:22,804 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceFive,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:22,819 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceFive,service=EJB3
| 2008-10-22 17:05:22,819 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceFour,service=EJB3
| 2008-10-22 17:05:22,819 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:22,819 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:22,819 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb3:is=serviceThree,management=interface,with=customName
| 2008-10-22 17:05:22,819 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:22,835 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:22,835 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceFour/remote
| 2008-10-22 17:05:22,835 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceFourManagement
| 2008-10-22 17:05:22,835 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceFour,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:22,851 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceFour,service=EJB3
| 2008-10-22 17:05:22,851 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3
| 2008-10-22 17:05:22,851 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:22,851 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:22,851 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) persistence.unit:unitName=#test
| 2008-10-22 17:05:22,866 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.StatelessRemote
| 2008-10-22 17:05:22,866 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:22,866 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:22,866 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceOne/remote-org.jboss.ejb3.test.service.ServiceOneRemote
| 2008-10-22 17:05:22,882 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceOneRemote
| 2008-10-22 17:05:22,882 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceOneLocal
| 2008-10-22 17:05:22,882 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceOne/remote
| 2008-10-22 17:05:22,882 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceOne/local-org.jboss.ejb3.test.service.ServiceOneLocal
| 2008-10-22 17:05:22,897 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceOne/local
| 2008-10-22 17:05:22,897 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceOneManagement
|
| 2008-10-22 17:05:22,897 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:22,897 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3
| 2008-10-22 17:05:22,897 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceSeven,service=EJB3
| 2008-10-22 17:05:22,913 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:22,913 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:22,913 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:22,913 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:22,913 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceSeven/local-org.jboss.ejb3.test.service.ServiceSevenLocal
| 2008-10-22 17:05:22,929 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceSevenLocal
| 2008-10-22 17:05:22,929 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceSeven/remote-org.jboss.ejb3.test.service.ServiceSevenRemote
| 2008-10-22 17:05:22,929 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceSeven/remote
| 2008-10-22 17:05:22,929 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceSevenManagement
| 2008-10-22 17:05:22,944 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceSeven/local
| 2008-10-22 17:05:22,944 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceSevenRemote
| 2008-10-22 17:05:22,944 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceSeven,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:22,944 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceSeven,service=EJB3
| 2008-10-22 17:05:22,944 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceSix,service=EJB3
| 2008-10-22 17:05:22,960 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:22,960 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:22,960 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/local
| 2008-10-22 17:05:22,960 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/remote
| 2008-10-22 17:05:22,976 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:22,976 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:22,976 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:serviceSix/local
| 2008-10-22 17:05:22,976 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceSixRemote
| 2008-10-22 17:05:22,991 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceSix/remote
| 2008-10-22 17:05:22,991 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceSixLocal
| 2008-10-22 17:05:22,991 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceSix,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:22,991 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceSix,service=EJB3
| 2008-10-22 17:05:22,991 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceThree,service=EJB3
| 2008-10-22 17:05:23,007 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,007 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,007 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceOneRemote
| 2008-10-22 17:05:23,007 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3,type=ManagementInterface
| 2008-10-22 17:05:23,007 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3
| 2008-10-22 17:05:23,022 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,022 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:remote-org.jboss.ejb3.test.service.ServiceOneRemote
| 2008-10-22 17:05:23,022 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,022 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceThree/remote
| 2008-10-22 17:05:23,038 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceThreeManagement
|
| 2008-10-22 17:05:23,038 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceThree,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,038 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceThree,service=EJB3
| 2008-10-22 17:05:23,038 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3
| 2008-10-22 17:05:23,038 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,054 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,054 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3,type=ManagementInterface
| 2008-10-22 17:05:23,054 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,054 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,069 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:serviceTwo/remote
| 2008-10-22 17:05:23,069 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceTwo/remote-org.jboss.ejb3.test.service.ServiceTwoRemote
| 2008-10-22 17:05:23,069 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceTwo/local
| 2008-10-22 17:05:23,069 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceTwo/local-org.jboss.ejb3.test.service.ServiceTwoLocal
| 2008-10-22 17:05:23,085 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:ServiceTwo/remote
| 2008-10-22 17:05:23,085 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceTwoRemote
| 2008-10-22 17:05:23,085 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.ServiceTwoLocal
| 2008-10-22 17:05:23,085 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,101 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3
| 2008-10-22 17:05:23,101 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=Session,service=EJB3
| 2008-10-22 17:05:23,101 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,101 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,101 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3,type=ManagementInterface
| 2008-10-22 17:05:23,101 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,116 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,116 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:Session/remote-org.jboss.ejb3.test.service.SessionRemote
| 2008-10-22 17:05:23,116 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.SessionRemote
| 2008-10-22 17:05:23,116 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:Session/remote
| 2008-10-22 17:05:23,132 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=Session,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,132 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=Session,service=EJB3
| 2008-10-22 17:05:23,132 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=SessionBean,service=EJB3
| 2008-10-22 17:05:23,132 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,132 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,147 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,147 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,147 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.SessionRemote
| 2008-10-22 17:05:23,147 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:SessionBean/remote
| 2008-10-22 17:05:23,163 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:SessionBean/remote-org.jboss.ejb3.test.service.SessionRemote
| 2008-10-22 17:05:23,163 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=SessionBean,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,163 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=SessionBean,service=EJB3
| 2008-10-22 17:05:23,163 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=StatelessBean,service=EJB3
| 2008-10-22 17:05:23,163 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,179 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,179 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,179 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,179 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/local
| 2008-10-22 17:05:23,194 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/local-org.jboss.ejb3.test.service.StatelessLocal
| 2008-10-22 17:05:23,194 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/remote
| 2008-10-22 17:05:23,194 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:StatelessBean/remote-org.jboss.ejb3.test.service.StatelessRemote
| 2008-10-22 17:05:23,194 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.StatelessRemote
| 2008-10-22 17:05:23,210 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.StatelessLocal
| 2008-10-22 17:05:23,210 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=StatelessBean,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,210 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=StatelessBean,service=EJB3
| 2008-10-22 17:05:23,210 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:jar=service-test.jar,name=TestResourceInjectionService,service=EJB3
| 2008-10-22 17:05:23,210 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with dependencies:
| 2008-10-22 17:05:23,226 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and demands:
| 2008-10-22 17:05:23,226 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.ejb:service=EJBTimerService
| 2008-10-22 17:05:23,226 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jboss.mq.destination:name=testTopic,service=Topic
| 2008-10-22 17:05:23,226 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and supplies:
| 2008-10-22 17:05:23,241 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Class:org.jboss.ejb3.test.service.TestResourceInjectionServiceIF
| 2008-10-22 17:05:23,241 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) jndi:TestResourceInjectionService/remote
| 2008-10-22 17:05:23,241 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:jar=service-test.jar,name=TestResourceInjectionService,service=EJB3) to KernelDeployment of: service-test.jar
| 2008-10-22 17:05:23,241 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:jar=service-test.jar,name=TestResourceInjectionService,service=EJB3
|
|
As an workaround (to move forward with my testing), i added a mappedName attribute to the @EJB injection:
| @Service (objectName = "jboss.ejb3:management=interface,with=customName,is=serviceThree")
| @Management(ServiceThreeManagement.class)
| @Depends ({"jboss.j2ee:jar=service-test.jar,name=ServiceTwo,service=EJB3","jboss.j2ee:jar=service-test.jar,name=ServiceOne,service=EJB3,type=ManagementInterface"})
| public class ServiceThree implements ServiceThreeManagement
| {
| // workaround: Inject default business interface through mappedName
| @EJB (mappedName="ServiceOne/remote")
| private ServiceOneRemote serviceOne;
| ...
| }
|
|
This deployed the jar fine and the testcase ERRORS came down by 2 (so now i have 3 ERRORS and 1 Failure on my local setup with this workaround. Testcase: testServiceDependencyInjectionAndInterception and Testcase: testDependsInjection now pass).
I'll continue to see if i can figure out why the injection isn't using the correct jndi-name.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183822#4183822
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183822
16 years
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Ordering Group -- Transaction Scenario Analysis (Typical
by gaohoward
"jhalliday" wrote : anonymous wrote : In this case, even the success of this commit doesn't mean that M1 is completed regarding ordering group rule, Simply because there may be other XA resources (XAResDB in this case) whose commit() may fail. JMS must not permit the deliver of M2 at this point of time and must be always aware of any recovery in the future. This means JMS server should not forget the M1 at this point.
|
| I respectfully disagree with that view. What you are suggesting is basically building automated heuristic outcome handling into the resource manager. It's incredibly difficult to do in a robust and correct manner and it's simply not worth the overhead.
|
| That said, there may, depending on the the isolation level used by the db, be a limited benefit to blocking M2 until an afterCompletion notification, provided it's done using in-memory (i.e. transient) data only.
I agree. I'll go first the simple one. That is we forget M1 after the commit() on JMS XA resource and deliver M2.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183803#4183803
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183803
16 years