It's not a secret anymore!
The moose likes EJB and other Java EE Technologies and the fly likes OutOfMemoryError with J2EE and JMS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "OutOfMemoryError with J2EE and JMS" Watch "OutOfMemoryError with J2EE and JMS" New topic

OutOfMemoryError with J2EE and JMS

John Adams

Joined: Jul 18, 2001
Posts: 3
I have been trying to set up a JMS running on two machines, with the J2EE server on one machine, and a client on each. JMS works fine on the machine which also hosts the server, but when I connect a client machine and try to make a connection to the Context.lookup() method:
topicConnectionFactory = (TopicConnectionFactory)jndiContext.lookup("TopicConnectionFactory");
I run out of memory with the following error:
Exception occurred during event dispatching:
<<no stack trace available>>
Process exit...
It appears that, in order to issue objects across the network, the j2ee system needs to load in a whole load of code and other
objects to achieve this. This takes up too much memory on my system. I have tried all the obvious things, like making sure the Java virtual machine has a minimum amount of memory and that other applications are shut down. This hasn't worked.
Any suggestions? Any workarounds? I am running on PC's (Win2k, NT) with up to 256Mb RAM. If I need more memory, how much would suffice?
I agree. Here's the link:
subject: OutOfMemoryError with J2EE and JMS
It's not a secret anymore!