cannot debug ejb

[ymajoros]

Last week, I had some problem debugging an ejb application, web part.

Now, it seems I can't debug the ejb part (session beans) of a new application I created. The debugger simply doesn't stop on breakpoints on the bean classes.

Seems to me that netbeans is broken again... or am I missing something? Any idea?

[Dan Kolar]

ymajoros napsal(a):
> Last week, I had some problem debugging an ejb application, web part.
>
> Now, it seems I can't debug the ejb part (session beans) of a new
> application I created. The debugger simply doesn't stop on breakpoints on
> the bean classes.
>
> Seems to me that netbeans is broken again... or am I missing something? Any
> idea?
>  
Hi,

 are you using NetBeans 6.1 with patch1 ?

Dan Kolar

[wbossons]

Check to make sure that you are referencing the correct machine in your
debug control panel. Sometimes if you are on a network and then leave
that network, netbeans remembers the machine name you use on your
network and that will not work. Try localhost instead if that's appropriate.

..\Wendy

Dan Kolar wrote:

> ymajoros napsal(a):
>> Last week, I had some problem debugging an ejb application, web part.
>>
>> Now, it seems I can't debug the ejb part (session beans) of a new
>> application I created. The debugger simply doesn't stop on
>> breakpoints on
>> the bean classes.
>>
>> Seems to me that netbeans is broken again... or am I missing
>> something? Any
>> idea?
>>  
> Hi,
>
> are you using NetBeans 6.1 with patch1 ?
>
> Dan Kolar

--
..\Wendy
Wendy Bossons
Senior User Interface Developer
Harvard-MIT Data Center
Office Phone:  [phone]
Email: wbossons <at> hmdc.harvard.edu


[wbossons.vcf]

---

begin:vcard
fn:Wendy Bossons
n:Bossons;Wendy
tel;work:617-384-5701
note:wbossons <at> hmdc.harvard.edu
version:2.1
end:vcard

---

[ymajoros]

What's the debug control panel?

Everything is on a locally installed server, I didn't run it on a remote server.

I tried under netbean 6.0 and 6.1 patch 1.

wbossons wrote:

Check to make sure that you are referencing the correct machine in your
debug control panel. Sometimes if you are on a network and then leave
that network, netbeans remembers the machine name you use on your
network and that will not work. Try localhost instead if that's appropriate.

..\Wendy

Dan Kolar wrote:
> ymajoros napsal(a):
>> Last week, I had some problem debugging an ejb application, web part.
>>
>> Now, it seems I can't debug the ejb part (session beans) of a new
>> application I created. The debugger simply doesn't stop on
>> breakpoints on
>> the bean classes.
>>
>> Seems to me that netbeans is broken again... or am I missing
>> something? Any
>> idea?
>>  
> Hi,
>
> are you using NetBeans 6.1 with patch1 ?
>
> Dan Kolar


--
..\Wendy
Wendy Bossons
Senior User Interface Developer
Harvard-MIT Data Center
Office Phone:  [phone]
Email: wbossons <at> hmdc.harvard.edu


begin:vcard
fn:Wendy Bossons
n:Bossons;Wendy
tel;work:617-384-5701
note:wbossons <at> hmdc.harvard.edu
version:2.1
end:vcard

[ymajoros]

Now, it seems I have this problem when trying to debug an application client. Don't know if it would be the same for a web app.


What's the debug control panel?

Everything is on a locally installed server, I didn't run it on a remote server.

I tried under netbean 6.0 and 6.1 patch 1.

wbossons wrote:

Check to make sure that you are referencing the correct machine in your
debug control panel. Sometimes if you are on a network and then leave
that network, netbeans remembers the machine name you use on your
network and that will not work. Try localhost instead if that's appropriate.

..\Wendy

Dan Kolar wrote:
> ymajoros napsal(a):
>> Last week, I had some problem debugging an ejb application, web part.
>>
>> Now, it seems I can't debug the ejb part (session beans) of a new
>> application I created. The debugger simply doesn't stop on
>> breakpoints on
>> the bean classes.
>>
>> Seems to me that netbeans is broken again... or am I missing
>> something? Any
>> idea?
>>  
> Hi,
>
> are you using NetBeans 6.1 with patch1 ?
>
> Dan Kolar


--
..\Wendy
Wendy Bossons
Senior User Interface Developer
Harvard-MIT Data Center
Office Phone:  [phone]
Email: wbossons <at> hmdc.harvard.edu


begin:vcard
fn:Wendy Bossons
n:Bossons;Wendy
tel;work:617-384-5701
note:wbossons <at> hmdc.harvard.edu
version:2.1
end:vcard

[wbossons]

When you choose Run|Attach Debugger, there is a panel that pops up.

There is a host setting -- it should refer to your localhost or loopback address.

Also, you may have to check your domain.xml to see if you have debugging allowed. Look for this line ...

<java-config classpath-suffix="" debug-enabled="true" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="">

Make sure that debug-enabled is set to true. Also, verify that the port is correct.

..\W

ymajoros wrote:

What's the debug control panel?

Everything is on a locally installed server, I didn't run it on a remote
server.

I tried under netbean 6.0 and 6.1 patch 1.



wbossons wrote:
  

Check to make sure that you are referencing the correct machine in your 
debug control panel. Sometimes if you are on a network and then leave 
that network, netbeans remembers the machine name you use on your 
network and that will not work. Try localhost instead if that's
appropriate.

..\Wendy

Dan Kolar wrote:
    

ymajoros napsal(a):
      

Last week, I had some problem debugging an ejb application, web part.

Now, it seems I can't debug the ejb part (session beans) of a new
application I created. The debugger simply doesn't stop on 
breakpoints on
the bean classes.

Seems to me that netbeans is broken again... or am I missing 
something? Any
idea?
  
        

Hi,

are you using NetBeans 6.1 with patch1 ?

Dan Kolar
      

-- 
..\Wendy
Wendy Bossons
Senior User Interface Developer
Harvard-MIT Data Center
Office Phone:  [phone]
Email: wbossons <at> hmdc.harvard.edu 


begin:vcard
fn:Wendy Bossons
n:Bossons;Wendy
tel;work:617-384-5701
note:wbossons <at> hmdc.harvard.edu
version:2.1
end:vcard



    

[wbossons.vcf]

---

begin:vcard
fn:Wendy Bossons
n:Bossons;Wendy
tel;work:617-384-5701
note:wbossons <at> hmdc.harvard.edu
version:2.1
end:vcard

---

[ymajoros]

debug-enabled was set to "false", but if I set it to "true", I get this, and the application doesn't start:

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Java Result: 1
Attached JPDA debugger to localhost:9009
debug-Doctorats-app-client:
debug:
BUILD SUCCESSFUL (total time: 44 seconds)

Here is the domain.xml line (with debug-enabled set to false):

 <java-config classpath-suffix="d:/Sun/AppServer/lib/Doctorats-authmodule.jar" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g">

I don't usually attach to the client application by hand (although I tried, and it works). I click on "debug" on my ear project.

wbossons wrote:

When you choose Run|Attach Debugger, there is a panel that pops up.

There is a host setting -- it should refer to your localhost or loopback
address.

Also, you may have to check your domain.xml to see if you have debugging
allowed. Look for this line ...

<java-config classpath-suffix="" debug-enabled="true"
debug-options="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}"
javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate
-keepgenerated -g" system-classpath="">

Make sure that debug-enabled is set to true. Also, verify that the port
is correct.

..\W

[ymajoros]

update (kind of unsatisfaying solution):

If I set debug-enabled to true in domain.xml, and I then run my project in netbeans (clicking "debug" fails), then attach the debugger... it works! Is this some bug in netbeans? There are some issues with that (unable to recompile a class while running, more ui gestures to simply debug the application, ...).

Side note, far less important for me: whatever the situation, netbeans always asks this question before debugging: "Is server running in debug mode?". Whatever the truth is, if you say "yes", you get an error message. I think I don't get the point. Can't it ask the server without bugging the user, and take appropriate steps?



debug-enabled was set to "false", but if I set it to "true", I get this, and the application doesn't start:

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Java Result: 1
Attached JPDA debugger to localhost:9009
debug-Doctorats-app-client:
debug:
BUILD SUCCESSFUL (total time: 44 seconds)

Here is the domain.xml line (with debug-enabled set to false):

 <java-config classpath-suffix="d:/Sun/AppServer/lib/Doctorats-authmodule.jar" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g">

I don't usually attach to the client application by hand (although I tried, and it works). I click on "debug" on my ear project.

wbossons wrote:

When you choose Run|Attach Debugger, there is a panel that pops up.

There is a host setting -- it should refer to your localhost or loopback
address.

Also, you may have to check your domain.xml to see if you have debugging
allowed. Look for this line ...

<java-config classpath-suffix="" debug-enabled="true"
debug-options="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}"
javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate
-keepgenerated -g" system-classpath="">

Make sure that debug-enabled is set to true. Also, verify that the port
is correct.

..\W

[ymajoros]

Ok, I reposted this in a new thread, to make it clearer.


update (kind of unsatisfaying solution):

If I set debug-enabled to true in domain.xml, and I then run my project in netbeans (clicking "debug" fails), then attach the debugger... it works! Is this some bug in netbeans? There are some issues with that (unable to recompile a class while running, more ui gestures to simply debug the application, ...).

Side note, far less important for me: whatever the situation, netbeans always asks this question before debugging: "Is server running in debug mode?". Whatever the truth is, if you say "yes", you get an error message. I think I don't get the point. Can't it ask the server without bugging the user, and take appropriate steps?

ymajoros wrote:

debug-enabled was set to "false", but if I set it to "true", I get this, and the application doesn't start:

FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Java Result: 1
Attached JPDA debugger to localhost:9009
debug-Doctorats-app-client:
debug:
BUILD SUCCESSFUL (total time: 44 seconds)

Here is the domain.xml line (with debug-enabled set to false):

 <java-config classpath-suffix="d:/Sun/AppServer/lib/Doctorats-authmodule.jar" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g">

I don't usually attach to the client application by hand (although I tried, and it works). I click on "debug" on my ear project.

wbossons wrote:

When you choose Run|Attach Debugger, there is a panel that pops up.

There is a host setting -- it should refer to your localhost or loopback
address.

Also, you may have to check your domain.xml to see if you have debugging
allowed. Look for this line ...

<java-config classpath-suffix="" debug-enabled="true"
debug-options="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}"
javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate
-keepgenerated -g" system-classpath="">

Make sure that debug-enabled is set to true. Also, verify that the port
is correct.

..\W