mikael
Newbie
Karma: 0
Posts: 5
|
 |
« on: February 26, 2010, 03:09:05 pm » |
|
Hi,
I have a serious problem with Maximo hanging at login. So I get the login screen and when I try to log in Maximo totally hangs.
It looks like Maximo starts normally (nothing unusual in the log files). Also after the hanging there isn't anything in the log files (only those two lines belowappears after hitting login button).
The last lines in the Custom01/logs/MAXIMOSERVER/SystemOut.log logfile are
[26.2.2010 16:25:07:526 EET] 00000037 ServletWrappe A SRVE0242I: [MAXIMO] [/maximo] [/webclient/login/login.jsp]: Initialization successful.
[26.2.2010 16:25:12:768 EET] 00000037 ServletWrappe A SRVE0242I: [MAXIMO] [/maximo] [webclient]: Initialization successful.
We're using Maximo v6.2.1 on a RedHat and the db is Oracle 10g.
I think it may be some kind of a db problem... although I can through to the db with telnet and I can connect to the db e.g. with SQL developer.
Does someone have some idea of what the problem is?
(I have already tried rebooting the system)
Thanks in advance!
-M
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #1 on: March 02, 2010, 07:56:28 am » |
|
try running the config db and restart the server.. if configdb gives the problem try restoredb and then restart the server..\
please try these and let me know if it works....
maybe also be the problem in ear file.. if configdb doesnt work try rebuilding the ear file and deploy it...
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
Razor007
Newbie
Karma: 0
Posts: 5
|
|
« Reply #2 on: March 07, 2010, 08:27:38 pm » |
|
Hi mikael, guess you might have resolved this. Do you mind posting what was the issue..and how you resolved this.
|
|
|
|
|
Logged
|
|
|
|
mikael
Newbie
Karma: 0
Posts: 5
|
|
« Reply #3 on: March 09, 2010, 12:43:25 pm » |
|
Hi and thanks for the replies.
Unfortunately I haven't resolved the problem yet. It's a test system (not the production Maximo) and that's why this has been hanging for a while now...
>>try running the config db and restart the server.. if configdb gives the problem try restoredb and then restart the server..\
>>please try these and let me know if it works....
>>maybe also be the problem in ear file.. if configdb doesnt work try rebuilding the ear file and deploy it...
Configdb tried and also tried a totally another database on another server --> no help
I have also recreated and redeployed the ear but with no luck.
Does websphere has some temporary files that it stores that could cause the problem?
-M
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #4 on: March 10, 2010, 07:17:35 am » |
|
it may be a problem of KPI's or cron task..
If you have lots of KPI's tht are running frequently with complex logic it may be the reason or if the cron tasks are running too frequently it may happen..
it may also happen if the server goes out of memory..
just check the logs.. it will give a hint.
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
mikael
Newbie
Karma: 0
Posts: 5
|
|
« Reply #5 on: March 17, 2010, 08:42:11 am » |
|
Hi,
I got our test system to work. Still I don't know what the actual problem was... I used an old backup of maximo.ear and deployed that and after that it worked.
Regarding Ethens post... We don't use the KPI's (only those are running that is OOTB). We have some cron tasks running at 20 and 30 sec intervals, but those hasn't caused any problems in neither production or test system and those have been running over 2 years. I also checked the memory and it was ok.
Even if the cause of the problem wasn't found so thanks for everyone for their help.
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #6 on: March 23, 2010, 09:15:24 am » |
|
if your old ear worked then probably there was some problem in the jsp files. which cudve been changed sometime during new ear build..
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
|
