| Author |
Message
|
| kriersd |
 Posted: Tue Oct 19, 2004 6:51 am Post subject: MQ Java App Running on Win2003 Hangs |
 |
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Hello Folks,
I have a major problem that I just can't seem to figure out. We just upgraded our OS to Windows 2003 server and I have a java application that is having problems ever since the upgrade. It seems strange that the application starts up and runs just fine for hours and then all of the sudden it just stops responding. The CPU and memory are not showing any problems at the time it stops responding. The application is so locked up that I can't even get a (ctl + break) java dump. We placed some additional logging in the application just to see what line of code it's stuck on. The logging always indicates that it is in the MQSeries API waiting for a message to arrive on the queue. Has anyone had a problem like this before.
This java application is polling for a new message every 5 seconds, just in case that makes any difference.
Version information
MQ 5.3 CSD 7
Windows 2003 Enterprise Edition
IBM JDK 1.3
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Tue Oct 19, 2004 9:55 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
When it is 'hung', what happens to the app if you put a message on the queue it is reading? Does it read it? Are you sure it is not doing a get with wait-forever?
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Oct 19, 2004 11:37 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Hi RogerLacroix,
Yeah, I am sure it's not in a "Get With Wait". For one if it was in a get with wait then I should be able to get a java core dump. The wierd thing is that when it happens the swing gui won't even display. I end up having to end the java process, thus killing the application.
It's funny because I can't recreate the problem at will. I have to let it happen and then try to debug it. This makes it much worse to debug.
Strange but real problem.
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Oct 19, 2004 12:16 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| Try a newer JRE, 1.3.0 is getting quite old now.... Try the sun one also, 1.4.2, don't use 5 yet... |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Oct 19, 2004 1:05 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Oct 19, 2004 2:17 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
The Swing compnent ONLY has 1 event queue (this has nothing to do with MQ). Therefore, your application and Swing components will run as within ONE thread unless you multi-thread your application.
You should be running AT LEAST 2 threads and NEVER do get wait-forever when you are coding GUI applications.
I have done extensive coding and testing with Java / Swing / MQ and this smells like you are either doing a get wait-forever or you blew up Swing.
Run your applications from a command prompt with 'java' and not 'javaw' and see if Swing spews the exception stack when it blows up.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Oct 20, 2004 11:21 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Well, I do know for sure that we are not doing a get with wait for ever, but I don't know for sure if the swing gui took an error. The java councel didn't show any errors, but that may not mean much. The strange thing is that this applicatioin has ran for years without the same problem on the NT platform. It sure is strange that it is happening on the Windows 2003 server. The only thing we changed ouside of the platform is the queue manager. We upgraded to version 5.3 at the same time we migrated to the new Windows 2003 server.
We have changed the JDK to SUN's version 1.4, and so far the error has yet to show up.
I'll keep you posted.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
