Error while deploying the ejb-management.jar (However this works on DB2 8.0 with driver DB2_v8.2_fp14)
2007-05-09 15:52:05,765 DEBUG [org.jboss.ejb.plugins.StatelessSessionInstancePool] Started jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/mgmt/MEJB
2007-05-09 15:52:05,765 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/mgmt/MEJB dependent components: []
2007-05-09 15:52:05,765 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionInterceptor] start called in CachedConnectionInterceptor
2007-05-09 15:52:05,765 DEBUG [org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin] select * from TIMERS
2007-05-09 15:52:05,906 WARN [org.jboss.ejb.txtimer.DatabasePersistencePolicy] Unable to get timer handles for containerId: jboss.j2ee:jndiName=ejb/mgmt/MEJB,service=EJB
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -351, SQLSTATE: 56084, SQLERRMC: 5
at com.ibm.db2.jcc.c.fg.e(fg.java:1596)
at com.ibm.db2.jcc.c.fg.a(fg.java:1225)
at com.ibm.db2.jcc.b.gb.n(gb.java:718)
at com.ibm.db2.jcc.b.gb.i(gb.java:255)
at com.ibm.db2.jcc.b.gb.c(gb.java:53)
at com.ibm.db2.jcc.b.w.c(w.java:46)
at com.ibm.db2.jcc.b.vb.h(vb.java:151)
at com.ibm.db2.jcc.c.fg.p(fg.java:1220)
at com.ibm.db2.jcc.c.fg.a(fg.java:1834)
at com.ibm.db2.jcc.c.fg.a(fg.java:473)
at com.ibm.db2.jcc.c.fg.executeQuery(fg.java:457)
at org.jboss.resource.adapter.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:171)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.selectTimers(GeneralPurposeDatabasePersistencePlugin.java:258)
at org.jboss.ejb.txtimer.DatabasePersistencePolicy.listTimerHandles(DatabasePersistencePolicy.java:165)
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 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 $Proxy29.listTimerHandles(Unknown Source)
at org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:408)
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 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.ejb.Container.restoreTimers(Container.java:771)
at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:410)
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)
db2 => ? SQL0351
SQL0351N An unsupported SQLTYPE was encountered in position
"<position-number>" of the output SQLDA (select
list).
Explanation: The element of the SQLDA at position
"<position-number>" is for a data type that either the
application requestor or the application server does not
support. If the application is not using the SQLDA directly,
"<position-number>" could represent the position of an element in
the select list or a parameter of a CALL statement.
The statement cannot be processed.
User Response: Change the statement to exclude the unsupported
data type. For a select statement, remove the names of any
columns in the select-list with the unsupported data type or use
a cast in the query to cast the column to a supported data
type.
sqlcode: -351
sqlstate: 56084
- is related to
-
JBPAPP-151 Error starting up JBossMQ default queues with db2-7.2
- Closed