Simulate connection error solution for sending and receiving Lotus mail

My project is a Domino server where a user account is used to simulate receiving and sending emails within the specified time. It is actually very simple, but the problems found after running are very large, after three days, no information can be found.

This error occurs when you connect to the domino database by releasing the connection from the CORBA. As we all know, to connect to Domino using Java, you must start the diiop service on the Domino server, in fact, this diiop is based on the CORBA operation, but the jar package provided by Lotus is obviously problematic. By the way, I forgot to say that my environment was domino5.08. At that time, JDK should be 1.3, but I used jdk1.5, so the problem was very serious.

I checked it. It was an error reported by the lotus thread because I used session every time I completed the database operation. recycle (), release the resource, but sometimes the lotus thread cannot be released and the following error is reported. Then, after I open CMD and run the netstat-N command, there is a dead connection to the email server. As the program continues to run, there are more and more dead connections.

Exception in finalizer
Org. Omg. CORBA. inv_objref: vmcid: 0x49420000 minor code: 64 completed: No
At sun. Reflect. nativeconstructoraccessorimpl. newinstance0 (native method)
At sun. Reflect. nativeconstructoraccessorimpl. newinstance (unknown source)
At sun. Reflect. delegatingconstructoraccessorimpl. newinstance (unknown source)
At java. Lang. Reflect. constructor. newinstance (unknown source)
At java. Lang. Class. newinstance0 (unknown source)
At java. Lang. Class. newinstance (unknown source)
At com. IBM. CORBA. IIOP. replymessage. getsystemexception (replymessage. Java: 93)
At com. IBM. CORBA. IIOP. repimpl. Invoke (repimpl. Java: 307)
At com. IBM. CORBA. Portable. objectimpl. _ invoke (objectimpl. Java: 36)
At Lotus. Domino. CORBA. _ iitemstub. bulkdecrefcount (_ iitemstub. Java: 557)
At Lotus. Domino. CSO. corbafinalizer. Run (corbafinalizer. Java: 79)
At java. Lang. thread. Run (unknown source)
Org. Omg. CORBA. inv_objref: vmcid: 0x49420000 minor code: 64 completed: No
At sun. Reflect. nativeconstructoraccessorimpl. newinstance0 (native method)
At sun. Reflect. nativeconstructoraccessorimpl. newinstance (unknown source)
At sun. Reflect. delegatingconstructoraccessorimpl. newinstance (unknown source)
At java. Lang. Reflect. constructor. newinstance (unknown source)
At java. Lang. Class. newinstance0 (unknown source)
At java. Lang. Class. newinstance (unknown source)
At com. IBM. CORBA. IIOP. replymessage. getsystemexception (replymessage. Java: 93)
At com. IBM. CORBA. IIOP. repimpl. Invoke (repimpl. Java: 307)
At com. IBM. CORBA. Portable. objectimpl. _ invoke (objectimpl. Java: 36)
At Lotus. Domino. CORBA. _ iitemstub. bulkdecrefcount (_ iitemstub. Java: 557)
At Lotus. Domino. CSO. corbafinalizer. Run (corbafinalizer. Java: 79)
At java. Lang. thread. Run (unknown source)

If the connection is released normally, the following message is displayed:
Connection closed: host = 10.68.100.233 (port 63148)

I stayed at the client for three days. At first I thought there was a problem with the thread I wrote. Later I thought there was a problem with JDK and finally decided whether there was a problem with the jar package provided by Domino.

Then, I put the jar package of domino6.5 under classpath, and the problem was solved. It seems that to use a JDK higher version, we need to use the jar package provided by the Higher version of Domino. Please remember!