| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Syserr logs in MQ Workflow are being updated in millions/day |
« View previous topic :: View next topic » |
| Author |
Message
|
| raj00784 |
 Posted: Wed Jan 21, 2009 3:26 am Post subject: Syserr logs in MQ Workflow are being updated in millions/day |
 |
|
Newbie
Joined: 28 Feb 2007
Posts: 2
Location: INDIA
|
[b]Hi,
Please anyone can helpout in the following issue.The syserr logs are being
updated like hell and its consuming lot of resources.Following are the log details :
01/21/09 16:34:35 FMC22590W Process CSE_R_PMU_PM00051843_RPMU00029507, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_M_BOM_BO01076791_MBOM00011696, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_PMU_PM00051895_RPMU00026372, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_BOM_WM00084355_RWMC00020747, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_PMU_PM00051879_RPMU00025880, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_BOM_WM00084588_RWMC00013068, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_BOM_BO01076811_RBOR01079052, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_PMU_PM00051832_RPMU00003680, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_BOM_WM00084363_RWMU00003125, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
01/21/09 16:34:35 FMC22590W Process CSE_R_BOM_WM00084329_RWMK00000168, activity CustomerServiceLoop: Member CustomerServiceLoop:DECISION is not set.
According to the analysis the LAN ID''s ie " CSE_R_BOM_WM00084329_RWMK00000168 " are getting repeated in the logs and its being carried out continiously.Please anybody can suggest on the same what can be done either at application level or product level to stop these logs and secondly its also updating data in the table PROCESS_ACT_INST in DB2 along with logs which is consuming the filesystem like hell and we are unable to figure out the solution for the same.Please update ASAP.[/b]
Thanks and Regards
Raj00784
[/b] |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Jan 21, 2009 6:35 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
If you look at your model you will see that you have a case where the at the CustomerServiceLoop activity you are not setting the Member called DECISION.
This is a very common beginners error. Make sure that you have initialized all of your Exit and Transition Condition variables.
NOTE: I have seen these message bring a system to its knees, i.e. you must fix this.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| hos |
| Posted: Wed Jan 21, 2009 7:05 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
in addition to John's explanation:
Member name
| Quote: |
| CustomerServiceLoop:DECISION |
suggests that your activity is processed in a (block) loop and that this member contains the exit condition of the loop. Therefore you see the activity being processed over and over again in an endless loop, filling up your resources.
The only way to fix this is to change your model or your activity implementation and set this member. |
|
| Back to top |
|
|
| chintu |
| Posted: Thu Apr 23, 2009 7:26 am Post subject: |
|
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
We have a similar problem in our production environment. Lots of "not set" warning messages. As John and Hos mentioned..the correct way to fix them would be to handle such null values. A temproray fix to stop updating the fmc log tables would be to change your domain fdl to
"MESSAGE_RETAIN_PERIOD NEVER
ERROR_RETAIN_PERIOD NEVER"
This would still write to your log files..but would not write the DB. |
|
| 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
|
|
|
|
