| Author |
Message
|
| smdavies99 |
 Posted: Mon Nov 14, 2011 1:15 am Post subject: Maximum length for WMBEVENT.LOG Messages |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Is there a max length for event messages that are written to the log file.
This is for Broker 6.1.0.9 on Solaris/Sparc.
I'm seeing some BIP2951I messages tuncated at 1035 characters.
_________________
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 |
|
 |
| lancelotlinc |
| Posted: Mon Nov 14, 2011 7:30 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 14, 2011 7:55 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| You may consider using log4j if you need to record more data than the WMB runtime allows. |
Sigh. How did I not think to expect that answer from you. 
Sadly, this is not possible. If this were a greenfield broker then yes we could look into using log4j
_________________
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 |
|
|
| lancelotlinc |
| Posted: Mon Nov 14, 2011 8:02 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| vmcgloin |
| Posted: Mon Nov 14, 2011 8:41 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
syslog line length is implementation specific.
The 1035 character limit you are seeing seems quite normal. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 14, 2011 10:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you need to log the event messages, why not send them to a queue and have some (home grown) program service the queue and write to a file... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 14, 2011 1:19 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Thanks for the suggerstions for alternate logging.
The LOG esql function makes it easy to record events in the same place as all the other broker events. Some of our analysis tools use bits of data in the event messages (of all types) to group them for later analysis. These help is fault investigation in the live systems which are strictly 'hands off' to mere devs like me.
For example, an error in a DB operation is not initially handled by the standard error handler. We use the LOG function to add extra data to the output such as the SQLCommand being used before and exception is thrown. The same applies to certain SAP Request return values.
We will just have to live with this restriction.
Every other option (eg log4j) else is pretty well a non starter in the current environment.
_________________
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 |
|
|
| lancelotlinc |
| Posted: Mon Nov 14, 2011 1:42 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
If the limit is the syslog daemon, you can recompile the syslog daemon source code and increase the character limit.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 14, 2011 2:25 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| If the limit is the syslog daemon, you can recompile the syslog daemon source code and increase the character limit. |
What a fantastic idea....
But
Good luck getting that done on Solaris/SPARC.
Then good luck in getting the Unix Sysadmins to accept the updated binary without a lot of blood letting, especially as Broker is going to be retired in 3-6 months and replaced by JBoss(yeah I know it does not make sense)
_________________
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: Mon Nov 14, 2011 3:04 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| Broker is going to be retired in 3-6 months and replaced by JBoss(yeah I know it does not make sense) |
It makes as much sense as it does to require 9 months of approval to apply a fixpack.
And, hey, just because they replace Broker with JBoss, doesn't mean they won't turn around and replace JBoss with Broker 6 months later.
Especially as they start to realize the difference in reliability. |
|
| Back to top |
|
|
|
|
