This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
What causes SQOUTBD in WebSphere to hold messages in the queue and does
not send it all the way to the end point?
We have two instances of Maximo deployed to 2 separate servers, one set up
for UI and Cron for the other. Cron server is setup with no
crontask.donotrun entries and UI is set with this parameters;
mxe.crontask.donotrun=ESCALATION,BBCron.BBCRON1,PMWoGenCronTask.PMWOGEN,REPORTLOCKRELEASE.REPORTLOCKRELEASE1,REPORTUSAGECLEANUP.REPORTUSAGECLEANUP1
When event is triggered from Cron server files go all the way to end point
but not when coming from UI. I can see the messages in the WebSphere
console's sqoutbd@ctgNode01.MXServer-intjmsbus.
Both servers are pretty much identical except for the maximo.properties.
Environment:
Maximo 7.1.1.5
2005 SQL Server
WebSphere 6.1 - 2 application servers (UI - CRON)
Regards,
Dennis B
The information contained in and transmitted with this Email may be
privileged, proprietary, confidential and protected from disclosure. No
privilege is hereby intended to be waived. This Email is intended only for
the person to whom it is addressed. If you are not the intended
recipient/addressee, any use of the Email and/or its contents, including,
but not limited to, dissemination, distribution or copying is strictly
prohibited and may be unlawful, and you must not take any action in
reliance on it. If you receive this Email in error, please immediately
notify the sender and delete the original message and any copies of it
from your computer system. We deny any liability for damages resulting
from the use of this Email by the unintended recipient, including the
recipient in error.