
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
Debugging Resin Apps in/with Eclipse
How are you passing the arguments to the
JVM? In Resin 3.0, that was done with specifying “args” in httpd.sh. In Resin
3.1 you need to specify the arguments in resin.conf as shown here:
http://www.caucho.com/resin-3.1/doc/server-tags.xtp#jvm-arg
Shane
Hi,
I
had two approaches to debug Resin Apps within Eclipse
which
worked for me perfectly with Resin 3.0.x. However
with
Resin 3.1.2 I can't get them to work.
The
first approach was to start Resin with the arguments
-Xdebug
-Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345
and
have in Eclipse Resin as Remote Application configured
(Run
-> Debug -> Remote Application), connection Type Socket.
The
second approach was to start Resin in Eclipse having
Resin
configured as 'Java Application'. To switch from Resin
3.0.x
to Resin 3.1.2 I just had to change the classpath and
change
the main class from
'com.caucho.server.http.ResinServer'
to
'com.caucho.boot.ResinBoot'
(I guess).
Both
approaches show the same result with Resin 3.1.2.
I see
the Resin threads in the debug perspective as usual, I'm able
to run
the application, but Breakpoints don't get recognized
hence
I'm not able to debug.
Any
Ideas?
Regards
Martin
_______________________________________________
resin-interest mailing list
resin-interest@...
http://maillist.caucho.com/mailman/listinfo/resin-interest