This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Dear group,
We have a problem with Maximo "hanging" 3 or 4 times a week. It happens
on various times, so there's no structure to recognize.
Suddenly the users get an hourglass and nobody can make any logon to the
system.
Maximo freezes for about 10 to 15 minutes.
When I look in the task manager on the application server, I can see the
JAVA process disappear (go down) and restart itself.
Then Maximo is available again.
We run:
- Maximo 6.2.6 (but we also had it with Maximo 6.2.3 and 6.2.5)
- Websphere 6.0.2.17
- Application server:
o Windows server 2003 SP2 on VMWare
o Java 1.6.0
- Oracle 10G
Since we run on VMWare, IBM will not support our problem.
Is there anybody who had similar problems or any ideas what we can check
or do to tackle this problem?
Many thanks to all in advance.
Ron Sleijpen
Royal Mosa
The contents of this e-mail and attachments, if any, is confidential and only intended for the person(s) to which it is addressed. If you receive this e-mail in error then we kindly request you to inform the sender thereof immediately, and to delete the e-mail and the attachments without printing, copying or distributing any of those.
The publication, copying whole or in part or use or dissemination in any other way of the e-mail and attachments by others than the intended person(s) is prohibited. Koninklijke Mosa BV cannot guarantee the security of electronic communication and is not liable for any negative consequence of the use of electronic communication, including but not limited to, damage as a result of in or non-complete delivery or delay in delivery of any e-mail; the text of the e-mail as sent is decisive. Nor can be guaranteed that this message is free from viruses.
On all our sales offers and email communication regarding sales offers applies our General Conditions of Delivery and Payment of Koninklijke Mosa BV. A copy of these conditions is filed in Dutch language at the Chamber of Commerce in Maastricht. A copy of the General Conditions of Delivery and Payment of Koninklijke Mosa BV is available at
WWW.MOSA.NL and on request a copy will be sent to you by post, fax or email, free of charge.
On all our purchase orders and email communication regarding purchase orders applies our General Terms and Conditions of Purchase of Koninklijke Mosa BV. A copy of these conditions is filed in Dutch language at the Chamber of Commerce in Maastricht. On request a copy of these conditions will be sent to you by post, fax or email, free of charge.
Koninklijke Mosa BV, Meerssenerweg 358, 6224 AL Maastricht, The Netherlands, Chambre of Commerce nr. 14600086
Have you checked the logs? If the Java process is disappearing, it sounds like you are running out of memory in the heap. What do you have the initial and maximum heap size set to?
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Ron Sleijpen
Sent: Thursday, February 02, 2012 2:34 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Maximo "hanging" for 15 minutes
Dear group,
We have a problem with Maximo "hanging" 3 or 4 times a week. It happens on various times, so there's no structure to recognize.
Suddenly the users get an hourglass and nobody can make any logon to the system.
Maximo freezes for about 10 to 15 minutes.
When I look in the task manager on the application server, I can see the
JAVA process disappear (go down) and restart itself.
Then Maximo is available again.
We run:
- Maximo 6.2.6 (but we also had it with Maximo 6.2.3 and 6.2.5)
- Websphere 6.0.2.17
- Application server:
o Windows server 2003 SP2 on VMWare
o Java 1.6.0
- Oracle 10G
Since we run on VMWare, IBM will not support our problem.
Is there anybody who had similar problems or any ideas what we can check
or do to tackle this problem?
Many thanks to all in advance.
Ron Sleijpen
Royal Mosa
The contents of this e-mail and attachments, if any, is confidential and only intended for the person(s) to which it is addressed. If you receive this e-mail in error then we kindly request you to inform the sender thereof immediately, and to delete the e-mail and the attachments without printing, copying or distributing any of those.
The publication, copying whole or in part or use or dissemination in any other way of the e-mail and attachments by others than the intended person(s) is prohibited. Koninklijke Mosa BV cannot guarantee the security of electronic communication and is not liable for any negative consequence of the use of electronic communication, including but not limited to, damage as a result of in or non-complete delivery or delay in delivery of any e-mail; the text of the e-mail as sent is decisive. Nor can be guaranteed that this message is free from viruses.
On all our sales offers and email communication regarding sales offers applies our General Conditions of Delivery and Payment of Koninklijke Mosa BV. A copy of these conditions is filed in Dutch language at the Chamber of Commerce in Maastricht. A copy of the General Conditions of Delivery and Payment of Koninklijke Mosa BV is available at
WWW.MOSA.NL and on request a copy will be sent to you by post, fax or email, free of charge.
On all our purchase orders and email communication regarding purchase orders applies our General Terms and Conditions of Purchase of Koninklijke Mosa BV. A copy of these conditions is filed in Dutch language at the Chamber of Commerce in Maastricht. On request a copy of these conditions will be sent to you by post, fax or email, free of charge.
Koninklijke Mosa BV, Meerssenerweg 358, 6224 AL Maastricht, The Netherlands, Chambre of Commerce nr. 14600086
Hello,
We had the problem of JVM automatically restarting. This was happening due to memory leaks in the jvm's. It was happening multiple times in a day.
We installed the WAS 6.0.2.25 fixpack in our servers. This resolved our memory leak issues for the most part.
Hope this helps..
Regards,
Ramesh
Hi,
We do a software ripple start of our report/cron server Tuesday and Thursday nights.
We reboot the UI and Report servers Saturday night. This is a full server reboot.
Could be overkill but we have not had issues since we put that in place.
Dave Bone
--- In MAXIMO@yahoogroups.com, "Ramesh" <ramsubbu16@...> wrote:
>
> Hello,
>
> We had the problem of JVM automatically restarting. This was happening due to memory leaks in the jvm's. It was happening multiple times in a day.
>
> We installed the WAS 6.0.2.25 fixpack in our servers. This resolved our memory leak issues for the most part.
>
> Hope this helps..
>
> Regards,
> Ramesh
>