Hi Paul,
thanks for your prompt response. I am not sure I have tried JDEE's new interface.
I have been able to attach to weblogic (the external process)
via a socket/shared memory. Is that what you are referring to?
The problem is that once I attach, it starts printing these messages and bogs down
weblogic so much that I cannot reach the point that I want to
debug. I understand that turning the debug messages off will help. However, is there
something fundamentally different between jdb and other debuggers
like JSwat? While jdb/weblogic gets bogged down and sometimes completely hangs,
JSwat/Weblogic seems to work very smoothly and lot faster for the same
application.
Thanks,
- Neeraj
-----Original Message-----
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 10:21 AM
To: Neeraj Apte
Cc: 'Paul Kinnucan'; [EMAIL PROTECTED]
Subject: Using JDEbug to debug a J2EE app
Neeraj Apte writes:
> Hi,
> I have been trying to use the debugger from the latest beta(5) of JDEE to debug
> an enterprise application running within weblogic, but it keeps
> printing the following messages (I think for every method call or something):
Hi Neeraj,
Those are messages for debugging the debugger. I'll turn them off in the next release.
Have you tried the JDEE's new interface to jdb? You should be able to use it to debug
a weblogic app as it allows attaching to an external process.
- Paul
> -------------------------8<-----------8<--------------------
> Debug message: 3:58:20 PM: EventHandler: sending event
> jde.debugger.EventSetEvent[eventSet=event set, policy:2, count:1 =
> {ClassPrepareEvent in
thread
> ExecuteThread: '12' for queue: 'default'},suspended=false,threadRef=instance of
> weblogic.kernel.ExecuteThread(name='ExecuteThread: '12' for queue:
> 'default'', id=2)]
> Debug message: 3:58:20 PM: EventHandler: sending resume event to [EMAIL PROTECTED]
> Debug message: 3:58:22 PM: EventHandler: VM resumed
> Debug message: 3:58:22 PM: EventHandler: sending resume event to [EMAIL PROTECTED]
> Debug message: 3:58:22 PM: EventHandler: VM resumed
> Debug message: 3:58:22 PM: JDEbug got cmd
> Debug message: 3:58:22 PM: JDEbug firing command event
> Debug message: 3:58:22 PM: proc: 1 got command:
> jde.debugger.CommandEvent[m_procId=1,m_cmdId=3,m_cmdName=finish,m_args=[]]
> Debug message: 3:58:22 PM: JDEbug command is jde.debugger.command.Finish
> Debug message: 3:58:22 PM: JDEbug waiting for cmd
> -------------------------8<-----------8<--------------------
>
> As a result, it's too darn slow and it makes the debugger virtually useless.
>
> Am I doing something wrong in terms of set up?
> Any help would be greatly appreciated.
> Thanks,
>
> - Neeraj
