Help!! Problem about remote debugging....

My application server is WebLogic 8.1.3 with JDK 1.4.2, there's several J2EE applications are running in the welogic server with different ports. In the startWebLogic.sh of one of the applications, there's the commmand line:

$/bin/java $ $ $ -Dweblogic.Name=$ -Dweblogic.management.username=$ -Dweblogic.management.password=$ -Dweblogic.ProductionModeEnabled=$ -Djava.security.policy="$/server/lib/weblogic.policy" -Dencoding=GBK -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000 weblogic.Server

When I run the remote debugging in Idea, Idea can connect the application server, howover the server seems to be suspended, and if I just stop the remote debugging, the server will go ahead.

The most confused thing is that the case is not always be that, sometimes the remote debugging works good.

9 comments
Comment actions Permalink

Hello truecolor,

Are there any method or exception breakpoints enabled in your project?
Which build of IDEA are you using?

My application server is WebLogic 8.1.3 with JDK 1.4.2, there's
several J2EE applications are running in the welogic server with
different ports. In the startWebLogic.sh of one of the applications,
there's the commmand line:

$/bin/java $ $ $
-Dweblogic.Name=$
-Dweblogic.management.username=$
-Dweblogic.management.password=$
-Dweblogic.ProductionModeEnabled=$
-Djava.security.policy="$/server/lib/weblogic.policy"
-Dencoding=GBK -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000
weblogic.Server

When I run the remote debugging in Idea, Idea can connect the
application server, howover the server seems to be suspended, and if I
just stop the remote debugging, the server will go ahead.

The most confused thing is that the case is not always be that,
sometimes the remote debugging works good.



0
Comment actions Permalink

Yes, there's a default exception breakpoint, but it is not active.
As for method breakpoint, these days, I created a method breakpoint, but I remember that it is my first time to create a such breakpoint, and those days I had no method breakpoint, the application server also would be suspended if to run remote debugging.

The Idea version is 6.0.x, the EAP built.

0
Comment actions Permalink

Hello truecolor,

Is the problem reproduced only while remote debugging or while remote running
too?

Yes, there's a default exception breakpoint, but it is not active.

As for method breakpoint, these days, I created a method breakpoint,
but I remember that it is my first time to create a such breakpoint,
and those days I had no method breakpoint, the application server also
would be suspended if to run remote debugging.

The Idea version is 6.0.x, the EAP built.



0
Comment actions Permalink

The problem is:
1. Start the application server with the command line arguments - "-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=61118" in startWebLogic.sh
2. any operation on web page, OK.
3. start the remote debugging,
4. any operaiton on web page, NO response.
5. stop the remote debugging, the operaion in step 4 will go on.

But the problem is not reproduced every time.

0
Comment actions Permalink

Hello truecolor,

Please replace your /bin/log.xml file by the attached file, run IDEA, reproduce the problem and then post here ]]>/log/idea.log file.

The problem is:

>

1. Start the application server with the command line arguments -
"-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,addressa118" in
startWebLogic.sh

>

2. any operation on web page, OK.

>

3. start the remote debugging,

>

4. any operaiton on web page, NO response.

>

5. stop the remote debugging, the operaion in step 4 will go on.

>

But the problem is not reproduced every time.

>

Attachment not added (general error): "log.xml"

0
Comment actions Permalink

I have the same problem. Actually my colleagues as well. Also it happens only sometimes but more often than not. It helps to reconnect debugger several times. I think this is general problem with Weblogic or debugger platform. I have no idea how to fix it. Any help yould appreciated.

0
Comment actions Permalink

Hi, Nikolay

The log.xml has not been attached.

0
Comment actions Permalink

Yes. this year we began to use WebLogic, and then I encountered this problem.

In the past years, we used Jboss all the while, and I never got this problem.

0
Avatar
Nikolay Chashnikov
Comment actions Permalink

Hmm... Second attempt.



Attachment(s):
log.xml
0

Please sign in to leave a comment.