Author |
Message
|
Smaranda |
Posted: Fri Feb 23, 2007 12:46 am Post subject: Log4J problems on AIX and Broker 6 |
|
|
Newbie
Joined: 18 Jan 2007 Posts: 5 Location: Romania
|
Hi
I am working with Message Broker Version 6. I am developing some flows using java compunte nodes and some custom made libraries. The server is installed on AIX. I have tried to use Log4J as method to log some messages. I have choosed this solution because I stiil have problems with java debuger in the toolkit (I have a topic on it but nobody had an aswer).
The log4j.properties file is reached and it seems that the file in created on server, but no message is write in file.
Did someone met this problem before?
Thanks in advance! |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Feb 23, 2007 12:54 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
Will you please tell us, are you getting any error while compiling the java program.
you said you are having some probelms with the java debugger' Please state that too.
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Smaranda |
Posted: Fri Feb 23, 2007 3:00 am Post subject: |
|
|
Newbie
Joined: 18 Jan 2007 Posts: 5 Location: Romania
|
Hi,
I do not have any error. I am sure about the fact that the properties file is found, because the file was at least once created. Besides, I have printed from that node the status of the logger and it seems that it is correct initialised.
You can read my message already post some time ago concerning Java Debugger
"I have a small problem. I am a begginer in WMB domain and I have tried to use the debugger for java compute node. I have red all details you have specified on this topic and the ones givven by th eprovider IBM.
Configuration
Toolkit 6.0.0.2 patch 2 on windows
WMB version 6 on AIX
I have started the proper listener and using the right port I have made the configuration for the debugger environment with that port. The listener is up and running but when I start to debug a small flow (in, java compute, out node) everithing seems to be fine with one small exception:
when I press the button to enter in the java code, the controll enters in java file and keep working without showing me anythin: neither variables , nor the current line of code.
I have places a brakepoint before the compute node and some breakpoints into code. The control never stops to any of th einternal brakepoints from java code.
Did anyone met this situation before? I really need a solution, but IBM site and formus do not seems to have one. "
That is the story. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Feb 23, 2007 4:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Did you configure the debugger for java ?
The standard config of the debugger is for ESQL (default port 10002 ?)
You need to issue an mqsichangebroker command (look it up) for java to be debugable. Then you need to plug that information (java debug port) into the java setup for the debugger.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Smaranda |
Posted: Fri Feb 23, 2007 4:31 am Post subject: |
|
|
Newbie
Joined: 18 Jan 2007 Posts: 5 Location: Romania
|
Hi
Yes I did that. I think I have already explained that. we havbe a different port number. I read the rpocedure of configuration on IBM articles.
When the debugger starts, the control enter in the code, but does not show me a line where it gets or any other details, just hang-up and waits for a long time until I kill it. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Feb 23, 2007 2:30 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Well is the firewall open to let the debugger communication through on the java debugger port?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Smaranda |
Posted: Sun Feb 25, 2007 10:34 pm Post subject: |
|
|
Newbie
Joined: 18 Jan 2007 Posts: 5 Location: Romania
|
Hi
I will suggest this to one of my colleagues, but I think the problem is different than just a firewall. I am working from a country direct to a server from another. My colleague is working locally with the broker.
Thanks for your suggestion, what about the log4j? Do you have any idea for this problem too?
 |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Feb 27, 2007 10:46 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
you might want to use the broker's logger capabilities while within the message flow.
See the infocenter for more details.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|