From: "Jacques Le Roux" <
[hidden email]>
> Hi Ray,
>
> Thanks for the tip. Until now in such cases (when wanting more to trace, for instance in classloader, etc.) I used the "stop in
> main" option of Eclipse Debug Configuration, but it's not available when remote debugging. I will put them both in Wiki !
Done
Jacques
> Jacques
>
> From: "Ray" <
[hidden email]>
>> Jacques,
>>
>> You can suspend the JVM through the command line options at start up.
>> Effectively the JVM boots, stops and waits for a debugger to connect and
>> then it continues so you can still use remote debugging. Just put
>> suspend=y in the start options alongside the socket and ports settings.
>>
>> Ray
>>
>>
>> Jacques Le Roux wrote:
>>> I put a note in
http://docs.ofbiz.org/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse :
>>>
>>> The official recommended way for debugging ofbiz is to use remote debugging. The second method : in Eclipse is really helpful
>>> when it comes to debug the framework java code. When someone has screwed up the framework java code (it happens rarely but Adam
>>> is able to do it ;o) and you can't load OFBiz. Then you have no other way than to debug OFBiz using inside debugging...
>>>
>>> I'm not able to debug current trunk version on Windows right now, but if no one beats me on it I will have a look in a couple of
>>> hours...
>>>
>>> Jacques
>>
>
Locked
