Discussion:
Async operation timed out
(too old to reply)
J***@GBM.NET
2009-05-08 18:25:30 UTC
Permalink
Hi,

I'm having this message a lot in the SystemOut.log:

SRVE0133E: An error occurred while parsing parameters. java.net.SocketTimeoutException: Async operation timed out

I found this thread:

http://www.ibm.com/developerworks/forums/thread.jspa?threadID=221071

but the info center says that recommendation applies to v5.1 nodes only. For v6.1 nodes HTTP transport channels should be modified instead, but there is no ConnectionIOTimeOut custom property, anyone knows how to solve this issue for WAS 6.1?

Thanks
Sven Vermeulen
2009-05-08 18:57:15 UTC
Permalink
Post by J***@GBM.NET
SRVE0133E: An error occurred while parsing parameters.
java.net.SocketTimeoutException: Async operation timed out
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=221071
but the info center says that recommendation applies to v5.1 nodes only.
For v6.1 nodes HTTP transport channels should be modified instead, but
there is no ConnectionIOTimeOut custom property, anyone knows how to
solve this issue for WAS 6.1?
Might be a long shot, but check which applications are deployed on your
application server. I vaguely remember that, on standalone profiles, an
"ibmasyncrsp" or something like that is installed automatically.

I had cosmetic errors as long as this application was deployed on the
JVM. Uninstalling it resolved the errors and didn't cause any functional
change.

Wkr,
Sven Vermeulen

Loading...