| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Repost: Application Log file full |
« View previous topic :: View next topic » |
| Author |
Message
|
| rtrabucc |
 Posted: Thu Jun 27, 2002 9:55 am Post subject: Repost: Application Log file full |
 |
|
Novice
Joined: 22 May 2002
Posts: 16
Location: Bedford MA
|
I'm still getting this error. I thought I had solved the problem but no such luck. Anybody have a clue?
Original post:
I'm running some pub/sub load tests and in the middle, the tests die with a JMS5053 error. When I check the broker machine, there is a dialog box telling me the application log file is full.
I have boosted every log file parameter I can find. I'm using 62 primary and 61 secondary and 4095 (X4)M.
My question is, how do I clean up the log files. I tried deleting them, but that just causes the queue manager not to start. I've search around in explorer, but the answer is still escaping me. I've tried deleting the queues between the broker and the queue manager, but that didn't work either.
I'm running on NT, 5.3 Beta.
Thanks!
Bob |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Thu Jun 27, 2002 11:49 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Are you sure it is an MQ log that is full?
Try looking at the NT event viewer. (Start->Programs->Administrative Tools->Event Viewer) Look at the settings and enable overwrite events as needed, or just clear the log.
I don't know what JMS5053 is so I may have the wrong end of the stick.
Cheers,
Vicky |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Jun 28, 2002 8:54 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I'd also suggest catching the linked exception to see if it gives a clearer indicator of what is wrong:
} catch( JMSException je ) {
/*******************************************/
/* Catch and display exception information */
/*******************************************/
System.out.println("JMSException: " + je);
Exception le = je.getLinkedException();
if (le != null) System.out.println("Linked exception: " + le);
} |
|
| Back to top |
|
|
| rtrabucc |
| Posted: Fri Jun 28, 2002 9:14 am Post subject: Anyone else? |
|
|
Novice
Joined: 22 May 2002
Posts: 16
Location: Bedford MA
|
Well thanks, I tried that to see if it would fix the problem. No luck. Although I'm suspicious that the event log might get filled because of something happening with the pub/su broker. It is FILLED with messages about it.
MQJMS5053 is the 'No Broker response' message that I commonly see when something is wrong with the pub/sub broker. However because I'm a newbie, I don't have any clue how to debug what the problem currently is with the broker.
Is there a pub/sub broker log file? This only seems to happen when I boost my tests up above 50 publishers and 50 subscribers and start pushing 100 publishers and 100 subscribers.
Bob |
|
| Back to top |
|
|
| rtrabucc |
| Posted: Fri Jun 28, 2002 9:16 am Post subject: |
|
|
Novice
Joined: 22 May 2002
Posts: 16
Location: Bedford MA
|
I also catch the exception, but all it tells we is that when trying to open a subscription, the .getBrokerResponse failed.
Bob |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
