while working with weblogic, Getting 'Internet Explorer cannot display the webpage' after some time.

[mika singh]

Hi,
when Some of the queries taking long time to execute, my web browser is displaying 'Internet Explorer cannot display the webpage' error message. What might be the reason?? Is weblogic killing the request?? Is it having any setting to avoid that??
server logs are displaying error message like:
<Error> <WebLogicServer> <aipsnp07> <wsaserver> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314260484297> <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "691" seconds working on the request "Http Request: /wsa/wvFlexiReportsAction.do", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
oracle.net.ns.Packet.receive(Unknown Source)
oracle.net.ns.DataPacket.receive(Unknown Source)
oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.net.ns.NetInputStream.read(Unknown Source)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1099)
oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:946)
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1060)
oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:830)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1124)
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1272)
............................
Please check the attachment for more information.

Thanks in advance.

[German Gonzalez-Morris]

It seems to stuck when accessing to database.

Take several thread dumps and analyze them.
Also try to identify the query is happening in that moment. It might be a problem with the query itself and/or database settings.

cheers,