This content has been marked as final. Show 2 replies
user12006136 wrote:So you have an OS, a VM, an Application (WAS) and then your company code that runs in there.
I am definitely not a java expert, but have no other and have to fix it. Any suggestion, which can help me understand what is going on. is welcome.
And something isn't working.
So you goal is to localize the problem.
It would help if you can replicate it. That would require the following
1. An install of everything some place besides production, like a test box.
2. A way to simulate 'client' traffic - which is messages that look like the messages that already go into the production machine.
3. Then you use 2 to send traffic for long periods of time to 1.
4. At some point if 1 and 2 are right then you will get the same error.
It would help if you can localize the problem. That is a lot easier if you can replicate it. If you can replicate then you can try removing things, generally parts of your company code. If you get to the point where that makes the problem go away then you might have a likely place for a problem (a bug in the code.)
If you can't replicate it then you have to look at logs and hope you can find something strange. That is helped by experience.
Depending on complexity of your company code this can take a long time (excluding just luck.)
One possible solution, if your business allows for it, is to just automatically restart the VM periodically. This is to prevent it from becoming bad in the first place. Might not seem like an ideal solution but it is something that can be implemented quickly.