Java and server PANIC

HCL Domino Domino Forum
1

Hi all

I have a rules-based Domino archiving agent written in Java that is causing a server panic when it runs for more than half an hour.

The error it experiences is “PANIC: lookuphandle not allocated”.

I have seen lots of questions about this error on this forum but very few answers. Does anyone know if this could be caused by recycling of objects that are being used by other threads? Or is this more likely to be related to the server running out of memory?

Are there tools for analysing rip files or would I be better off forwarding this to Lotus Support?

If anyone fancies a look at the rip, I can mail it to you or post it here (it is very large though)

Many thanks for any help offered

Marc

2

Subject: RE: Java and server PANIC

We get the same error when trying the following Javacode

RichTextItem rtitem = docMail.createRichTextItem(“Body”);

Vector v_body = new Vector();

v_body.addElement(“any string”);

rtitem.setValues( v_body); // On this command the server chrashes!!!

3

Subject: RE: Java and server PANIC

We are with the sabe problem too… I get this error everytime I try to write to
a RichText Java object.

The error:
Thread=[03EC:007E-060C]
Stack base=0x2119F564, Stack size = 1188 bytes
PANIC: LookupHandle: null handle

The Java code that generates it:
[



rtitem = doc.createRichTextItem(“Body”);

while(message.indexOf(“\n”) != -1) {

// the following line rises PANIC:

rtitem.appendText(message.substring(0, message.indexOf(“\n”)));

rtitem.addNewLine();

message = message.substring(message.indexOf(“\n”)+1);

}

rtitem.appendText(message);
]

The problem is that when I create a Body field with the simple String object,
the new lines aren’t sent.

Does someone have any clue?

Thanks.

José Marcelo

4

Subject: Java and server PANIC

I get this when an agent returns a null instead of a value. I always thought it was a bug in Domino.

5

Subject: Java and server PANIC - more info

Thanks for the response.

After rebooting the server I am getting a slightly different error in the RIP. This time it runs for an hour and half (an improvement) and it is nserver.exe causing the crash with an exception of type “access violation”.

Does this ring any bells?