|
Donagh
|
 |
« on: August 20, 2010, 08:42:38 pm » |
|
Hello,
We are running maximo 6.2.6 in our development server and we started to experience "performace issues" (slowdowns).
Checking the maxsession table, we discovered hundreds of active connections. We have several utilities that connect via
RMI and apparently they are no longer disconnecting properly after the upgrade.
At first I was concerned that it was a problem with our utilities, so I used the checkmxserver.bat utility on the Maximo
server to test. Here are the steps to reproduce:
1. Run the checkmxserver.bat utility 10 times on both the 6.2.00 machine and the 6.2.6 machine. 2. Connect to the database on both machines and do a "select * from maxsession" query. 3. On the 6.2.00 machine, there is only one row in the table (the MAXIMO default session). On the 6.2.6 machine, there are
eleven rows in the table (one MAXIMO default session and ten MAXADMIN sessions, with MAXADMIN being the login I passed to
checkmxserver.bat)
I noticed that there is a known bug with "idle" sessions on WebSphere, but we are running WebLogic and these sessions are
forcibly closed with a call to MXServer.Disconnect() so they should not be flagged as "idle".
Has anyone else seen this behavior?
Thanks in advance,
Donagh
|