Problem solved in using JDE/JPDA to remotely debug our Weblogic EJB
application! The problem was that the production implementation of
JDK1.2.2 on solaris does not fully support JPDA. The documentation on
the Sun site regarding this matter is somewhat contradictory. In one
place, http://java.sun.com/products/jpda/readme.html, it implied that
the production implementation is supported. In another place,
http://java.sun.com/products/jpda/faq.html#QG0, it is flatly stated that
the production implementation is not supported. This was trickly because
some applications can be debugged. The first thing I did was try a small
sample application and it worked. What the precise problem is that
prevented weblogic I can't say.
Thanks to all those that offered their assistance!
Chuck Irvine
Sprint
-----Original Message-----
From: paulk [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 26, 2000 5:47 PM
To: Irvine, Chuck R.
Cc: paulk; jde; Justin.Dickmann; java-debugger
Subject: RE: Help! Using JDEbug for Remote Weblogic Debugging
At 07:20 PM 9/26/00 -0500, Chuck Irvine wrote:
>Paul,
>
>No luck with putting our server in debug server mode. We included
>jpda.jar at the front of the classpath. The only thing we have in our
>LD_LIBRARY_PATH is the path to the jpda libraries. Very frustrating.
>
Since the problem seems to be with the socket, I would work very hard to
ensure that the socket library included with JPDA is the one being
loaded.
For example, you migh consider looking around your system for any other
versions and renaming them temporarily to ensure that they don't get
loaded.
- Paul
>The good news is, though, we did get remote debugging to work with the
>debugger in server mode, just as Justin was able to do. I've got a
>ticket open with BEA. They should be calling me tomorrow. Will tell you
>what they say.
>
>Thanks!!
>
>Chuck
>
>-----Original Message-----
>From: paulk [mailto:[EMAIL PROTECTED]]
>Sent: Monday, September 25, 2000 4:32 PM
>To: Irvine, Chuck R.
>Cc: paulk; Justin.Dickmann; jde
>Subject: RE: Help! Using JDEbug for Remote Weblogic Debugging
>
>
>At 06:24 PM 9/25/00 -0500, you wrote:
>>Hi Paul,
>>
>>Hope I'm not bothering you. If I am, please ignore.
>>
>>My comrades are looking to me to get remote weblogic debugging going.
>>Your previous message indicated that you might be familiar with this
>>subject.
>>
>>Any help would be appreciated.
>>
>
>Hi Chuck,
>
>I have no experience with Weblogic. However, I believe the basic
problem
>is
>that you are trying to use JDK 1.2.2 to launch Weblogic as a JDPA
server
>without including the requisite JPDA libraries in the launch command.
>(Remember JDK 1.2.2 itself antedates JPDA and thus has no knowledge of
>JDPA.) I have a couple of suggestions. First, assuming that you have
>installed the JPDA backward compatibility package, include
>jpda/lib/jpda.jar on the classpath of the command that launches
>WebServer.
>Secondly, make sure that jpda/lib/libdt_socket.so and jdpda/lib/jdwp.so
>are
>on the LD_LIBRARY_PATH of the command that launches Webserver. Make
sure
>in
>particular that jpda/lib/libdt_socket.so shadows any other version of
>libdt_socket.so on your system.
>
>Please let me know whether or not these suggestions work.
>
>- Paul
>
>>
>>-----Original Message-----
>>From: Irvine, Chuck R.
>>Sent: Monday, September 25, 2000 3:39 PM
>>To: 'paulk'; 'jde'
>>Subject: RE: Help! Using JDEbug for Remote Weblogic Debugging
>>
>>
>>Very sorry.
>>
>>Solaris 5.6.
>>Weblogic 4.5.
>>Visibroker 3.4.
>>
>>Thanks!!
>>
>>Chuck
>>
>>-----Original Message-----
>>From: paulk [mailto:[EMAIL PROTECTED]]
>>Sent: Monday, September 25, 2000 2:55 PM
>>To: Irvine, Chuck R.; jde
>>Cc: paulk
>>Subject: Re: Help! Using JDEbug for Remote Weblogic Debugging
>>
>>
>>At 01:25 PM 9/25/00 -0500, Chuck Irvine wrote:
>>>We are trying to launch our Weblogic (EBJ) application with arguments
>>to
>>>allow for remote debugging from JDE. I can successfully launch and
>>debug
>>>a small test program, but when I try to launch our Weblogic server, I
>>>get the error referred to below: "Error [4] ...". I've poked around
on
>>>usenet, but have only found postings that report the same problem -
no
>>>one has posted a solution yet. Your help is greatly appreciated!
>>
>>
>>Platform?
>>
>>
>>- Paul
>>
>>>Chuck Irvine
>>>Sprint
>>>
>>>-----Original Message-----
>>>From: Chou, Carey
>>>Sent: Monday, September 25, 2000 11:59 AM
>>>To: Chuck R. Irvine
>>>Subject:
>>>
>>>
>>>
>>>
>>>
>>>Error [4] in accept() call!
>>>err:: Interrupted system call
>>>Socket transport failed to init.
>>>dt_socket transport error; accept failed, rc = -1
>>>
>>>
>>>
>>>exec /usr/java1.2/bin/java -Xdebug -Xnoagent -Djava.compiler=None
>>>-Xrunjdwp:transport=dt_socket,server=y,suspend=n -Xmx64m -Xms64m
>>>-classpath
>>>/sets/tools/CM-PIT-1/CmAppServer-1-S11/weblogic451sp11boot.jar:/sets/
t
>o
>>o
>>>ls/weblogic/classes/boot::/sets/tools/CM-PIT-1/CmAppServer-1-S11/clas
s
>e
>>s
>>>12.zip:/sets/tools/tpbroker/lib/vbjapp.jar:/sets/tools/tpbroker/lib/v
b
>j
>>o
>>>rb.jar:/sets/tools/CM-PIT-1/CmAppServer-1-S11/cmarch.jar:/sets/tools/
C
>M
>>-
>>>PIT-1/CmAppServer-1-S11:/sets/tools/CM-PIT-1/CmAppServer-1-S11/cmprop
s
>.
>>j
>>>ar
>>>-Dweblogic.class.path=/sets/tools/CM-PIT-1/CmAppServer-1-S11/weblogic
4
>5
>>1
>>>sp11.jar:/sets/tools/weblogic/license:/sets/tools/weblogic/classes:/s
e
>t
>>s
>>>/tools/weblogic/lib/weblogicaux.jar:/sets/tools/CM-PIT-1/CmAppServer-
1
>-
>>S
>>>11:/sets/tools/CM-PIT-1/CmAppServer-1-S11/cmserver.jar:/sets/tools/CM
-
>P
>>I
>>>T-1/CmAppServer-1-S11/CosNotification.jar:/sets/tools/CM-PIT-1/CmAppS
e
>r
>>v
>>>er-1-S11/bsh-1.0.jar:/sets/tools/CM-PIT-1/CmAppServer-1-S11/junit.jar
>>>-Dweblogic.home=/sets/tools/weblogic
>>>-Dweblogic.system.home=/sets/tools/CM-PIT-1/CmAppServer-1-S11
>>>-Dweblogic.system.name=cmappserver1
>>>-Dweblogic.httpd.documentRoot=public_html/ -Djava.security.manager
>>>-Djava.security.policy==/sets/tools/CM-PIT-1/CmAppServer-1-S11/weblog
i
>c
>>.
>>>policy -Dorg.omg.CORBA.ORBClass=com.visigenic.vbroker.orb.ORB
>>>-Dorg.omg.CORBA.ORBSingletonClass=com.visigenic.vbroker.orb.ORB
>>>com.sprint.arch.server.Server cmappserver
>>>
>>>
>>>
>>
>>
>>
>
>
