| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| sysout in Java Compute Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| phaniIIB |
 Posted: Thu Aug 20, 2015 7:22 am Post subject: sysout in Java Compute Node |
 |
|
Acolyte
Joined: 28 Jul 2015
Posts: 51
|
| Where do I see my system.out.println() logs of Java Compute Node. I am running IIB v10 in Linux. Can anyone tell me if it is possible to track sysout logs in any specific place. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Aug 20, 2015 7:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's much easier to use the IIB log classes.
But sysout goes to a file buried in the EG runtime folder. It's stdout and stdin on Unix and console.txt on Windows
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| BhavinJ |
| Posted: Fri Jul 22, 2016 2:22 am Post subject: logs not getting generated |
|
|
Newbie
Joined: 22 Jul 2016
Posts: 1
|
Hi Jeff,
I am working on v10.0.0.3. We are migrating a few applications to IIB. A few of them already have sysouts in the java parts and hence we are to use them as well for run status.
I used to see the sysouts in the location mentioned by you till now but they are not getting logged in console.txt anymore(I had to reinstall product and all).
If anyone can help with what might I try to see the sysouts. Or if somehow i can give path for javacompute sysouts? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 02, 2016 5:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Your java developers should be trained not to use, or restrained from using, println.
If you're running v10 on Windows, and the console.txt file is not in the location I mentioned, then I don't know where it would be.
If you *were* running on Windows and are *now* running on Unix, then the file is no longer "console.txt", but is now "stdout" and "stderr".
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 02, 2016 6:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Your java developers should be trained not to use, or restrained from using, println. |
Part of the migration to IIB should be to adapt the code to the IIB environment. As a minimum you need to change it from whatever they're processing now to the IIB input structures. You also need to remove file access, MQ access and all the other things which are now handled by IIB - this includes logging as my most worthy associate points out.
If you're just moving the code into IIB and not exploiting all of the facilities, why are you spending time and money migrating the code? Why not leave it where it is?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
