| Author |
Message
|
| ceteareth |
 Posted: Fri Feb 22, 2013 12:26 am Post subject: Logging is inconsistent |
 |
|
Acolyte
Joined: 12 Aug 2012
Posts: 51
|
Hello everyone.
I implemented logging using a java based api(logback). It is working fine for months. We continously develops applications but right now we are experiencing that the messages are not always being logged even for the old applications which does not have any issue before.
I am thinking that perhaps there is something on the background that is prohibiting the logger to work.
The application works end to end but it is not logging messages most of the time.
do you have any idea on why this is happening? Thanks in advance. |
|
| Back to top |
|
 |
| adubya |
| Posted: Fri Feb 22, 2013 12:29 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
Have you enabled trace and verified that the logging is being invoked ?
Is the target for the log a file, if so are the file/directory permissions set correctly such that the broker user can write to the file ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 22, 2013 6:07 am Post subject: Re: Logging is inconsistent |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ceteareth wrote: |
| I implemented logging using a java based api(logback). |
Why did you do this rather than use the facilities WMB has for logging?
| ceteareth wrote: |
I am thinking that perhaps there is something on the background that is prohibiting the logger to work.
The application works end to end but it is not logging messages most of the time. |
Sounds plausible
| ceteareth wrote: |
| do you have any idea on why this is happening? |
How can we know that? This is an external java api you've introduced into your broker installation. We don't know how you've done that (or why you've done that) and we don't know what else you've introduced. I think it's a good theory that if you've got such a relaxed attitude to introducing external jars to WMB, one of the others that's in play is affecting this. You should research CLASSLOADER and good luck fixing this.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 22, 2013 6:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
DO NOT USE LOGBACK.
DO NOT USE LOG4J.
Use java.util.logging. |
|
| Back to top |
|
|
| ceteareth |
| Posted: Mon Feb 25, 2013 11:42 pm Post subject: |
|
|
Acolyte
Joined: 12 Aug 2012
Posts: 51
|
my colleague noticed a error being displayed in MQ logs.
| Code: |
2013-02-26 09:52:52.283867 Execution group started. UUID is: '8f1fb8a8-3c01-0000-0080-988f9481b2cb'. Broker is: MOCK_BROKER
2013-02-26 09:54:22.782 12 SLF4J: Class path contains multiple SLF4J bindings.
2013-02-26 09:54:22.785 12 SLF4J: Found binding in [jar:file:/APP/mqsi/components/MOCK_BROKER/8f1fb8a8-3c01-0000-0080-988f9481b2cb/config/94f64a11-3d01-0000-0080-8cf51a9918a8/JAR/LIB_CommonJava.mqsiLibrary/logback-classic-1.0.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2013-02-26 09:54:22.786 12 SLF4J: Found binding in [jar:file:/APP/mqsi/components/MOCK_BROKER/8f1fb8a8-3c01-0000-0080-988f9481b2cb/config/1c904b11-3d01-0000-0080-8cf51a9918a8/JAR/LIB_CommonJava.mqsiLibrary/logback-classic-1.0.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2013-02-26 09:54:22.786 12 SLF4J: Found binding in [jar:file:/APP/mqsi/components/MOCK_BROKER/8f1fb8a8-3c01-0000-0080-988f9481b2cb/config/574c4a11-3d01-0000-0080-8cf51a9918a8/JAR/LIB_CommonJava.mqsiLibrary/logback-classic-1.0.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2013-02-26 09:54:22.786 12 SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2013-02-26 09:54:23.596 12 SLF4J: Actual binding is of type [ch.qos.logback.classic.selector.DefaultContextSelector]
|
The application seems to be confused on which jar to use. I am assuming that this is causing the problem.
My current setup is that the jar files are in the "IBM\MQSI\shared-classes". |
|
| Back to top |
|
|
| adubya |
| Posted: Tue Feb 26, 2013 12:39 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| Looks like the log4j jar is being deployed with your flow and so conflicting with the one you've placed in shared-classes. You need to eliminate one of them. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 26, 2013 4:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| adubya wrote: |
| Looks like the log4j jar is being deployed with your flow and so conflicting with the one you've placed in shared-classes. You need to eliminate one of them. |
You need to eliminate both of them, and use java.util.logging instead of log4j. |
|
| Back to top |
|
|
|
|
