facebook

Tomcat and jmx management: stop problems

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #244456 Reply

    I recently have set my Tomcat config to use these additional properties (MyEclipse/Application Servers/Tomcat 5/JDK):

    -Dcom.sun.management.jmxremote
    -Dcom.sun.management.jmxremote.port=8999
    -Dcom.sun.management.jmxremote.ssl=false
    -Dcom.sun.management.jmxremote.authenticate=false

    I’m using Eclipse 3.1 with MyEclipse 4.0.0 GA, Tomcat 5.5.9 and JDK 1.5.0_04 on Windows XP SP2.

    It start Tomcat correctly in Eclipse and I can connect it via JConsole or MC4J.

    But, when I stop it this appear:

    Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 8999; nested exception is:
    java.net.BindException: Address already in use: JVM_Bind

    And Tomcat don’t stop.
    To stop it I have to modify config an drop the parameters reported above, before to invoke stop again.

    I think it happens because when I stop Tomcat, MyEclipse invoke JVM using those parameters, so port 8999 result already in use.

    Is there a way to avoid this?
    It’s so tedious…

    Thanks a lot

    Giovanni Grimoldi

    #244463 Reply

    Riyad Kalla
    Member

    Giovanni,
    There is not currently a way to avoid this, but you can switch to the Debug perspective and just kill the Tomcat process as a faster workaround for the time being.

    #244512 Reply

    Have you planned to resolve this in next releases?

    Giovanni

    #244535 Reply

    Riyad Kalla
    Member

    Giovanni,
    This is the first time this problem has ever been reported, I filed it when you reported it and one of the developers looking into it said that our launch model will change in MyEclipse 5.0 and may address this issue, so while this may not be in 4.1, it will likely be taken care of changes in our 5.0 release cycle.

    #292760 Reply

    DarkMortal
    Member

    This message has not been recovered.

    #292789 Reply

    Riyad Kalla
    Member

    This message has not been recovered.

    #292799 Reply

    DarkMortal
    Member

    This message has not been recovered.

    #292859 Reply

    Riyad Kalla
    Member

    This message has not been recovered.

    #292908 Reply

    DarkMortal
    Member

    This message has not been recovered.

    #292996 Reply

    Riyad Kalla
    Member

    This message has not been recovered.

    #305841 Reply

    ibrandt
    Participant

    This message has not been recovered.

    #305854 Reply

    support-joy
    Member

    This message has not been recovered.

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Tomcat and jmx management: stop problems

You must be logged in to post in the forum log in