-
15. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Can you see java:/TransactionManager listed in the Naming panel of the admin gui?
-
16. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Well, in the status menu there is no 'JNDI View' option (EAP 6 or 7.1.1.Final)???
Ok, using 7.2.0.Alpha1-SNAPSHOT with 1.4.0.Final (management console?) there are some infos.
Looks not too bad or?
-
17. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
It exists under "Profile" in the top right under 7.1.1.
I seem to recall using 7.1.2 for my screenshot above however, which is (roughly) equivalent to EAP 6.0.0.
(Actually, I just checked and the screenshot is from 7.1.3.Final, but the JNDI view can be found somewhere in every version since at least 7.1.1.Final).
-
18. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Right, using EAP6 (7.1.2.Final-redhat-1) infos can be found at Container --> Transactions or Container --> Naming.
So whats next?
-
19. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
I suspect that you have polluted your application with an obsolete JBoss JNDI implementation.
Do you have a jar named jbossall-client.jar or jnp-client.jar buried in there somewhere?
Perhaps you can list all the jars in this particular application. Those in the EAR and more particularly any that are in embedded WAR/WEB-INF/lib directories.
-
20. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Just by the way, one of the first steps upgrading to AS 7 was removing the old jbossall-client.
Here the libs (ear and war; just removed some customer jars without jars inside):
EAR:
bowf-ejb-4.3.0-SNAPSHOT.jar
bowf-persistence-4.3.0-SNAPSHOT.jar
bowf-web-4.3.0-SNAPSHOT.war (war libs see below)
lib/antlr-2.7.6.jar
lib/aopalliance-1.0.jar
lib/axis-1.4.jar
lib/axis-jaxrpc-1.4.jar
lib/axis-saaj-1.4.jar
lib/axis-wsdl4j-1.5.1.jar
lib/bowf-ws-4.3.0-SNAPSHOT.jar
lib/commons-beanutils-1.7.0.jar
lib/commons-cli-1.1.jar
lib/commons-codec-1.2.jar
lib/commons-collections-3.2.jar
lib/commons-dbcp-1.4.jar
lib/commons-discovery-0.2.jar
lib/commons-httpclient-3.1.jar
lib/commons-lang-2.4.jar
lib/commons-pool-1.5.4.jar
lib/dom4j-1.6.1.jar
lib/ehcache-1.2.3.jar
lib/hibernate-commons-annotations-3.2.0.Final.jar
lib/hibernate-core-3.6.0.Final.jar
lib/hibernate-jpa-2.0-api-1.0.0.Final.jar
lib/joda-time-2.0.jar
lib/poi-3.5-FINAL.jar
lib/slf4j-api-1.6.4.jar
lib/slf4j-log4j12-1.6.4.jar
lib/spring-aop-3.1.2.RELEASE.jar
lib/spring-asm-3.1.2.RELEASE.jar
lib/spring-beans-3.1.2.RELEASE.jar
lib/spring-context-3.1.2.RELEASE.jar
lib/spring-core-3.1.2.RELEASE.jar
lib/spring-expression-3.1.2.RELEASE.jar
lib/spring-jdbc-3.1.2.RELEASE.jar
lib/spring-orm-3.1.2.RELEASE.jar
lib/spring-tx-3.1.2.RELEASE.jar
lib/spring-web-3.1.2.RELEASE.jar
lib/utils-1.07.00.jar
WAR:
WEB-INF/lib/antlr-2.7.2.jar
WEB-INF/lib/aopalliance-1.0.jar
WEB-INF/lib/commons-beanutils-1.7.0.jar
WEB-INF/lib/commons-chain-1.2.jar
WEB-INF/lib/commons-digester-1.8.jar
WEB-INF/lib/commons-validator-1.3.1.jar
WEB-INF/lib/dom4j-1.6.1.jar
WEB-INF/lib/hibernate-commons-annotations-3.2.0.Final.jar
WEB-INF/lib/hibernate-core-3.6.0.Final.jar
WEB-INF/lib/hibernate-jpa-2.0-api-1.0.0.Final.jar
WEB-INF/lib/jaxen-1.1.1.jar
WEB-INF/lib/joda-time-2.0.jar
WEB-INF/lib/jstl-1.0.jar
WEB-INF/lib/jta-1.1.jar
WEB-INF/lib/oro-2.0.8.jar
WEB-INF/lib/slf4j-api-1.6.4.jar
WEB-INF/lib/spring-aop-3.1.2.RELEASE.jar
WEB-INF/lib/spring-asm-3.1.2.RELEASE.jar
WEB-INF/lib/spring-beans-3.1.2.RELEASE.jar
WEB-INF/lib/spring-context-3.1.2.RELEASE.jar
WEB-INF/lib/spring-context-support-3.1.2.RELEASE.jar
WEB-INF/lib/spring-core-3.1.2.RELEASE.jar
WEB-INF/lib/spring-expression-3.1.2.RELEASE.jar
WEB-INF/lib/spring-struts-3.1.2.RELEASE.jar
WEB-INF/lib/spring-tx-3.1.2.RELEASE.jar
WEB-INF/lib/spring-web-3.1.2.RELEASE.jar
WEB-INF/lib/spring-webmvc-3.1.2.RELEASE.jar
WEB-INF/lib/struts-core-1.3.10.jar
WEB-INF/lib/struts-el-1.3.10.jar
WEB-INF/lib/struts-extras-1.3.10.jar
WEB-INF/lib/struts-taglib-1.3.10.jar
WEB-INF/lib/struts-tiles-1.3.10.jar
WEB-INF/lib/utils-1.07.00.jar
-
21. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
You have some duplication in the WAR which should probably be removed.
Make sure your maven plugins are up to date because the current maven-ear-plugin will normally sort this out for you by stripping duplicate jars from the WEB-INF/lib directories of any WAR files.
You should also declare jstl-1.0.jar, jta-1.1.jar and hibernate-jpa-2.0-api-1.0.0.Final.jar to be "provided".
I'd also try and lose that wizened old version of Axis as well.
I don't think that this would cause the JNDI lookup of the transaction manager to fail, however.
-
22. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Well, I cleaned the libs a bit and updated the ear-plugin to 2.8 (2.7 before).
This doesn't change anything BUT....
... now I am going completely mad after I realized that the application is running on 7.1.1.Final (don't know if I tried before).
EAP6 (7.1.2.Final) and 7.2.0.ALPHA-SNAPSHOT throwing the exception.
I compared standalone-full.xml
EAP6 (7.1.2 or later) is required due to customer/support reasons.
Tried to check the release notes but there are a heap of changes...
-
23. Re: Error on deployment - Unable to locate the transaction manager (EJB 2.x, hibernate 3.2.6, spring 2.5.6)
Well, to close this topic:
Fall back to 7.1.1.Final as this version is not so picky.
And moved back to spring 2.5 and hibernate 3 as well.
Maybe it was a mixture of some misconfiguration but I believe a jndi.properties in the ejb.jar was the bad guy.
And of course the jndi name for all the SimpleRemoteStatelessSessionProxyFactoryBean (bloody lazy spring stuff).
Then I had to undo all the changes I made cause of some documentation (and other topics here), which obviously doesn't fit my case.
Finally, deployment without errors/warnings on 7.1.1.Final. Basic funtionality tested without errors.
Switched to EAP6 (7.1.2.Final) and everything is fine as well.
Really a hard lesson....and at the end, "everything" depends on a clean jndi naming.
Thanks to all who "waste" some time on it.
