[Resin-interest] Debugging Resin Apps in/with Eclipse

[MORAWETZ Martin]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070814/165f1831/attachment-0001.html
-------------- next part --------------



"Diese E-Mail sowie jeglicher Anhang sind vertraulich und ausschlie?lich f?r den/die bezeichneten
Adressaten bestimmt. Diese Mitteilung kann rechtlich gesch?tzte, firmeninterne oder anderweitig
vertrauliche Informationen enthalten, deren Weitergabe ohne unsere Zustimmung strengstens
untersagt ist. Sofern Sie nicht der beabsichtigte Adressat sind oder diese E-Mail irrt?mlich
erhalten haben, sind Sie nicht autorisiert, diese Mitteilung bekanntzumachen, zu kopieren,
weiterzugeben oder aufzubewahren. Bitte informieren Sie uns in diesem Fall unverz?glich
und vernichten diese E-Mail.

Diese Fu?note dient auch der Best?tigung dar?ber, da? diese E-Mail automatisch auf Computerviren,
anst??ige Inhalte und Einwahlprogramme gescannt wurde."

"The information in this e-mail and in any attachments is confidential and intended solely
for the attention and use of the named addressee(s). This information may be subject to legal,
professional or other privilege and further distribution of it is strictly prohibited without
our authority. If you are not the intended recipient, you are not authorised to and must not
disclose, copy, distribute, or retain this message or any part of it, and should notify us
immediately.

This footnote also confirms that this email has been automatically scanned for the presence
of computer viruses, profanities and certain file types."

[Shane Cruz]

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



________________________________

From: resin-interest-bounces at caucho.com
[mailto:resin-interest-bounces at caucho.com] On Behalf Of MORAWETZ Martin
Sent: Tuesday, August 14, 2007 7:09 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Debugging Resin Apps in/with Eclipse



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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070814/064b385c/attachment.html

[MORAWETZ Martin]

I use Resin on a windows machine. I tried both specifying the
args in resin.conf and starting Resin with 'httpd.exe args'.

Specifiying them in resin.conf results in:

java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:179)
at com.caucho.server.resin.Resin.parseCommandLine(Resin.java:934)
at com.caucho.server.resin.Resin.main(Resin.java:1341)
Can't connect to parent process through socket 1976
Resin needs to connect to its parent.
[Loaded java.util.IdentityHashMap$KeySet from C:\Programme\Java\jdk1.6.0_02\jre\
lib\rt.jar]
[Loaded java.util.IdentityHashMap$IdentityHashMapIterator from C:\Programme\Java
\jdk1.6.0_02\jre\lib\rt.jar]
[Loaded java.util.IdentityHashMap$KeyIterator from C:\Programme\Java\jdk1.6.0_02
\jre\lib\rt.jar]
[Loaded java.io.DeleteOnExitHook from C:\Programme\Java\jdk1.6.0_02\jre\lib\rt.j
ar]

Resin doesn't start up.

Starting httpd.exe with the args
C:\Programme\resin\httpd.exe -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345 -server a
causes Resin to start up correctly saying

"Listening for transport dt_socket at address: 12345
Resin Professional 3.1.2 (built Wed, 18 Jul 2007 11:30:06 PDT)
Copyright(c) 1998-2007 Caucho Technology. All rights reserved.
:
:
"

As I wrote before, partly it works, because I can see the Resin Threads in
the Eclipse Debug perspective.

Interesting thow that specifying the arguments in the resin.conf and with
httpd.exe behaves that different.

Regards Martin



-----Urspr?ngliche Nachricht-----
Von: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] Im Auftrag von Shane Cruz
Gesendet: Dienstag, 14. August 2007 14:36
An: General Discussion for the Resin application server
Betreff: Re: [Resin-interest] 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




________________________________


From: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] On Behalf Of MORAWETZ Martin
Sent: Tuesday, August 14, 2007 7:09 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Debugging Resin Apps in/with Eclipse



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




"Diese E-Mail sowie jeglicher Anhang sind vertraulich und ausschlie?lich f?r den/die bezeichneten
Adressaten bestimmt. Diese Mitteilung kann rechtlich gesch?tzte, firmeninterne oder anderweitig
vertrauliche Informationen enthalten, deren Weitergabe ohne unsere Zustimmung strengstens
untersagt ist. Sofern Sie nicht der beabsichtigte Adressat sind oder diese E-Mail irrt?mlich
erhalten haben, sind Sie nicht autorisiert, diese Mitteilung bekanntzumachen, zu kopieren,
weiterzugeben oder aufzubewahren. Bitte informieren Sie uns in diesem Fall unverz?glich
und vernichten diese E-Mail.

Diese Fu?note dient auch der Best?tigung dar?ber, da? diese E-Mail automatisch auf Computerviren,
anst??ige Inhalte und Einwahlprogramme gescannt wurde."

"The information in this e-mail and in any attachments is confidential and intended solely
for the attention and use of the named addressee(s). This information may be subject to legal,
professional or other privilege and further distribution of it is strictly prohibited without
our authority. If you are not the intended recipient, you are not authorised to and must not
disclose, copy, distribute, or retain this message or any part of it, and should notify us
immediately.

This footnote also confirms that this email has been automatically scanned for the presence
of computer viruses, profanities and certain file types."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070814/b6ac5d90/attachment-0001.html

[Eric Kreiser]

I am on linux... but specifying the args in the resin.conf works great
for me...

the main difference is that prior to the resin 3.1.x series... the
watchdog parent process was not java... and simply passed any arguments
passed to it down to the child java process which was actually your
application server.

now in the 3.1.x series... the parent process is java as well as the
child process... and the way to alter the child process is thru the
resin.conf

Post by MORAWETZ Martin
I use Resin on a windows machine. I tried both specifying the
args in resin.conf and starting Resin with 'httpd.exe args'.
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:179)
at com.caucho.server.resin.Resin.parseCommandLine(Resin.java:934)
at com.caucho.server.resin.Resin.main(Resin.java:1341)
Can't connect to parent process through socket 1976
Resin needs to connect to its parent.
[Loaded java.util.IdentityHashMap$KeySet from
C:\Programme\Java\jdk1.6.0_02\jre\
lib\rt.jar]
[Loaded java.util.IdentityHashMap$IdentityHashMapIterator from
C:\Programme\Java
\jdk1.6.0_02\jre\lib\rt.jar]
[Loaded java.util.IdentityHashMap$KeyIterator from
C:\Programme\Java\jdk1.6.0_02
\jre\lib\rt.jar]
[Loaded java.io.DeleteOnExitHook from
C:\Programme\Java\jdk1.6.0_02\jre\lib\rt.j
ar]
Resin doesn't start up.
Starting httpd.exe with the args
C:\Programme\resin\httpd.exe -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345 -server a
causes Resin to start up correctly saying
"Listening for transport dt_socket at address: 12345
Resin Professional 3.1.2 (built Wed, 18 Jul 2007 11:30:06 PDT)
Copyright(c) 1998-2007 Caucho Technology. All rights reserved.
"
As I wrote before, partly it works, because I can see the Resin Threads in
the Eclipse Debug perspective.
Interesting thow that specifying the arguments in the resin.conf and with
httpd.exe behaves that different.
Regards Martin
-----Urspr?ngliche Nachricht-----
*Von:* resin-interest-bounces at caucho.com
[mailto:resin-interest-bounces at caucho.com] *Im Auftrag von *Shane Cruz
*Gesendet:* Dienstag, 14. August 2007 14:36
*An:* General Discussion for the Resin application server
*Betreff:* Re: [Resin-interest] 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
http://www.caucho.com/resin-3.1/doc/server-tags.xtp#jvm-arg
Shane
------------------------------------------------------------------------
*From:* resin-interest-bounces at caucho.com
[mailto:resin-interest-bounces at caucho.com] *On Behalf Of *MORAWETZ
Martin
*Sent:* Tuesday, August 14, 2007 7:09 AM
*To:* General Discussion for the Resin application server
*Subject:* [Resin-interest] Debugging Resin Apps in/with Eclipse
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
"Diese E-Mail sowie jeglicher Anhang sind vertraulich und ausschlie?lich f?r den/die bezeichneten
Adressaten bestimmt. Diese Mitteilung kann rechtlich gesch?tzte, firmeninterne oder anderweitig
vertrauliche Informationen enthalten, deren Weitergabe ohne unsere Zustimmung strengstens
untersagt ist. Sofern Sie nicht der beabsichtigte Adressat sind oder diese E-Mail irrt?mlich
erhalten haben, sind Sie nicht autorisiert, diese Mitteilung bekanntzumachen, zu kopieren,
weiterzugeben oder aufzubewahren. Bitte informieren Sie uns in diesem Fall unverz?glich
und vernichten diese E-Mail.
Diese Fu?note dient auch der Best?tigung dar?ber, da? diese E-Mail automatisch auf Computerviren,
anst??ige Inhalte und Einwahlprogramme gescannt wurde."
"The information in this e-mail and in any attachments is confidential and intended solely
for the attention and use of the named addressee(s). This information may be subject to legal,
professional or other privilege and further distribution of it is strictly prohibited without
our authority. If you are not the intended recipient, you are not authorised to and must not
disclose, copy, distribute, or retain this message or any part of it, and should notify us
immediately.
This footnote also confirms that this email has been automatically scanned for the presence
of computer viruses, profanities and certain file types."
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
_______________________________________________
resin-interest mailing list
resin-interest at caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070814/e529f69e/attachment.html

[Mike Wynholds]

Just to be even more specific, the requirement for putting the cmd line args in resin.conf on windows actually kicked in at 3.1.2 (for some reason). With 3.1.1 I was able to debug by putting the cmd line args on the cmd line. Dunno why.



As for getting debugging to work with windows and Resin 3.1.2, I am able to do so with IDEA (dunno about eclipse), but adding this to resin.conf:



<jvm-arg>-Xdebug</jvm-arg>

<jvm-arg>-Xnoagent</jvm-arg>

<jvm-arg>-Djava.compiler=NONE</jvm-arg>

<jvm-arg>-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</jvm-arg>



and then having IDEA connect to any old remote server (nothing Resin specific).



what you are seeing when you put the cmd line args on the cmd line is the Resin watchdog process running in debug mode. so you could debug the watchdog process, but not the Resin process. not quite what you want.



..mike..



________________________________

From: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] On Behalf Of Eric Kreiser
Sent: Tuesday, August 14, 2007 8:58 AM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Debugging Resin Apps in/with Eclipse



I am on linux... but specifying the args in the resin.conf works great for me...

the main difference is that prior to the resin 3.1.x series... the watchdog parent process was not java... and simply passed any arguments passed to it down to the child java process which was actually your application server.

now in the 3.1.x series... the parent process is java as well as the child process... and the way to alter the child process is thru the resin.conf


MORAWETZ Martin wrote:

I use Resin on a windows machine. I tried both specifying the

args in resin.conf and starting Resin with 'httpd.exe args'.



Specifiying them in resin.conf results in:



java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:179)
at com.caucho.server.resin.Resin.parseCommandLine(Resin.java:934)
at com.caucho.server.resin.Resin.main(Resin.java:1341)
Can't connect to parent process through socket 1976
Resin needs to connect to its parent.
[Loaded java.util.IdentityHashMap$KeySet from C:\Programme\Java\jdk1.6.0_02\jre\
lib\rt.jar]
[Loaded java.util.IdentityHashMap$IdentityHashMapIterator from C:\Programme\Java
\jdk1.6.0_02\jre\lib\rt.jar]
[Loaded java.util.IdentityHashMap$KeyIterator from C:\Programme\Java\jdk1.6.0_02
\jre\lib\rt.jar]
[Loaded java.io.DeleteOnExitHook from C:\Programme\Java\jdk1.6.0_02\jre\lib\rt.j
ar]



Resin doesn't start up.



Starting httpd.exe with the args

C:\Programme\resin\httpd.exe -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345 -server a

causes Resin to start up correctly saying



"Listening for transport dt_socket at address: 12345
Resin Professional 3.1.2 (built Wed, 18 Jul 2007 11:30:06 PDT)
Copyright(c) 1998-2007 Caucho Technology. All rights reserved.

:

:

"



As I wrote before, partly it works, because I can see the Resin Threads in

the Eclipse Debug perspective.



Interesting thow that specifying the arguments in the resin.conf and with

httpd.exe behaves that different.



Regards Martin







-----Urspr?ngliche Nachricht-----
Von: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] Im Auftrag von Shane Cruz
Gesendet: Dienstag, 14. August 2007 14:36
An: General Discussion for the Resin application server
Betreff: Re: [Resin-interest] 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




________________________________


From: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] On Behalf Of MORAWETZ Martin
Sent: Tuesday, August 14, 2007 7:09 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Debugging Resin Apps in/with Eclipse



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



"Diese E-Mail sowie jeglicher Anhang sind vertraulich und ausschlie?lich f?r den/die bezeichneten
Adressaten bestimmt. Diese Mitteilung kann rechtlich gesch?tzte, firmeninterne oder anderweitig
vertrauliche Informationen enthalten, deren Weitergabe ohne unsere Zustimmung strengstens
untersagt ist. Sofern Sie nicht der beabsichtigte Adressat sind oder diese E-Mail irrt?mlich
erhalten haben, sind Sie nicht autorisiert, diese Mitteilung bekanntzumachen, zu kopieren,
weiterzugeben oder aufzubewahren. Bitte informieren Sie uns in diesem Fall unverz?glich
und vernichten diese E-Mail.

Diese Fu?note dient auch der Best?tigung dar?ber, da? diese E-Mail automatisch auf Computerviren,
anst??ige Inhalte und Einwahlprogramme gescannt wurde."

"The information in this e-mail and in any attachments is confidential and intended solely
for the attention and use of the named addressee(s). This information may be subject to legal,
professional or other privilege and further distribution of it is strictly prohibited without
our authority. If you are not the intended recipient, you are not authorised to and must not
disclose, copy, distribute, or retain this message or any part of it, and should notify us
immediately.

This footnote also confirms that this email has been automatically scanned for the presence
of computer viruses, profanities and certain file types."
--
This message has been scanned for viruses and
dangerous content by MailScanner <http://www.mailscanner.info/> , and is
believed to be clean.





________________________________




_______________________________________________
resin-interest mailing list
resin-interest at caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070814/795aeb76/attachment-0001.html

[MORAWETZ Martin]

Thank you all for responding,

I managed somehow to get it to work by specifiying the
args in resin.conf, actually I don't know what I did different
now.

http://www.caucho.com/resin-3.1/doc/ide-eclipse.xtp <http://www.caucho.com/resin-3.1/doc/ide-eclipse.xtp> says:
"You can launch Resin internally from Eclipse by launching
the main Resin class with the correct parameters", which was
my second debugging approach. I used 'com.caucho.boot.ResinBoot'
as main Resin class. Doing so apparently lets me debug the
watchdog process again, is that correct?

Regards Martin


-----Urspr?ngliche Nachricht-----
Von: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] Im Auftrag von Mike Wynholds
Gesendet: Dienstag, 14. August 2007 19:31
An: General Discussion for the Resin application server
Betreff: Re: [Resin-interest] Debugging Resin Apps in/with Eclipse



Just to be even more specific, the requirement for putting the cmd line args in resin.conf on windows actually kicked in at 3.1.2 (for some reason). With 3.1.1 I was able to debug by putting the cmd line args on the cmd line. Dunno why.



As for getting debugging to work with windows and Resin 3.1.2, I am able to do so with IDEA (dunno about eclipse), but adding this to resin.conf:



<jvm-arg>-Xdebug</jvm-arg>

<jvm-arg>-Xnoagent</jvm-arg>

<jvm-arg>-Djava.compiler=NONE</jvm-arg>

<jvm-arg>-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005</jvm-arg>



and then having IDEA connect to any old remote server (nothing Resin specific).



what you are seeing when you put the cmd line args on the cmd line is the Resin watchdog process running in debug mode. so you could debug the watchdog process, but not the Resin process. not quite what you want.



..mike..




________________________________


From: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] On Behalf Of Eric Kreiser
Sent: Tuesday, August 14, 2007 8:58 AM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Debugging Resin Apps in/with Eclipse



I am on linux... but specifying the args in the resin.conf works great for me...

the main difference is that prior to the resin 3.1.x series... the watchdog parent process was not java... and simply passed any arguments passed to it down to the child java process which was actually your application server.

now in the 3.1.x series... the parent process is java as well as the child process... and the way to alter the child process is thru the resin.conf


MORAWETZ Martin wrote:

I use Resin on a windows machine. I tried both specifying the

args in resin.conf and starting Resin with 'httpd.exe args'.



Specifiying them in resin.conf results in:



java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:179)
at com.caucho.server.resin.Resin.parseCommandLine(Resin.java:934)
at com.caucho.server.resin.Resin.main(Resin.java:1341)
Can't connect to parent process through socket 1976
Resin needs to connect to its parent.
[Loaded java.util.IdentityHashMap$KeySet from C:\Programme\Java\jdk1.6.0_02\jre\
lib\rt.jar]
[Loaded java.util.IdentityHashMap$IdentityHashMapIterator from C:\Programme\Java
\jdk1.6.0_02\jre\lib\rt.jar]
[Loaded java.util.IdentityHashMap$KeyIterator from C:\Programme\Java\jdk1.6.0_02
\jre\lib\rt.jar]
[Loaded java.io.DeleteOnExitHook from C:\Programme\Java\jdk1.6.0_02\jre\lib\rt.j
ar]



Resin doesn't start up.



Starting httpd.exe with the args

C:\Programme\resin\httpd.exe -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345 -server a

causes Resin to start up correctly saying



"Listening for transport dt_socket at address: 12345
Resin Professional 3.1.2 (built Wed, 18 Jul 2007 11:30:06 PDT)
Copyright(c) 1998-2007 Caucho Technology. All rights reserved.

:

:

"



As I wrote before, partly it works, because I can see the Resin Threads in

the Eclipse Debug perspective.



Interesting thow that specifying the arguments in the resin.conf and with

httpd.exe behaves that different.



Regards Martin







-----Urspr?ngliche Nachricht-----
Von: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] Im Auftrag von Shane Cruz
Gesendet: Dienstag, 14. August 2007 14:36
An: General Discussion for the Resin application server
Betreff: Re: [Resin-interest] 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




________________________________


From: resin-interest-bounces at caucho.com [mailto:resin-interest-bounces at caucho.com] On Behalf Of MORAWETZ Martin
Sent: Tuesday, August 14, 2007 7:09 AM
To: General Discussion for the Resin application server
Subject: [Resin-interest] Debugging Resin Apps in/with Eclipse



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






"Diese E-Mail sowie jeglicher Anhang sind vertraulich und ausschlie?lich f?r den/die bezeichneten
Adressaten bestimmt. Diese Mitteilung kann rechtlich gesch?tzte, firmeninterne oder anderweitig
vertrauliche Informationen enthalten, deren Weitergabe ohne unsere Zustimmung strengstens
untersagt ist. Sofern Sie nicht der beabsichtigte Adressat sind oder diese E-Mail irrt?mlich
erhalten haben, sind Sie nicht autorisiert, diese Mitteilung bekanntzumachen, zu kopieren,
weiterzugeben oder aufzubewahren. Bitte informieren Sie uns in diesem Fall unverz?glich
und vernichten diese E-Mail.

Diese Fu?note dient auch der Best?tigung dar?ber, da? diese E-Mail automatisch auf Computerviren,
anst??ige Inhalte und Einwahlprogramme gescannt wurde."

"The information in this e-mail and in any attachments is confidential and intended solely
for the attention and use of the named addressee(s). This information may be subject to legal,
professional or other privilege and further distribution of it is strictly prohibited without
our authority. If you are not the intended recipient, you are not authorised to and must not
disclose, copy, distribute, or retain this message or any part of it, and should notify us
immediately.

This footnote also confirms that this email has been automatically scanned for the presence
of computer viruses, profanities and certain file types."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.caucho.com/pipermail/resin-interest/attachments/20070816/c1709653/attachment-0001.html