Java Agent Remote Debugging

HCL Domino Domino Forum
1

I’m trying to remote debug a java agent (runonserver) I’ve written. As written on Ian Connor’s article(see IBM - United States)

I’ve added JavaEnableDebug=1 to the notes.ini and restarted the server. Then I’ve tried to start the java agent and I’ve got an error msg “runtime error” in nserver.exe. With that msg the domino server crashes. Without javaenabledebug=1 (normal mode) the agent works fine.

FYI: The domino server and client is on the same machine (for testing purposes).

Can anybody give me some hints to solve this problem? Or is there another way to debug a java agent code?

Thanx in advance.

-Manuel

2

Subject: See this tip we published

3

Subject: RE: See this tip we published

thanx for your reply.

I’ve tried your guide. Well, I’m using Eclipse instead of Websphere Studio but I think that doesn’t matter :slight_smile:

I’ve enabled javadebug in server notes.ini again and while starting the server the console told me that debug is enabled.

Then I’ve set a breakpoint in Eclipse and created a remote java application debug entry, using host localhost and port 9788. Clicking on Eclipse tells me surprisingly “failed to connect to remote VM. Connection refused”. Doesn’t the javaenabledebug-mode tell the server to listen on port 9788 for a remote debugger?

I think I’m getting stupid not to see the problem why the server isn’t listening on port 9788… can you help me out?

thanx again!

4

Subject: Read the tip again

We only got the debugging to work on a local agent, not a server agent.

Howard

5

Subject: RE: See this tip we published

edit your windows path variable to include the path to the domino jvm as seen here

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/26a4443abbcd46b885256f1d002bef9f?OpenDocument

6

Subject: RE: See this tip we published

Thanx to both of you.

As I’m using a server agent, the dt_socket.dll has to be copied to the domino dir, not notes dir - certainly I was sleeping while doing this…:wink:

to set the path variable should work as well, I guess.

Well, my fault, sorry guys!