| Author |
Message
|
| [EG]Slayer |
 Posted: Wed Nov 19, 2008 3:13 am Post subject: WBI V6 Java compute node and sytem.out.println |
 |
|
Novice
Joined: 01 Aug 2008
Posts: 16
|
Hi all,
I'm using WBI Message Broker V6.02 on AIX 5.3.
In a java compute node I want to generate a trace file using system.out.println. I would like to know where is the default path for this trace because I can't find it ... Maybe I have to activate something to generate the trace file ?
Thanks for your help. |
|
| Back to top |
|
 |
| broker_new |
| Posted: Wed Nov 19, 2008 5:21 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
/var/mqsi/components/BROKERNAME/EG(UUID)/stdout
/var/mqsi/components/BROKERNAME/EG(UUID)/stderr
_________________
IBM ->Let's build a smarter planet
Last edited by broker_new on Wed Nov 19, 2008 6:19 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 19, 2008 5:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Only on Unix platforms.
On windows platforms, at 6.0 levels at least, stdout goes NOWHERE.
Do not use stdout from your Java Compute nodes. |
|
| Back to top |
|
|
| [EG]Slayer |
| Posted: Wed Nov 19, 2008 7:27 am Post subject: |
|
|
Novice
Joined: 01 Aug 2008
Posts: 16
|
ok, thanks  |
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Nov 19, 2008 8:12 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
I don't see why you can't redirect it on windows, or better still use a logging library - then you won't have to remove your logging statements when it goes into production.
[/code] |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 19, 2008 8:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| JLRowe wrote: |
| I don't see why you can't redirect it on windows, |
Because it's already redirected to nowhere.
| JLRowe wrote: |
| or better still use a logging library - then you won't have to remove your logging statements when it goes into production. |
Yes. This is the correct thing to do. Use Log4J or the built in Java logging facilities, or MbService.log* methods and not System.out.println. Then it is manageable and controllable. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Nov 19, 2008 10:31 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
FYI, from WMB 6.1 Windows stdout and stderr get redirected into a file called Console.txt in your workpath.
Also, in 6.0 for testing purposes on Windows you can change the service to "Interact with the Desktop" in the services snapin and then you can see stdout/stderr in a console window..
Cheers,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
