Author |
Message
|
JVR |
Posted: Tue Jun 23, 2015 11:09 pm Post subject: Issues in using IAM3 log4j supportpck for IIB9 |
|
|
Newbie
Joined: 05 Mar 2012 Posts: 8
|
Hello,
I am using IIB 9.0.0.1 on Linux as development environment and have configured IAM3 support pack for log4j.I have followed the instructions as given in the IAM3 documentation.
The happy path works great and the logs are successfully written to the target file.
The documentation mentions that if the Log4j initialization (Config file location is not correct, Appender is not present)or log4j (logging) fails and the function would return the Boolean value as False, utilizing which an error handling mechanism can be built.
CALL initLog4j('brokerlog.xml') INTO rc;
IF ( rc = FALSE ) THEN
-- error initializing log4j
I'm facing an issue where this Boolean variable is never set to false (is always true) even if the log4j initialization fails or all the above mentioned scenarios are true (as seen in the console.txt file of the Execution group)
Code: |
2015-06-23 13:11:07.702 Execution group started. UUID is: '99284888-4b01-0000-0080-f60302705a92'. Broker is: BRKR9
Listening for transport dt_socket at address: 5555
2015-06-23 13:11:48.083 30 log4j:WARN Error looking up config file
2015-06-23 13:11:48.086 30 java.io.FileNotFoundException: Loggingconfig1.xml
2015-06-23 13:11:48.086 30 at com.ibm.broker.IAM3.LogManager.init(LogManager.java:67)
2015-06-23 13:11:48.087 30 at com.ibm.broker.IAM3.Log4jNode.initLog4j(Log4jNode.java:698)
2015-06-23 13:25:50.754 30 log4j:WARN No appenders could be found for logger (APP:MF_APP_HCSPROVIDER_FLOW:BRKR9).
2015-06-23 13:25:50.755 30 log4j:WARN Please initialize the log4j system properly. |
What are the scenarios when this value would be set as False? Does this require any configuration changes?
I have gone through multiple blogs and forums but have not found a scenario where a error handling mechanism was built if log4j failed.
Thanks in advance. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Jun 24, 2015 4:08 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
The current direction is not to use log4j but to use java.util.logging instead.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
JVR |
Posted: Wed Jun 24, 2015 5:27 am Post subject: |
|
|
Newbie
Joined: 05 Mar 2012 Posts: 8
|
Thanks.
I have seen the same suggestion in this/other forums as well.
For now, this is the requirement.
 |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jun 24, 2015 5:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Are you sure that the value returned is always set to "True"? Or is it not set to any value, or to a nill value, or to something other than simply "false"? |
|
Back to top |
|
 |
JVR |
Posted: Wed Jun 24, 2015 5:52 am Post subject: |
|
|
Newbie
Joined: 05 Mar 2012 Posts: 8
|
Yes!! I was hoping to see anything other than true set in the Boolean variable.
It is always set to true.
I provided an erroneous configuration file and still see the value set as True.
Code: |
2015-06-23 13:45:23.071 30 log4j:WARN Config file used: /C:/Program%20Files%20(x86)/IBM/MQSI/9.0.0.3/bin/Loggingconfig.xml
2015-06-23 13:45:23.169 30 log4j:ERROR Parsing error on line 15 and column 23
2015-06-23 13:45:23.170 30 log4j:ERROR An element with the identifier "FILEOtherr" must appear in the document.
2015-06-23 13:45:23.177 30 log4j:ERROR No appender named [FILEOtherr] could be found.
2015-06-23 13:46:20.869 30 log4j:WARN No appenders could be found for logger (APP:MF_APP_HCSPROVIDER_FLOW:BRKR9).
2015-06-23 13:46:20.870 30 log4j:WARN Please initialize the log4j system properly. |
|
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jun 24, 2015 6:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Sounds like a bug in the supportPac. |
|
Back to top |
|
 |
Anjali |
Posted: Tue Aug 30, 2016 6:21 am Post subject: Re: Issues in using IAM3 log4j supportpck for IIB9 |
|
|
Novice
Joined: 20 Jul 2016 Posts: 11
|
even I am doing on the same code. and also placed the jars in the right place but i am facing the issue like this:
'Log4jLoggingPluginNode', in message flow 'log4jmsgflow'. The broker cannot create nodes of this type because an implementation library for this node type does not exist in the LIL path.
"""""
Ensure that the LIL path is correct, and that it contains all the required node implementation libraries, including those supplied by IBM. The node name is case sensitive, therefore check that the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode', ensure that when the node was registered with the toolkit the name registered did not end in 'Node'.
Also ensure that you have saved the message flow, and any nested message flows. Redeploy the new configuration to the broker, specifying a complete configuration. If the LIL file is correct, check that the message node type is correct.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.
""""""
Could you plz suggest me why I am getting this.
Im doin on toolkit 9.0.0.0
with windows 10 pro |
|
Back to top |
|
 |
|