OpenJMS lock-up

[Guest]

At the site where I work, we are using OpenJMS to process 16000 message
an hour. However, it appears that OpenJMS will lock-up after having
processed a large number of requests and no messages will be further
processed. This situation is corrected when OpenJMS is restarted and
then everything will continue processing correctly. However, this
situation obviously cannot work in a Production environment.

Here is the environment where OpenJMS is used in Production:
Red Hat Enterprise Linux 4
Java 1.4.2
OpenJMS 0.7.6.1

Has anyone observed this issue occurring on OpenJMS when processing a
large volume of messages?
Is there any reliable fix to this other than restarting OpenJMS?

 

[robert]

(e-mail address removed) escreveu:

At the site where I work, we are using OpenJMS to process 16000 message
an hour. However, it appears that OpenJMS will lock-up after having
processed a large number of requests and no messages will be further
processed. This situation is corrected when OpenJMS is restarted and
then everything will continue processing correctly. However, this
situation obviously cannot work in a Production environment.

Here is the environment where OpenJMS is used in Production:
Red Hat Enterprise Linux 4
Java 1.4.2
OpenJMS 0.7.6.1

Has anyone observed this issue occurring on OpenJMS when processing a
large volume of messages?
Is there any reliable fix to this other than restarting OpenJMS?

Although I've used OpenJMS I can only give general advice to try
capturing the /var/log/messages errors. What does the OpenJMS logs say,
do they just stop? Try capturing vmstat to see if its memory related.
Is there a jvm error?

My biggest hint would be to use the java service wrapper with openJMS -
there are scripts around which combine the two nicely. The java service
wrapper (creates a jvm daemon on *nix) has a JNI layer that pings the
JVM and will detect any openjms failures and do auto recover. The java
service wrapper uses the jvm hooks starting in 1.3 and may help you
track down the provblem. I do recall openjms being a bit flaky but
never reached the volume you're referring to.

If you decide to go the daemon route with openjms you'll have your
subscriber / queue that implements WrapperListener . My publisher was
inside a war so not sure off the top of my head how that would work. I
seem to remember that openjms needs tomcat to run - there's a daemon
for that too.

BTW, are you using the rmi connector?

HTH,
Robert
http://www.braziloutsource.com/

 

[Scott Ellsworth]

At the site where I work, we are using OpenJMS to process 16000 message
an hour. However, it appears that OpenJMS will lock-up after having
processed a large number of requests and no messages will be further
processed.

This sounds painful. Have you tried ActiveMQ? It gave me good results
when I tried posting and draining 100k messages. (No association, just
a happy customer.)

Scott