== Ensure Jade Module Never Replies with an HTML Page ==
One thing I've never managed to workout is how to override the default error HTML page the Jade Apache module returns if the Web Application is not running. Our consumers are ALWAYS expecting a SOAP response, I'd like to wrap the 502 Bad Gateway message in a SOAP envelope rather than relying on the consumers to have to handle a possible HTML page coming back.
== Thin Client read first failed (wrong length received 0) ==
While I have your ear... something else popped up recently on an older 6.2 system. The Web Application is constantly peppering the jommsg log with the following:
Code: Select all
JadApp: Client Tcp address = 10.100.0.3 port=26346, App Server Tcp address = 172.16.100.103 port=8227
JadApp: Thin Client read first failed (wrong length received 0): (10.100.0.3)
Not sure where to start with this one. This is an old VM server, it's a little sluggish and needs the occasional reboot, other than that it seems ok and the web service serves it's purpose.