ed at that point. But
> such behavior is obviously non-deterministic and can lead to problems under
> high loads... But from what you wrote so far it doesn't sound like that's
> the problem you're having.)
>
> -Original Message-
> From: Neal Sanche [mailto:[EMA
Title: RE: [JBoss-user] JBoss 2.4.6 JMS Socket Leak
Hmmm. I'm not a JBoss developer exactly (I'm a "user"), so I probably can't help you a great deal here. Though your problem worries me since we are using JMS with JBoss as well.
This is another wild guess, but may
context? It could *theoretically* be
> > possible that the JNDI contexts accumulate too fast for the garbage
> > collector to keep up...?
> >
> > -Original Message-
> > From: Neal Sanche [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, June 03, 2002 6:50 PM
> &
d *theoretically* be
> possible that the JNDI contexts accumulate too fast for the garbage
> collector to keep up...?
>
> -Original Message-
> From: Neal Sanche [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 03, 2002 6:50 PM
> To: [EMAIL PROTECTED]
> Subject:
Title: RE: [JBoss-user] JBoss 2.4.6 JMS Socket Leak
This is just a wild guess (and maybe it really is a bug in JBoss...), but how about also closing the JNDI context? It could *theoretically* be possible that the JNDI contexts accumulate too fast for the garbage collector to keep up
Hi All,
I've been encountering socket leaks in JBoss 2.4.6 when running code similar
to the following to send JMS messages to topics on which Message Driven Beans
are listening.
public static void sendLogItem(int type, String message) {
TopicPublisher publisher = null;
Top
