cancel
Showing results for 
Search instead for 
Did you mean: 

HELP! : Problem with SAPJ2EE engine, JCO and eisconnector

Former Member
0 Kudos

Hi:

sorry for the subject capitals, but we have a serious problem.

Our portal installation: Unix - EP6 - SP2 - PATCH 3 - HF7 + SAPJ2EE engine WAS PL-19

We have an application developed in java - JCO that connects to the SAPR3 back-end system. Everything works fine whether a few number of users are working with the java application or no error/exception has occurred.

If multiple users (10 or more) runs java appl or a severe error/exception occurs, then system seamlessly hungs and Eisconnector pool doesn't give more JCO connections to another users. At that moment, the application seems to be hung for everybody and the unique way to solve the problem is to restart the eisconnector service.

As another user post, I'm thinking to create a shortcut at my WXP-desktop to stop-start eisconnector with a mouse click,

Is this really a SAP J2EE engine bug?

How can i fix the eisconnector pool problem without upgrade the Portal version o J2EE engine?

Is there any way to upgrade the "connector parts" only?

Thanks in advance.

Best regards.

Agustin Alvarez

Message was edited by: Agustin Alvarez

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi.

Yes the application open and release connections in all functions of java code. In a few users scenario with a normal application execution, there is no problem.

The problem become with many users and whether a java exception occurred. One user gets an red-exception-screen from server and nobody more can execute the application again. If you restart connectors, all works fine again.

We've revised the java code finding all R3 connection functions to avoid uncontrolled exceptions. In that functions we've inserted a "try-catch" code to force release the connection.

Thanks,

Agustin Alvarez.

Former Member
0 Kudos

Hello Agustin,

I've had this problem as well... very frustrating indeed. Take a look at this post:

/thread/8950 [original link is broken]

Moving to patch 4 helped the situation but did not entirely fix it. In the end SAP logged into the client EP and spent a couple of days fooling around with it. Try the suggestions in the thread above... if they don't help let me know.

Cheers,

Mike

Former Member
0 Kudos

Hi Agustin,

does the application release the pool entry after execution?

Kind regards

Francisco