[JBoss Messaging] - EJB3 MDB and 1.2.0.Beta2
by asturn
I switched from 1.0.1.SP2 to 1.2.0.Beta2 and now my test application does not deploy any more:
| 08:50:29,395 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@16068c9(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1573872 destination=/queue/testQueue isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=20 maxSession=20 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=10000)
| java.lang.ClassCastException: org.jboss.jms.client.container.FailoverValveInterceptor cannot be cast to org.jboss.aop.advice.Interceptor
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:116)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$setExceptionListener_8089029433030319178.invokeNext(ClientConnectionDelegate$setExceptionListener_8089029433030319178.java)
| at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$setExceptionListener_8089029433030319178.invokeNext(ClientConnectionDelegate$setExceptionListener_8089029433030319178.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.setExceptionListener(ClientConnectionDelegate.java)
| at org.jboss.jms.client.JBossConnection.setExceptionListener(JBossConnection.java:117)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:140)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
| at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:359)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:305)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:589)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:619)
The problem seems to be a class cast exception with the aop:
| java.lang.ClassCastException: org.jboss.jms.client.container.FailoverValveInterceptor cannot be cast
| to org.jboss.aop.advice.Interceptor
|
Everything worked fine with 1.0.1.SP2 (JBoss 4.0.5GA with EJB3, JBoss Messaging 1.0.1.SP2 standard installation, jboss-messaging.jar from the jbossesb.sar copied to the lib directory of the server)
The test application is just a jar containing one MDB (very similar to the sample bean in the samples)
Best regards!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011764#4011764
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011764
19Â years, 2Â months
[Persistence, JBoss/CMP, Hibernate, Database] - DBCP pool Active connections / DB down
by muni78
Greetings,
I seems to have a strange problem with DBCP and Oracle Connection poll mechanism. Here how it goes.
I'm using Oracle 10g Database and my applicaiton is running on Tomcat 5.1 and my DBCP version is 1.2
1. Get Database connection from DBCP BasicDataSource ds
ex :- conn = ds.getConnection()
2. Create a Statement from conn, conn.createStatement()
3. Get ResultSet from Statement stmt, stmt.executeSql(sql)
4. Now, Shutdown the oracle DB or disconnect the client from Server (remove the Lan cable)
5. execute one more SQL query like stmt.executeSql(sql)
6. SQL Exception is thrown at during point 5 , like 17002:I/O error
7. Exception is occurred if i close the connection, conn.close(); (Error Code 0 and message is connection is already closed)
8. At this point, DBCP is not returning the connection to ideal pool, means Connection still has active status and we can check the active status from BasicDataSource like bs.getNumActive()
I think its bug with DBCP if now I hope someone can to light to solve this issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011733#4011733
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011733
19Â years, 2Â months