🚀 go-pugleaf

Simeon Leyzerzon wrote:

> I've followed the instructions and configured debugging on a remote box for JBX:
> 
> Added the following to the remote WebLogic server startup scipt:
> 
> JAVA_OPTIONS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5006
> 
> In JBuilder I've created a remote debuggin configuration whereby I attach to the remote box using port 5006
> 
> What I'm getting as a result of this configuration is JBX stops at the first breakpoint in the project, but then all the debuggin options (step in, over, out) are greyed out(disabled).  
> 
> I'm debugging a servlet, it's deployed on WLS 8.1 sp2 on Solaris.
> 
> Am I missing any required steps?
> Thank you in advace for your help.
> Simeon
> 

On which OS are you running JBuilderX?

Is your project using the same JDK revision as the WebLogic instance 
(JDK 1.4.2)?

-- 

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
     http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
     http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
     http://www.visi.com/~gyles19/fom-serve/cache/1.html

Lori,

JBX is running on Win XP.  I have the same JDK (1.4.2_03) locally and on WebLogic instance on Solaris box.

Thank you for your help!
Simeon


"Lori M Olson [TeamB]" <javadragon@techie.com> wrote:
>Simeon Leyzerzon wrote:
>
>> I've followed the instructions and configured debugging on a remote box for JBX:
>> 
>> Added the following to the remote WebLogic server startup scipt:
>> 
>> JAVA_OPTIONS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5006
>> 
>> In JBuilder I've created a remote debuggin configuration whereby I attach to the remote box using port 5006
>> 
>> What I'm getting as a result of this configuration is JBX stops at the first breakpoint in the project, but then all the debuggin options (step in, over, out) are greyed out(disabled).  
>> 
>> I'm debugging a servlet, it's deployed on WLS 8.1 sp2 on Solaris.
>> 
>> Am I missing any required steps?
>> Thank you in advace for your help.
>> Simeon
>> 
>
>On which OS are you running JBuilderX?
>
>Is your project using the same JDK revision as the WebLogic instance 
>(JDK 1.4.2)?
>
>-- 
>
>Regards,
>
>Lori Olson [TeamB]
>
>------------
>
>Save yourself, and everyone else, some time and search the
>newsgroups and the FAQ-O-Matic before posting your next
>question.
>
>Google Advanced Newsgroup Search
>     http://www.google.ca/advanced_group_search
>Other Newsgroup Searches:
>     http://www.borland.com/newsgroups/ngsearch.html
>Joi Ellis's FAQ-O-Matic:
>     http://www.visi.com/~gyles19/fom-serve/cache/1.html

Simeon Leyzerzon wrote:

> Lori,
> 
> JBX is running on Win XP.  I have the same JDK (1.4.2_03) locally and
> on WebLogic instance on Solaris box.
> 
> Thank you for your help! Simeon
> 
> 

Please confirm... Have you checked your Windows XP firewall settings to
make sure that the port you are using for remote debug is completely open?

-- 

Regards,

Lori Olson [TeamB]

How do I test that?  Is there a command I could run from a terminal window on XP?  We've tested on port 5005 & 5006.  Both exibit the same behavior.

Regards,
Simeon


"Lori M Olson [TeamB]" <javadragon@techie.com> wrote:
>Simeon Leyzerzon wrote:
>
>> Lori,
>> 
>> JBX is running on Win XP.  I have the same JDK (1.4.2_03) locally and
>> on WebLogic instance on Solaris box.
>> 
>> Thank you for your help! Simeon
>> 
>> 
>
>Please confirm... Have you checked your Windows XP firewall settings to
>make sure that the port you are using for remote debug is completely open?
>
>-- 
>
>Regards,
>
>Lori Olson [TeamB]

Simeon Leyzerzon wrote:

> How do I test that?  Is there a command I could run from a terminal window on XP?  We've tested on port 5005 & 5006.  Both exibit the same behavior.
> 
> Regards,
> Simeon
> 

  telnet localhost 5005
  telnet localhost 5006

If it is blocked by your firewall, you'll get something like:

Connecting To localhost...Could not open connection to the host, on port 
5006: Connect failed

-- 

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
     http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
     http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
     http://www.visi.com/~gyles19/fom-serve/cache/1.html

I can definitely telnet to the remote box, but not on these ports.  Just tested...  Are these the ports on which telnet will be listening?
Thank you.
Simeon





"Lori M Olson [TeamB]" <javadragon@techie.com> wrote:
>Simeon Leyzerzon wrote:
>
>> How do I test that?  Is there a command I could run from a terminal window on XP?  We've tested on port 5005 & 5006.  Both exibit the same behavior.
>> 
>> Regards,
>> Simeon
>> 
>
>  telnet localhost 5005
>  telnet localhost 5006
>
>If it is blocked by your firewall, you'll get something like:
>
>Connecting To localhost...Could not open connection to the host, on port 
>5006: Connect failed
>
>-- 
>
>Regards,
>
>Lori Olson [TeamB]
>
>------------
>
>Save yourself, and everyone else, some time and search the
>newsgroups and the FAQ-O-Matic before posting your next
>question.
>
>Google Advanced Newsgroup Search
>     http://www.google.ca/advanced_group_search
>Other Newsgroup Searches:
>     http://www.borland.com/newsgroups/ngsearch.html
>Joi Ellis's FAQ-O-Matic:
>     http://www.visi.com/~gyles19/fom-serve/cache/1.html

Simeon Leyzerzon wrote:

> I can definitely telnet to the remote box, but not on these ports.
> Just tested...  Are these the ports on which telnet will be
> listening? Thank you. Simeon

telnet is just a handy way of checking if specific ports are available.

Your Windows firewall must be configured to allow connections on the 
debugging ports you are using.  If you are using a third-party firewall, 
read up on how to open ports, otherwise read the Windows help on the 
Windows Firewall if you need more information.

-- 

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
     http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
     http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
     http://www.visi.com/~gyles19/fom-serve/cache/1.html

Lori,

On the Unix side I'm seeing the following when stopping at the breakpoint in JBX (netstat command):

nys45a-4703.5006     wnyc110566905.csfb.cs-group.com.3944 17104      0 24820      0 ESTABLISHED

which I'm interpreting as the fact that it connects and no firewall is involved.  But the JBX debugging options are disabled in the IDE.

Regards,
Simeon


"Lori M Olson [TeamB]" <javadragon@techie.com> wrote:
>Simeon Leyzerzon wrote:
>
>> I can definitely telnet to the remote box, but not on these ports.
>> Just tested...  Are these the ports on which telnet will be
>> listening? Thank you. Simeon
>
>telnet is just a handy way of checking if specific ports are available.
>
>Your Windows firewall must be configured to allow connections on the 
>debugging ports you are using.  If you are using a third-party firewall, 
>read up on how to open ports, otherwise read the Windows help on the 
>Windows Firewall if you need more information.
>
>-- 
>
>Regards,
>
>Lori Olson [TeamB]
>
>------------
>
>Save yourself, and everyone else, some time and search the
>newsgroups and the FAQ-O-Matic before posting your next
>question.
>
>Google Advanced Newsgroup Search
>     http://www.google.ca/advanced_group_search
>Other Newsgroup Searches:
>     http://www.borland.com/newsgroups/ngsearch.html
>Joi Ellis's FAQ-O-Matic:
>     http://www.visi.com/~gyles19/fom-serve/cache/1.html