We are using Webmethods Integration Server 18.104.22.168 (build 315) on a Solaris 10 platform for our client and we have a very strange behavior not reproducible and not frequent !
I’ve tried to find something relevant in the Webmethod tech forum but I don’t succeed in so I create this post.
I hope I use the good forum to post my message.
We have 4 I.S. distributed on 2 solaris 10 servers. And we have some trouble with one of those 4 I.S. on only one server (and always the same I.S., we don’t have notice the trouble on the other I.S. deployed on this server).
Many packages are deployed on these I.S. (and some of them are deployed on the 2 I.S. in the same time).
Those packages are some OOB Webmethod packages and some others are our owned packages.
Sometimes (very rare, no more than one time per year) our client create a troubleshooting ticket because of services not available anymore.
It was not the same package each time the trouble occured (but each time one of our owned package).
We have checked the server.log and no weird logs appeared.
We have tried disable then enable or unload then load package but nothing works.
We have also noticed that package status on GUI are not consistent with real package status.
When the trouble appears, the only way we have found to get a steady behavior is to stop and restart the I.S.
Is someone has noticed such behavior and find a way to fix it on its integration server ?
In order to be efficient, the next time it will arrive, what are the best practices to find the reason why it happens when we notice such a weird behavior ?
Thanks in advance for your answer ?