Dynamic JDE Connector Issue of Increasing Handles Count leads to OutOfMemory and after resolving it gives NullPointerException

Question

We’re trying to use dynamic java connector for JDE9.0 and facing issue of increased Handles count for the process.

Scenario:

Calling Dynamic JDE connector in parallel with multiple calls simultaneously.

The implementation process of executing BSFN is as follows:

1) Login method has all credentials and return sessionID

int sessionID =   
Connector.getInstance().login(username.trim(), password.trim(), env.trim(), role.trim());
…

2) ExecuteBSFN has input parameters as module, bsfnName and inputfile (input data to bsfn)

…..

ExecutableMethod execMethod = bsfnMethod.createExecutable();
execMethod.resetValues();
Map<String, String> input = inputParams(moduleName, bsfnName, inputFile);

if(input != null)
   execMethod.setValues(input);

CallObjectErrorList errorList = execMethod.executeBSFN(sessionID);
Map output = execMethod.getValues();
….

3) Logout:

Connector.getInstance().logoff(sessionID);    

In this case we observed that Handles count for the process keeps on increasing even though we used logoff() method and eventually leads to OutOfMemory.

In Order to resolve this issue in logout implementation, after doing logoff we called:

       Connector.getInstance().shutDown();

In this case we observed that on it throws null pointer exception for subsequent calls. Does anyone know how to overcome this situation?

Answer 1

You should review if the BSFN called from the user session prevented the logout by reviewing the enteprise server callobject kernel jde log files as the BSFN is still running asynchronously in enterprise server callobject kernel.

Connector.getInstance().shutDown(); will iterate through all the active user session and call Connector.getInstance().logoff(sessionID);.

So if there are other active session running business function , shutDown will logout the session in middle of BSFN execution and will cause null pointer exception for the logged out session.

Answer 2

If you have multiple sessions for JDE then Connector.getInstance().shutDown() it not going to work because shutDown() will close all the active sessions that's why you are getting null pointer exception to the other active user.

For your Handles count and OutOfMemory, you can close the particular session like

Step 1: logoff the user by session id

Connector.getInstance().logoff(sessionID);

Step 2: Notify the JDE for shutting down the current session it will solve your handle count and OutOfMemory issue

                        NotificationManager.notifyEvent(new JdeEvent() {

                            @Override
                            public Object getSource() {
                                return Connector.getInstance();
                            }

                            @Override
                            public String getName() {
                                return "SHUTDOWN";
                            }
                        });