RelaX!
New Member
Yesterday, all of a sudden the wsa adapter stopped functioning in an operational environment.
If I look with fathom, the dot before the wsa1 container is blue.
If you click on that blue dot it takes about 2 minutes before the wsa configuration page shows but almost all options are grayed out.
The Tomcat 7 servlet engine is running and restarting this service does not have any effect.
The testpage for the servlet engine says WSA: 111 OK
Rebooting th entire database server (OpenEdge 10.2B SP5 32 bit on Windows 2008 SE 64-bit) has no effect either.
Anyone who can help me out with this problem ?
Kind regards, Marcel
If I look with fathom, the dot before the wsa1 container is blue.
If you click on that blue dot it takes about 2 minutes before the wsa configuration page shows but almost all options are grayed out.
The Tomcat 7 servlet engine is running and restarting this service does not have any effect.
The testpage for the servlet engine says WSA: 111 OK
Rebooting th entire database server (OpenEdge 10.2B SP5 32 bit on Windows 2008 SE 64-bit) has no effect either.
Anyone who can help me out with this problem ?
Kind regards, Marcel