Re: newbie's question -- basic debugging of n/w app fails

"Nathan Fiedler" <[email protected]> Wed, 3 Nov 2004 13:25:15 -0800 (PST)
Newsgroups gmane.comp.java.jswat.user
Message-ID <[email protected]>
First of all, version 2.20 of JSwat is quite old. There has been at least
one bug fix that should help your situation, so please try the most recent
version.

As for problem #1, it is a networking issue. The JVM was unable to acquire
a socket for debugging, and that could be caused by any of a number of
networking-related issues. I would just as soon recommend you run the
receiver separately and attach JSwat to it.

Upgrading to the final version of JDK 1.5 may also help.

Problem #2, part A should be corrected by using the latest version of
JSwat. Be sure that you set the sourcepath appropriately -- see the
built-in help.

For part B, it sounds like your receiver has a bug. JSwat has no influence
over the threading behavior of the debuggee. The only conclusion I can
draw is that the receiver is doing something wrong.

Thanks

n


Banibrata Dutta wrote:
> Hi,
>
> I am trying to run the JAIN-SIP stack's (NIST) bundled sample
> application using jswat. JAIN-SIP is actually a Java implementation of
> the SIP (VoIP) protocol stack, with a JAIN API over it. This
> application communicates with another peer protocol stack via TCP/IP
> or UDP/IP. The default port (for both TCP & UDP) is 5600 & 5700 (for
> sender & receiver stacks respectively) which are run on the same
> machine, so communication is via loopback interface.
>
> Having given the background, I have tried to run the "sender"
> application as it is, but trying to run the "receiver" application
> inside JSwat. The receiver application when run outside of debugger
> runs just fine, but it is giving problems if I try to run it through
> the debugger (not that both apps are compiled with the -g option).
>
> problem-1) When I start my application, I get this error...
>
> Cause of death:
> ERROR: transport error 202: connect failed: Network is unreachable
> ["transport.ing to the final version of JDK 1.5 may also help.

Problem #2, part A should be corrected by using the latest version of
JSwat. Be sure that you set the sourcepath appropriately -- see the
built-in help.

For part B, it sounds like your receiver has a bug. JSwat has no influence
over the threading behavior of the debuggee. The only conclusion I can
draw is that the receiver is doing something wrong.

Thanks

n


Banibrata Dutta wrote:
> Hi,
>
> I am trying to run the JAIN-SIP stack's (NIST) bundled sample
> application using jswat. JAIN-SIP is actually a Java implementation of
> the SIP (VoIP) protocol stack, with a JAIN API over it. This
> application communicates with another peer protocol stack via TCP/IP
> or UDP/IP. The default port (for both TCP & UDP) is 5600 & 5700 (for
> sender & receiver stacks respectively) which are run on the same
> machine, so communication is via loopback interface.
>
> Having given the background, I have tried to run the "sender"
> application as it is, but trying to run the "receiver" application
> inside JSwat. The receiver application when run outside of debugger
> runs just fine, but it is giving problems if I try to run it through
> the debugger (not that both apps are compiled with the -g option).
>
> problem-1) When I start my application, I get this error...
>
> Cause of death:
> ERROR: transport error 202: connect failed: Network is unreachable
> ["transport.c",L41]
> ERROR: JDWP Transport dt_socket failed to initialize,
> TRANSPORT_INIT(510) ["debugInit.c",L497]
> JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
>
> FATAL ERROR in native method: JDWP No transports initialized,
> jvmtiError=JVMTI_ERROR_INTERNAL(113)
>
>
> problem-2) If I run the debugee application (receiver) in a standalone
> JVM and then "attach" to it via JSwat, I am able to do that. But on
> attaching, I do not see the application source-code in the source-pane
> in JSwat. Also, after I set breakpoints in the "attached" application,
> when i do "RESUME", the main listener thread keeps spawning at a
> high-rate and they keep becoming ZOMBIEs.
>
> Could someone help me with these problems ?
>
> thanks & regards,
> Banibrata.