If you want to change this, there is a lot of BS on the internet, something like – change the startup parameters and add this…
XX:MaxPermSize=256m -Dweblogic.wsee.wstx.wsat.deployed=false -Dweblogic.client.socket.ConnectTimeout=30000 -Xms1536m -Xmx1536m
It does not work,
You need to go to your server, tuning and set the Login Timeout setting. Defalt is 5000 (ms), which is 5 seconds. This is 12.1.2.0. Make it bigger, like mine is 50 seconds now. I’m doing this as I’m having lots of issues with a AWS ELB.
####<Apr 9, 2015 10:57:48 AM EST> <Warning> <Socket> <jdewebprod03> <JDEPD3_8080> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1428541068826> <BEA-000449> <Closing the socket, as no data read from it on 172.31.169.170:45,489 during the configured idle timeout of 50 seconds.>
####<Apr 9, 2015 10:57:48 AM EST> <Warning> <Socket> <jdewebprod03> <JDEPD3_8080> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1428541068827> <BEA-000449> <Closing the socket, as no data read from it on 172.31.169.170:45,492 during the configured idle timeout of 50 seconds.>
####<Apr 9, 2015 10:57:48 AM EST> <Warning> <Socket> <jdewebprod03> <JDEPD3_8080> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1428541068828> <BEA-000449> <Closing the socket, as no data read from it on 172.31.169.170:45,488 during the configured idle timeout of 50 seconds.>
####<Apr 9, 2015 10:57:48 AM EST> <Warning> <Socket> <jdewebprod03> <JDEPD3_8080> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1428541068829> <BEA-000449> <Closing the socket, as no data read from it on 172.31.169.170:45,490 during the configured idle timeout of 50 seconds.>
####<Apr 9, 2015 10:58:08 AM EST> <Warning> <Socket> <jdewebprod03> <JDEPD3_8080> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1428541088821> <BEA-000449> <Closing the socket, as no data read from it on 172.31.137.115:24,853 during the configured idle timeout of 50 seconds.>
3 comments:
hi
this is a solution or a report? i mean with increasing this value the problem solved or not?thanks in advance
Shannon, you are a savior :). Your post helped us with a strange problem that we were seeing when uploading files to a database!
THANK YOU!!!
Solution, so you do not get that error anymore. increase the number
Post a Comment