For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 13 replies, 4 voices, and was last updated 21 years, 7 months ago by
Scott Anderson.
-
AuthorPosts
-
Jay KuehnMemberI am running both Websphere 4.06 and 5.1.
When running 4.06, I get all the standard out messages in the console.
When I run with 5.1, I only get the loaded class… messages.Is there a way to get the standard out messages in the consle window?
August 27, 2004 at 10:14 am #213772
Riyad KallaMemberI’m checking on this for you
August 27, 2004 at 2:54 pm #213851
Scott AndersonParticipantMetavante,
I believe you have to use the websphere console to reconfigure its logging settings. There’s no way to do it directly through the connector at the current time.
August 27, 2004 at 3:27 pm #213853
Jay KuehnMemberI guess I dont understand why it just works in WAS 4.x.
The location of the log files changed in WAS 5.1.August 27, 2004 at 3:38 pm #213855
Jay KuehnMemberAny Idea what needs to be changed? I just looked through the admin console.
August 27, 2004 at 6:58 pm #213873
Scott AndersonParticipantI wish I knew. Configuration of WAS is a difficult . I’d have to check the doc located here:
http://publib.boulder.ibm.com/infocenter/ws51help/topic/com.ibm.websphere.base.doc/info/aes/ae/welc_troubleshooting.htmlAugust 31, 2004 at 11:03 am #214072
Chip EdwardsMemberWhere does MyEclipse expect to find the logs? I am having the same problem with 5.0.2.6.
September 1, 2004 at 4:43 pm #214284
Jay KuehnMemberThis is not a WebSphere configuration problem.
Myeclipse needs to listen to the corrent port for the log messages (or something).September 1, 2004 at 5:56 pm #214291
Riyad KallaMemberMetavante, do you have a resource with this info?
September 2, 2004 at 9:18 am #214352
Scott AndersonParticipantActually, what is echoed to the Console View in Eclipse is exactly what is sent to the “console” (or stdout) by the application. The Console View isn’t specifically a Log View. However, it can generally be used as one since most application servers will log to standard out as the default. For example, JBoss, Tomcat, WebLogic, Resin, etc all do this. WebSphere apparently doesn’t do that. It sends some high level messages to standard out, and thereby to the Console View, and other messages it directs to its log files. My suggestion earlier was that if you want to see the log output in the Console View, WebSphere will have to be configured to send its log output to standard out, rather than to its default log file. Another workaround to see the file is simply to use File > Open External File…
I guess I dont understand why it just works in WAS 4.x.
The location of the log files changed in WAS 5.1.It worked in WAS 4.x because by default all log messages went to standard out, just like all the other application servers.
September 2, 2004 at 9:37 am #214361
Jay KuehnMemberYou are correct. I am looking to the standard out messages.
The Standard out message are going to default_server_stdout.log.If you can catch the stdout in was 4.x, why cant you catch was 5.x?
Also I see no File, open external file.
September 3, 2004 at 11:07 am #214513
Scott AndersonParticipantMetavante,
As I mentioned earlier, the confusion you’re experiencing is caused by IBM changing the default behavior of WebSphere 5.1 with respect to log management. To be sure you get everything configured the way you want, I’ve put together a tutorial that walks you through setting up the log configuration so that everything will end up in the Eclipse Console View. The tutorial is available here:
http://www.myeclipseide.com/Articles/WebSphere5.1LogConfiguration/WAS5.1LogConfiguration.htmlSeptember 7, 2004 at 12:56 pm #214708
Jay KuehnMemberThank You Very Much!
September 7, 2004 at 2:41 pm #214717
Scott AndersonParticipantYou’re welcome. Glad you’re up and running.
-
AuthorPosts
