Websphere 6.1 debugging experience

Hi,
Anyone experienced problems similar to those described here:
http://www.jetbrains.net/jira/browse/IDEADEV-25155 ?

If so, any additional information about your environment and debug scenarios is welcome.
In the issue it is stated that IDEA 6 works well with WS 6.1, while 7.0 does not. Our experience shows that IDEA version does not
matter - we noticed this behaviour on both versions. However, we cannot reliably reproduce it and cannot say anything about the
cause yet. We just see that for some reason WebSphere's VM stops responding to debugger's requests.
I tried playing with IBM's VM JIT and on my machine and it helped - "-Xjit:disableinlining" makes difference. However, on another
machine it did not help.

Such behaviour makes me think that the problem is in IBM's VM implementation of JDWP interface - perhaps some JDI call or a sequence
of calls causes VM to hang. So any additional information on the problem could help us to find the reason.

Thanks in advance,

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


4 comments
Comment actions Permalink

This is one most annoying me every time, If it happens I am stopping debugger and everything works well. I sent you couple of times snapshots about this, u replied back to me it is not IDEA problem. You are correct about IDEA version it happened 6 and happening now. I included the “-Didea.debugger.keep.temp.objects=false” in Idea.exe.vmoptions but no difference.

0
Comment actions Permalink

me it is not IDEA problem


I still belive it is the problem of IBM's jdk. Just because Sun's jdk works fine. But if we could find out what causes the problem,
then it might be possible to workaround it somehow. (similar to "idea.debugger.keep.temp.objects" option)

I included the "-Didea.debugger.keep.temp.objects=false" in Idea.exe.vmoptions but no difference.


This workaround was applicable to IBM JDK version 1.4.2. Seems like for newer jdk version (1.5) this is not the issue.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

mine is websphere 6.0.x, still that param is valid for my environment.

0
Comment actions Permalink

Yes, I see this happening every now and them. Usually it's not a big deal -- when it happens, I just disconnect from the remote VM and reconnect.

I'm using WebSphere 5.1:
Host Operating System is Windows XP, version 5.1
Java version = J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT disabled), Java Compiler = , Java VM name = Classic VM

0

Please sign in to leave a comment.