[bittersweetryan]

I have an application that I recently switched development servers from the integrated Tomcat to Websphere 6.1 on and I’m no longer receiving any relevant stack traces upon an exception in my console. Is there a way I can configure MEB and Websphere 6.1 to output stack traces in the console?

Currently the only way I’m able to do it is to use the exceptions printStackTrace method which only shows the top of the stack trace which isn’t very helpful.

[support-joy]

bittersweetryan,

I am afraid I cannot reproduce this issue at my end. Could you try something for me. Open MyEclipse Blue IDE, from menu options click on MyEclipse > Examples on Demand. This will open the examples on demand browser. Select any EOD and click on [install] to check-in the project to your package explorer. Next run this project on WAS6.1. Could you check if you are able to see stacktrace in console? If not, then do the following –
1. From menu options click on Help > About MyEclipse Enterprise Workbench and copy and paste – build-id and version-id here
2. From menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here
3. Open your .log file located at [your workspace dir]/.metadata/.log, clear the .log file, replicate issue and attach .log
4. Attach screenshot of your console output to help me get a visual

[bittersweetryan]

Thanks for the help Joy:

1: Version: 8.6.1 Blue, Build id: 8.6.1-Blue-20101117

2:

*** Date:
Thursday, August 18, 2011 7:41:21 AM CDT

** System properties:
OS=WindowsVista
OS version=6.0.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Blue Edition
Version: 8.6.1 Blue
Build id: 8.6.1-Blue-20101117

*** Eclipse details:
MyEclipse Blue Edition

Version: 8.6.1 Blue
Build id: 8.6.1-Blue-20101117

Eclipse Platform

Version: 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Build id: M20100211-1343

Eclipse Java Development Tools

Version: 3.5.2.r352_v20100108-7r88FEwFI0WTuoBl0iaG0tyhfZH6
Build id: M20100211-1343

Eclipse Plug-in Development Environment

Version: 3.5.2.R35x_v20100119-7Z7_FA2FDX-aXQYWqYDBz-z0qufo
Build id: M20100211-1343

Eclipse Graphical Editing Framework GEF

Version: 3.5.2.v20100111-1352-777928194B66D5D476C33B2A
Build id: 201001111753

Eclipse RCP

Version: 3.5.2.R35x_v20100119-9SA0FxwFnoCU5XxWItFdXXb27BA6
Build id: M20100211-1343

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\ranklam.IDL\AppData\Local\Genuitec\Profiles\MyEclipse Blue Edition 8.6\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\Users\ranklam.IDL\AppData\Local\Genuitec\Profiles\MyEclipse Blue Edition 8.6\../../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Users\ranklam.IDL\AppData\Local\Genuitec\Profiles\MyEclipse Blue Edition 8.6\../../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Users/ranklam.IDL/AppData/Local/Genuitec/Profiles/MyEclipse Blue Edition 8.6
-configuration
configuration
–clean
-vm
C:/Users/ranklam.IDL/AppData/Local/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

4: see attachment, this output is generated from exception.printStackTrace(), whereas in tomcat I’d see much more of the stack trace in the console view (including jsp line numbers)

Attachments:

You must be logged in to view attached files.

[support-joy]

bittersweetryan,

Could you please do the following –

1. clear your .log file located at [your workspace dir]/.metadata/.log, replicate the issue and attach .log here
2. Can you confirm if you have checked out a sample EOD and tried out by adding an exception in lets say .java or .jsp and does it throw any exception in the console?
3. For a change, could you try deploying and running the same project on tomcat?Does it show the stack trace?

I have also escalated your issue to dev team member.

[bittersweetryan]

Just for an experiment I tried upgrading to MEB 9.1 on my development machine and this appears to have fixed the issue. I how see all relevant debugging output. For comparison sake I’ll attach a screenshot of what I’m seeing now in my console view.

There is a slight chance I was using a version 9 workspace in my 8.6 instance. Would this be a cause for the issue I was having?

Attachments:

You must be logged in to view attached files.

[bittersweetryan]

I may have figured out the root of the issue. When running MEB with “Run as Administrator” checked on Windows 7 I DID NOT recieve the extra debuggin output. When I unchecked that option I once again received the debugging output. This is the opposite behavior that I would have expected but it might be something for your development team to look into.

[support-joy]

bittersweetryan,

Good to hear you are all set. I am afraid we could not reproduce this issue. We ran the profile as an administrator and also as a user, but both the times console displays stacktrace. Could you please retest your theory and confirm that you are still facing this issue on ME Blue 9.1?

[bittersweetryan]

Joy, on 9.1 here’s what I’f found. I get good output in the console until I catch an exception and do a exception.printStackTrace(). As soon as that is called the first time I loose debugging output in the console.

I also cleared my .metadata .log file and reproduced this issue and no information was written to the log.

Restarting MEB will bring back debugging output to the console until the first exception is thrown by my websphere project.

[support-joy]

bittersweetryan,

Do you still have issue when not running as an administrator?
Thank you for the observations. I have made a note of the same. Let us know if you are running into any other issue.

Best Regards

[bittersweetryan]

I’ve been keeping a close eye on this issue, unfournately I had to switch back to MEB 8.6 because I just wasn’t able to be productive on 9.1 without decent output in the console. I cleared my log in my workspace as well and the error wasn’t showing anything in the log.

What happens is that after a short period of time it appears the console “fills up” and stops giving me any output. This is not an issue on MEB 8.6. If you’d like I can post my project file, or even workbench files so you can see exactly how I have 9.1 configured.

[bittersweetryan]

Here is my .metadata\.log file after I lose debugging output in the console:

!SESSION 2011-09-06 14:57:59.391 ———————————————–
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.jface 2 0 2011-09-06 14:58:10.178
!MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2011-09-06 14:58:10.178
!MESSAGE A conflict occurred for SHIFT+DEL:
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.datatools.sqltools.result.removeAllInstances,Remove All Visible Results,
,
Category(org.eclipse.datatools.sqltools.result.category,SQL Results View,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.ui.edit.cut,Cut,
Cut the selection to the clipboard,
Category(org.eclipse.ui.category.edit,Edit,null,true),
org.eclipse.ui.internal.handlers.WidgetMethodHandler@1610393,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.dialogAndWindow,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.topcased.modeler.deleteModelObject,Delete From Model,
Allows the user to delete the selected graph element and its associated model element in a Topcased editor.,
Category(org.eclipse.ui.category.edit,Edit,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)

!ENTRY org.eclipse.osgi 2 1 2011-09-06 14:58:13.208
!MESSAGE NLS unused message: prompt.optclasspath in: com.genuitec.eclipse.easie.core.configuration

!ENTRY org.eclipse.osgi 2 1 2011-09-06 14:58:13.209
!MESSAGE NLS unused message: prompt.preclasspath in: com.genuitec.eclipse.easie.core.configuration

!ENTRY org.eclipse.osgi 2 1 2011-09-06 14:58:13.209
!MESSAGE NLS unused message: prompt.optlibrarypath in: com.genuitec.eclipse.easie.core.configuration

!ENTRY org.eclipse.dltk.core 4 0 2011-09-06 14:58:37.415
!MESSAGE error saving index
!STACK 0
java.io.UTFDataFormatException
at org.eclipse.dltk.internal.core.util.Util.writeUTF(Util.java:1430)
at org.eclipse.dltk.core.search.index.DiskIndex.writeCategoryTable(DiskIndex.java:1177)
at org.eclipse.dltk.core.search.index.DiskIndex.writeCategories(DiskIndex.java:1133)
at org.eclipse.dltk.core.search.index.DiskIndex.mergeWith(DiskIndex.java:724)
at org.eclipse.dltk.core.search.index.Index.save(Index.java:243)
at org.eclipse.dltk.core.search.indexing.core.SourceModulesRequest.run(SourceModulesRequest.java:85)
at org.eclipse.dltk.core.search.indexing.AbstractJob.execute(AbstractJob.java:77)
at org.eclipse.dltk.internal.core.search.processing.JobManager.run(JobManager.java:452)
at java.lang.Thread.run(Thread.java:619)

[support-tony]

Ryan,

You say you’ve switched back to MyEclipse Blue 8.6. Are you not now seeing the problem? If not, can you say what is different between your 8.6 environment now and your 8.6 environment when you first reported this problem? Is it possible for you to replicate the same environment with MyEclipse Blue 9.1, to solve the issue?

If you still have the problem with 9.1, yes, it would help if you could attach your project and explain the detailed steps to replicate the problem. You can attach the project to an email to support@genuitec.com, if you don’t want to attach here (if so, please include a link to this topic). Also, could you let us know what additional plugins you have installed as they may have an impact in some way.

[bittersweetryan]

Tony,

The problem exists but its a bit different in 8.6. I wish I could tell exactly what makes my debug output disappear but I have not yet been able to find out exactly what is reproducing it and after it happens there are no new messages in my .log file.

I’ll gladly provide whatever information you need to help troubleshoot this issue. Developing is quite tricky without my console output!

Ryan

[bittersweetryan]

I figured it out, websphere had a log output rollover setting of 1 mb. Whenever my system.out log would reach 1 mb websphere would create a new one and myeclipse blue would no longer be associated with it in the console view.

[Brian Fernandes]

Ryan,

This is a seriously good find, thanks for getting back to us with it. We’ve filed a bug and will try and fix it as soon as viable.

[Author]

Posts