facebook

Resin3 hair pulling

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

    lkb
    Member

    I can not for the life of me get Hotswap and debugging working with Resin3, MyEclipse and JDK 1.5.

    My setup:
    Windows XP (not by choice)
    Eclipse 3.1.0
    MyEclipse 4.0.2
    JDK 1.5.0_05-b05

    resin-pro-3.0.s051014 (required for hotswap on windows w/jdk 1.5)

    So, under Resin3 in the MyEclipse Application Server I have:
    Resin Home Directory: C:\resin-pro-3.0.s051014
    Configuration File: C:\resin-pro-3.0.s051014\conf/resin.conf

    Paths:
    all jars from resin_home/lib except resin.jar and resin1.5.jar

    library path:
    resin_hom/bin

    Now…..
    What goes in optional JVM arguments?
    I have tried
    -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
    and
    -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
    and
    -J-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000
    and
    -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
    and
    -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
    and
    -Xdebug -J-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000

    in run mode with the -xdebug, resin will start but will complain about being out of sync if I make one small code change.

    in debug mode I get a popup:

    A configuration error occured during startup. Please verify the preference field with the prompt: ERROR: JDWP unable to get necessary JVMTI capabilities. [“debugInit.c”, L279]

    So, clearly something is amiss. Has anyone gotten this to work properly?

    #240113 Reply

    Scott Anderson
    Participant

    I think we covered this one here:
    https://www.genuitec.com/forums/topic/closed-problems-launching-resin-3-pro-myeclipseide-4-0-1/#post-239000

    If the workaround solves the issue for you, you’ll be pleased to know that this was addressed in MyEclipse 4.0.3 (available now) so that adding pro.jar to the path is no longer required.

    #240115 Reply

    lkb
    Member

    That thread doesn’t help me at all.

    The pro.jar was already added by me.

    I am getting some other error:

    A configuration error occured during startup. Please verify the preference field with the prompt: ERROR: JDWP unable to get necessary JVMTI capabilities. [“debugInit.c”, L279]

    #240116 Reply

    Scott Anderson
    Participant

    It’s really unclear how you’re trying to start Resin. If you’re starting using our Resin 3 connector at Window > Preferences > MyEclipse > Application Servers > Resin 3 then you don’t need to set any debug arguments at all. All you have to do is point the configuration panel to the location of your Resin 3 install. MyEclipse handles setting up the debug connection automatically. Providing debug arguments would likely mess this up. Details on configuring application servers is in Using Application Servers quickstart in the Documentation Section.

    If you’re trying to launch Resin manually, externally from MyEclipse and then connect to it, information on how to do that is in the Remote Debugging quickstart in the same documentation section shown above.

    The first option, using the built-in connector is far simpler and highly recommended, but Resin must be running on the same machine as MyEclipse.

    #240150 Reply

    lkb
    Member

    I am running it from within MyEclipse.

    So, I have set it up without any args at all.

    Choose my JDK 1.5.0_05, select Debug mode, and nothing in the paths.

    I run it, and it starts.

    I can step through code.

    But, if I try to alter something like change

    return foo;

    to

    retuirn false;

    for debugging, I get this error:

    Hot code replace failed
    <not responding> was unable to replace the running code with the code in the workspace.

    Reason:
    Hot code replace failed = Scheme change not implemented

    So, that’s why I was trying the various arguments, to enable jdwp.

    So, is what I’m trying to do possible?

    #240188 Reply

    Scott Anderson
    Participant

    So, that’s why I was trying the various arguments, to enable jdwp.

    The issue is likely that you’re not running Eclipse and Resin with the same JDK version and the two JDKs are having trouble communicating. To start Eclipse with a particular JDK use:
    eclipse.exe -vm <path-to-jdk-install>\bin\javaw.exe

    Then set the Resin connector to use the same JDK at Window > Preferences > MyEclipse > Application Servers > Resin 3 > JDK

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Resin3 hair pulling

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