| Author |
Message
|
| constantlearner |
 Posted: Fri Jan 08, 2010 8:51 pm Post subject: Log is full Error in Broker |
 |
|
Newbie
Joined: 08 Jan 2010
Posts: 8
|
Hi,
Im getting a strange problem in broker. I created a new default configuration in my env today and everything went fine. Then i imported my project from a different workspace to my new workspace and created bar file. When i deploy this bar file in my broker im getting 2012 log is full error and I can see 5 log files in
C:\Program Files\IBM\WebSphere MQ\log\WBRK61_DEFAULT_QUEUE_MANAGER\active
Each is having a size of 1024K. This may be because when the default q manager was created the primary was 3 and secondary was 2.
But my question here is why are the log files getting full when i have just deployed my bar file? There is no flow running or there is nothing thats logging at this instance. I read that when an infinite loop happens then the logs get full and we get such errors but in this case i have just deployed my bar file.
Also i havent created any queues in the Queue Manager and even if i create the queues, I will be keeping them Non Persistant.
Is this something to do with my flow? Any logic issues?
Thanks,
Antony |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sat Jan 09, 2010 3:39 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are a dozen or more reasons why the defaults used in WMQ are not really suitable for real messaging use.
You can increase the number of log files. Don't forget to restart the QM (plus broker etc) after you have done so.
The only time I ever use the default configuration is to use any of the samples provided with broker.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| constantlearner |
| Posted: Sat Jan 09, 2010 10:21 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 8
|
Thanks for the reply.
I increased my log # of log files to Primary - 40 and secondary - 20 and restarted QM. Now when i deploy my bar file and give a run, i can see the 15 log files getting created at one go 
Not sure if my flow is in loop, this is the third time im creating this default configuration |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jan 09, 2010 10:48 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Can you explain exactly what you are doing. Also please let us know what version + patch level of Broker you are using.
When you create the default config it is just that. It is created and the queue manager + broker + config mgr are created and started.
I'm guessing that you are then trying to deploy a flow to the broker.
If so, have you created the object such as WMQ queues that the flow is going to use.
Are there any messages in the event log?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jan 10, 2010 8:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You've not said how big your bar file is.
Oddly enough, Message Broker uses MQ messages to send bar files from Toolkit to ConfigMgr and from ConfigMgr to Broker. And doesn't think you'd like to lose them, so it sends them as persistent messages.
Except on Broker v7, when it skips the non-existent ConfigMgr.
So if you have, for example, a 300MB bar file, it's gonna take... you guessed it... 300MB of log space in MQ. |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Jan 11, 2010 1:20 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
I also note that in your original message you state that you have not created any queues in the QM
possibly when you deploy the flows are trying to start and then failing multiple times as they cannot find the queues they should be reading messages from hence the amount of errors
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
|
|
