Enterprise Edition & WebLogic Debugging

[Robert Gardner]

Configuration Information:
Product: Visual Cafe for Windows Enterprise Suite 3.0

I have Visual Cafe Enterprise Edition 3.1a and WebLogic 4.5.1, all
using JDK 1.2.2. I am trying to debug a servlet from within WebLogic
using Attach to Process.

If I set my project to be an EJB project I can launch WebLogic from
within VC, but it launches a JDK 1.1 debuggable VM, not a 1.2
debuggable VM, so I am unable to debug.

I have followed all the guidelines the support site for "Configuring
Visual Cafe 3.0x to Run and Debug Programs Using JDK 1.2.x" but a 1.1
debuggable VM still launches.

Is there any way to run WebLogic 4.5.1 within a 1.2 debuggable VM and
enable source-level debugging from VC 3.1a?

[Tim Dutton (Symantec)]

Hi Robert,

Have you tried starting WebLogic out side of Visual Café and then
attaching to the process?

Regards,

Tim Dutton
Internet Tools Technical Support
Symantec Corporation

[shahzad khan]

I have beem having the same problem so I am trying your solution of
attaching to a process. However, When I pull up the
File->AttachToProcess and click on any host it just says 'No VMs
found' Why is it unable to locate the VMs or more specifically what
do I have to do to make it reckognize them?

Shahzad

[Tim Dutton (Symantec)]

Shahzad,

Did you start WebLogic first?

[Jim Despelteau]

I'm trying to go down this road also. I have WL 4.5.1, Enterprise Suite
3.1.a, and a 1.2 VM on NT 4.0 SP6. The previous posters are correct in
noting that if just launch your 1.2 VM outside of Cafe, when you proceed
from within Cafe to "Attach to Process", the VM's will not be listed. What
you have to do is modify the way you launch the WebLogic server by using
debugvm.exe instead of java.exe. I have successfully done this to start the
weblogic server. I then bring up Cafe, Attach to Process, and successfully
connect to the weblogic server. This is verified via the Messages screen
which says words to the effect that "connected to host". I am also then
able to open the source file for my EJB and set a breakpoint. However, when
I then execute a client that attempts to call the EJB method, the
debugvm.exe (weblogic server) access violates in javai.dll. I know my
client works because I can execute the client to a java.exe started weblogic
server without problems. I know my bean works because I've successfully
debugged the same bean using a "WebLogic Enterprise Bean project" and hot
deploying the bean to the server. One thing I have noticed is that when
Cafe starts the weblogic server, you end up with 2 processes, debugvm.exe
and java.exe. When I manually launch the weblogic server with
\VisualCafe\Java2\bin\debugvm.exe, I only get one process, debugvm.exe. I
can't seem to find any documentation on any additional magic to starting
debugvm.exe. Can this be done?

Tim Dutton (Symantec) <nospa...@devtools.symantec.com> wrote in message
news:38dc89f1....@service.symantec.com...

[Tim Dutton (Symantec)]

Hi Jim,

I will look at this post and respond shortly.

[shahzad khan]

Thanks for all your responses.

The original question though remains unanswered, can you run a 1.2VM.
It seems that "Symantec Debug VM Loader 2.0 for JDK 1.1" is always
loaded up in all of these senarios.

Thanks

[Tim Dutton (Symantec)]

Hi Shahzad,

The reason that you are seeing this is because although you can plug
in a different JDK, the internal VM is still 1.1.7a. The IDE will use
your JDK for debugging and execution, but there will still be hooks
into the internal VM.

[Tim Dutton (Symantec)]

Jim,

You may want to disable the jit and see if that helps. Let me know if
you need further assistance.

[Jim Despelteau]

Tim,

Setup - Cafe 3.1a, WL 4.51, JDK 1.2.2 on NT4 SP6

I had jit disabled all along, so that's not the issue. I have made
significant progress since then, but still have one more issue. I found a
patch under the VisualCafe/platforms directory called vcdbg_generic_1.2,
unzipped it and followed the directions. After that, the debugvm.exe
problems disappeared, I was able to set breakpoints in EJB's and debug
inside Weblogic. But I was only able to do this for EJB's that I wrote
using Cafe's Enterprise Bean Project. I was not able to do this for EJB's
that were written, compiled, and deployed externally to Cafe projects. I
perceive the root of my problem has to do with differences in the way Cafe
deploys EJB's to the Weblogic server, or problems with the Weblogic server
being able to locate source/class files for the EJB.

The error I see now is when I try to set a breakpoint in the EJB source
file, Cafe complains that
"Debug (14:19:54): No code at line 114 for file foo.java: file has not been
parsed completely or the file is built with optimizations turned on.", and
the breakpoint is not set. The bean is fine, I can successfully deploy and
exercise the bean's methods outside of the debugger.

The sequence is this (all on one machine)
1. start ddservices.exe
2. start the Weblogic server with debugvm.exe
3. start up Cafe
4. Attach to the Weblogic server process
5. Under Project/Options, add paths to the class and java files for the EJB
class and java files
6. Open the EJB source file
7. Set breakpoint (results in above error)

I have verified that the file is not built with optimizations turned on, and
is built with the 1.2.2 JDK with debugging info on.
Once again I have successfully done this with an EJB that I built within a
Cafe EJB Project, and deployed using Cafe's wizardry. There's no magic to
this, it just adds a jar file under the Weblogic/classes directory. In
order to use Cafe's Weblogic debugging, are there very specific requirements
as to how an EJB needs to be deployed?

Secondly, where should I configure the Cafe project to tell the debugger how
to find the source files?

In case you're interested, you've got a site license riding on our ability
to make this work....

TIA,

Jim Despelteau

[Tim Dutton (Symantec)]

Hi Jim,

I am looking into this now, and will respond on the new thread that
you posted in this group.

[Todd Carmichael]

You can count on another site license from our company as well if you can
solve this problem.

"Tim Dutton (Symantec)" <nospa...@devtools.symantec.com> wrote in message

news:38e9b65e...@service.symantec.com...

[Tim Dutton (Symantec)]

Hi Todd,

Jim has solved his own issue and he has posted it on a thread later in
this group titled:
"Re: Success at last - Cafe31a, WL 4.51, and EJB breakpoints"

So I guess you owe him the site license:)

[Todd Carmichael]

I have not had luck yet. I have tried numerous configurations without any
luck. Currently when I launch debugvm and try to launch my servlet, I get
an access violation in javai.dll

"Tim Dutton (Symantec)" <nospa...@devtools.symantec.com> wrote in message

news:38fa10ee...@service.symantec.com...

[Tim Dutton (Symantec)]

Todd,

Take a look at this document in our online Knowledge Base:

Title: 'Error: "Invalid Page Fault in Module JAVAI.DLL" when Trying to
Load Scientific Notation Numbers Using the JDBC-ODBC Bridge'
Document ID: 199872884644
Web URL:
http://service1.symantec.com/SUPPORT/devtools.nsf/docid/199872884644&src=w

[Todd Carmichael]

I am having more success. I got past this error by following the directions
"Configuring Visual Cafe 3_0x to Run and Debug Programs Using JDK
1_2_x.htm". I can now attach to debugvm and set a breakpoint following
JimD's instructions. However, when I try to access my servlet page from a
browser, the browser simply hangs and my breakpoint is never hit.

I know that is not much information to debug.

"Tim Dutton (Symantec)" <nospa...@devtools.symantec.com> wrote in message

news:38ea1be1...@service.symantec.com...

[Tim Dutton (Symantec)]

Todd,

Thanks for the follow up.

[Todd Carmichael]

Note, it debugging a servlet still does not work.

"Tim Dutton (Symantec)" <nospa...@devtools.symantec.com> wrote in message

news:38fea54f...@service.symantec.com...

[Tim Dutton (Symantec)]

Todd,

We will have to continue to look at this.