I have implemented a JBossMQ-driven JMS Queue which is answered by a
JBoss-managed pool of Message-Driven Beans; the deployment descriptor allows
the MDB to run in as many as 15 threads simultaneously, so there are usually
multiple instances of onMessage() running at once.
The problem which I'm
The formatting may make it unclear, so note that where I say "Remember to
enclose in ...", the formats should be, respectively:
|
|
|
|
|
|
and
|
|
|
|
|
|
View the original post :
http://www.jboss.com/index
For anyone else who might be having this problem: I think I have figured it out.
My initial conclusion was correct; JBoss was creating more message threads than
it had the heap capacity to support, causing an OutOfMemoryError. The minimum
and maximum number of message threads for a standard MDB
Hi,
I currently have a JBoss EJB application which employs 7 message queues using
MDBs with container-managed transactions, to which messages are posted via JNDI
from a stateless session bean within the same application. I have recently
begun encountering OutOfMemoryErrors during periods of he
One additional piece of information: sometimes, the stalled request eventually
fails and produces this exception:
| java.sql.SQLException: Closed Connection
| at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
| at oracle.jdbc.dbaccess.DBError.throwSqlExcep
I recently completed transitioning an RMI standalone application (which
operated via naming lookup on rmiregistry) to EJBs running under JBoss 4.0.3.
The application makes JDBC calls to a database in order to get user/login
information.
The problem is that, at seemingly random intervals, reque
