[JCA/JBoss] - Re: Integration with Oracle AQ via Sun Adapter
by ryandavid
Caused by: oracle.jms.AQjmsException: argomenti non validi nella chiamata
| at oracle.jms.AQjmsDBConnMgr.checkForSecurityException(AQjmsDBConnMgr.java:321)
| at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:541)
| at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:69)
| at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:163)
| at oracle.jms.AQjmsQueueConnectionFactory.createQueueConnection(AQjmsQueueConnectionFactory.java:108)
| at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createConnection(ManagedQueueConnectionFactory.java:60)
| at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:141)
| at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:122)
| ... 33 more
|
I debugged the aqapi.jar class file and I discovered that it is called the method createConnection (the first method that doesn't take user/password parameters) of AQjmsQueueConnectionFactory class.
So the problem should be in classes of sun adapter.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211404#4211404
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211404
17 years, 2 months
[EJB 3.0] - Deployment EJB3 5.0 GA migration
by horstL
hello all,
i have a question about migration from jboss 4.2.3GA to 5.0.0GA with EJB3.0 (about 300 EJB's)
my ear was working under 4.2.3GA without problems in 5.0.0GA i always get a Stackoverflow
the xml deployment descriptors
application.xml, jboss-app.xml, persistence.xml
are all fixed and corrected to the new version, the EJB3 is only annotated
the standard setup of my EJB beans is
Entity Bean (@Entity) / Entity Bean IF (no annotations)
EntityManager (as Stateless Session bean/ includes @PersistenceContext)
EntityManagerIF (only @Local)
ManagerBean (@Stateless with the business logic)
ManagerBeanIF (only @Remote)
now the question: how can i check where the problem is ?
| 2009-02-19 11:12:20,624 INFO [org.jboss.ejb3.EJBContainer] (HDScanner) STARTED EJB: at.test.persistence.xyzEM ejbName: xyzEM
| 2009-02-19 11:12:20,627 INFO [org.jboss.ejb3.session.SessionSpecContainer] (HDScanner) Stopping jboss.j2ee:ear=test.ear,jar=test.jar,name=xyzEM,service=EJB3
| 2009-02-19 11:12:20,628 INFO [org.jboss.ejb3.EJBContainer] (HDScanner) STOPPED EJB: at.test.persistence.xyzEM ejbName: xyzEM
| 2009-02-19 11:12:20,629 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Start: name=jboss.j2ee:ear=test.ear,jar=test.jar,name=xyzEM,service=EJB3 state=Create java.lang.StackOverflowError
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:69)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
|
|
in the old version of jboss there was always an info when an ear was deployed this is also missing now
br horst
PS: the overflow is not coming up on the same position of the deployment
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211391#4211391
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211391
17 years, 2 months