Hi!
Jeff McArthur wrote:
> I have a problem debugging a redeployed bean. Here are the steps I took:
>
> 1) Redeployed a bean (start server, touch .jar in deploy directory)
> 2) Connected a remote debugger to JVM
> 3) Set a breakpoint, ran a client...no break in EJB
> 4) Reboot jBoss (bean now deployed in startup)
> 5) Reattach debugger
> 5) Run client, voila! the EJB breakpoint is hit
>
> NOTE-debugger was running throughout;debug-connection auto-terminated after
> step 4
>
> I'd think this were the debugger if it weren't for the fact that rebooting
> the server "fixes" the problem. I'm wondering if redeployment loads the
> bean differently (maybe they don't listen on the debugger port after
> redeployment?).
>
> I want to iterate <change-code, make-jar, deploy, debug> without stopping
> servers or debuggers, basically.
The problem might be that EJB's are loaded into separate classloaders,
and I'm not sure if your debugger connects to the right classloader, or
how that works.
I guess this is dependent on the debugger architecture.
If you do a redeploy, can you verify that you are actually getting the
new code running?
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
