Could not store message: 127 msg=90 hard NOT_STORED PERSISTE

[krishnad2468]

Hi,

We are using jboss-3.2.1 server and MDB's. Message driven beans are running for a while and today i got this error. This is the first i am seeing error. I am not sure why i am getting this error. Can any one have any idea why will get this error? I searched on google and i didn't find any proper solution for this problem. I will appriciate for any help.

Stack trace:
***********************


javax.ejb.EJBException: null; CausedByException is:
Could not store message: 127 msg=90 hard NOT_STORED PERSISTENT queue=QUEUE.reportQueue priority=4 hashCode=779642058; - nested throwable: (org.jboss.util.NestedSQLException: No ManagedConnections Available!; - nested throwable: (javax.resource.ResourceException: No ManagedConnections Available!))

STACKTRACE =
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.ServerException: EJBException:; nested exception is:
javax.ejb.EJBException: null; CausedByException is:
Could not store message: 127 msg=90 hard NOT_STORED PERSISTENT queue=QUEUE.reportQueue priority=4 hashCode=779642058; - nested throwable: (org.jboss.util.NestedSQLException: No ManagedConnections Available!; - nested throwable: (javax.resource.ResourceException: No ManagedConnections Available!))
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java)
at sun.rmi.transport.Transport$1.run(Transport.java)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java)
at java.lang.Thread.run(Thread.java)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:135)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:87)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85

[krishnad2468]

Hi,

No one replied so far to my question? Can any one have any idea please?

Thanks.

[vgamerma]

We have the same issue. I believe it's due to use of HSQLDB. Currently investigating movign the backend data store for ConfigJBossMQDB to Oracle.

One thing I can't find an answer to is either this is available in 3.2.1. I am afraid we will have to migrate to at least 3.2.4.

http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB

Anybody can say for sure?

Thanks,
Val

[genman]

3.2.1 is full of bugs, many critical, so upgrading to 3.2.7 at least is your best bet.

[krishnad2468]

Hi Genmen,

You are saying jboss-3.2.1 is full of bugs. Full of bugs in what ? Full of bugs in supporting JMS?
We are using jboss-3.2.1. Can I configure JbossMQ to point to other database instead of Hypersonic?
Is upgrading jboss only the option to resolve my problem?

Thanks.

[genman]

Feel free to look at the release notes between 3.2.1 and 3.2.7. If you want a definite answer read the code, or pay money to a JBoss consultant.

[thebadpete]

I am also getting this issue in JBoss 4.0.1. And I am using MySQL database, not the default one. So it does seem like a lingering issue...

[adrian.brock]

Look just go read the FAQ and/or create a separate DataSource for jms
until you fix the connection leak in your application.

DO NOT HIJACK, CROSS POST OR ME TOO

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp