[jvermeer]

Hi,

Since my upgrade to MyEclipse 7 I have noticed that when I start my application server in MyEclipse the stack traces on my server console aren’t clickable anymore. This only occurs when I start my application server for the first time. When I hit the restart button the server will restart and the stack traces on my server console are clickable again like they always were in older versions of MyEclipse.

I currently use ME 7.1.1 and Tomcat as Application server.

Can anyone help me?

[support-joy]

I cannot reproduce this at my end. I have downloaded the GoogleMapsExample from ExamplesOnDemand. Deployed and ran the application on Tomcat 5.5. I can click on stack traces on my server console. What is your system configuration? Can you copy and paste your installation detail here? You can get it from MyEclipse > Installation Summar > Installation Detail. Also does ME report any error? How did you install ME 7.1.1? Meaning – download of all-in-one installer, using pulse, installed eclipse 3.4.1 classic and added myeclipse plugin? what is your tomcat version?

[jvermeer]

Hi,

My installation details are:

*** Date:
vrijdag 17 april 2009 12:44:27 uur CEST

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.1.1
Build id: 7.1.1-20090310

Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700

Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800

Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\development\Genuitec\MyEclipse 7.1\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\development\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\development\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
configuration
-vm
C:\development\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

I installed MyEclipse using the all in one installer.
The error log only reports a lot of unused messages from maven.
My tomcat version is 5.5.15

I get this every morning after I started MyEclipse. To reproduce this you can try these steps:
1: Start MyEclipse
2: Start tomcat

When I start tomcat for the first time the console doesn’t respond. See https://www.genuitec.com/forums/topic/tomcat-console/
It may be possible the problem is connected to this topic.

When I open the Java Stack Trace console, the tomcat console appears. I close the Java Stack Trace console and the tomcat console remains.
I can’t click on any stack trace.

Now I restart my tomcat server using the restart button.
The server shuts down and starts again. Now I can click on a stack trace in my tomcat console.

I hope this can help you to reproduce my problem.

J Vermeer.

[support-joy]

J Vermeer,

Thanks for the reproduction script. I am afraid, I am still not able to reproduce this issue. Since this issue is reported by a lot of other users as in the other post referred above, I am sure that there should be a reproduction script. I am flagging this for dev team members to investigate. Can you give me any other pointers that will help me reproduce at my end? Do you have any plugins added? If yes, what are they?

Sorry for the inconvinience caused.

[jvermeer]

Hi,

I have no other plugins installed.
Besides the other topic mentioned I can’t find any other connection which could be related to this problem.

I hope the dev team can find something to solve it.

Regards J Vermeer.

[support-joy]

J Vermeer,

Thanks, I have added this issue to the existing PR and flagged it for the dev team members to investigate. I will get back to you on this.

Inconvinience caused is sincerely regretted.

[support-joy]

J Vermeer,

I am able to replicate this issue. I will get back to you later with the dev teams findings. Sorry for the inconvinience.

[Author]

Posts