On Mon, 24 Jun 2002, Scott M Stark wrote:
> You are using an out of date beta. Go to sourceforge and get
> the latest 3.0.0 release.
Well... I tried to fix the problem before I start fighting
another problem that has appeared with testing the 3.0.0
release :)
The problem is following exception while deploying an EJB
application. It appears after "Deploying EJB" messages:
20:15:15,549 INFO [EjbModule] Deploying UserManager
20:15:15,616 INFO [EjbModule] Deploying OptionsBrowser
20:15:15,682 INFO [EjbModule] Deploying UserStudentManager
20:15:15,919 INFO [EjbModule] Deploying UserGraduateManager
20:15:16,003 INFO [EjbModule] Deploying UserTeacherManager
20:15:16,240 INFO [EjbModule] Deploying UserAdvocateManager
<snip>
returning ManagedConnection to pool:
javax.resource.ResourceException: Could not cleanup:
com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED command not allowed
within multi-statement transaction.
at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.cleanup(LocalManagedConnection.java:198)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java:137)
at
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:324)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection(BaseConnectionManager2.java:494)
at
org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener.connectionClosed(LocalTxConnectionManager.java:388)
at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.closeHandle(LocalManagedConnection.java:338)
at
org.jboss.resource.adapter.jdbc.local.LocalConnection.close(LocalConnection.java:97)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.safeClose(JDBCUtil.java:58)
at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:69)
at
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>(JDBCEntityBridge.java:103)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:332)
at
org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:155)
at org.jboss.ejb.EntityContainer.create(EntityContainer.java:337)
at org.jboss.ejb.Container.invoke(Container.java:789)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:894)
at $Proxy6.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:272)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy19.create(Unknown Source)
Because of changes in service descriptors I used an mssql-service.xml
from docs/jca/examples and changed the values for jdbc driver and
database information.
It happens with JBoss 3.0.0 on RH7.3 with Sybase ASE 11.0.0.3
and jConnect 5.2.
Does anybody have an idea what could I do with this?
Thanks
Pavel
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
