Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / March 2006

Tip: Looking for answers? Try searching our database.

OpenJMS lock-up

Thread view: 
spammemore98@gmail.com - 06 Mar 2006 16:12 GMT
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 - 06 Mar 2006 20:22 GMT
> 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
[quoted text clipped - 11 lines]
> 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 - 06 Mar 2006 21:16 GMT
> 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

Signature

Scott Ellsworth
scott@alodar.nospam.com
Java and database consulting for the life sciences



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.