WebCenter Sites Managed Server Taking Long Time to Start Up.
(Doc ID 1673507.1)
Last updated on NOVEMBER 18, 2024
Applies to:
Oracle WebCenter Sites - Version 11.1.1.8.0 and laterInformation in this document applies to any platform.
Symptoms
It takes a long time (many minutes) for the WebCenter Sites managed server to reach RUNNING state.
Thread dumps, taken while the server is starting, show one single thread reading from SystemLocaleString most of the time it takes for the server to start.
"[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=25 idx=0x4c tid=14430 prio=5 alive, in native, daemon
at jrockit/net/SocketNativeIO.readBytesPinned(Ljava/io/FileDescriptor;[BIII)I(Native Method)
at jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:32)
at java/net/SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(SocketInputStream.java)
at java/net/SocketInputStream.read(SocketInputStream.java:129)
at oracle/net/ns/Packet.receive(Packet.java:300)
at oracle/net/ns/DataPacket.receive(DataPacket.java:106)
at oracle/net/ns/NetInputStream.getNextPacket(NetInputStream.java:315)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:260)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:185)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:102)
at oracle/jdbc/driver/T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:124)
at oracle/jdbc/driver/T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:80)
at oracle/jdbc/driver/T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1137)
at oracle/jdbc/driver/T4CTTIfun.receive(T4CTTIfun.java:290)
at oracle/jdbc/driver/T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle/jdbc/driver/T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle/jdbc/driver/T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
at oracle/jdbc/driver/T4CPreparedStatement.fetch(T4CPreparedStatement.java:1119)
at oracle/jdbc/driver/OracleResultSetImpl.close_or_fetch_from_next(OracleResultSetImpl.java:375)
^-- Holding lock: oracle/jdbc/driver/T4CConnection@0x97c3f750[recursive]
at oracle/jdbc/driver/OracleResultSetImpl.next(OracleResultSetImpl.java:279)
^-- Holding lock: oracle/jdbc/driver/T4CConnection@0x97c3f750[recursive]
at oracle/jdbc/driver/ScrollableResultSet.cacheAllRows(ScrollableResultSet.java:2283)
at oracle/jdbc/driver/ScrollableResultSet.getLastRow(ScrollableResultSet.java:2337)
at oracle/jdbc/driver/ScrollableResultSet.last(ScrollableResultSet.java:477)
^-- Holding lock: oracle/jdbc/driver/T4CConnection@0x97c3f750[biased lock]
at weblogic/jdbc/wrapper/ResultSet_oracle_jdbc_driver_ScrollableResultSet.last()Z(Unknown Source)
at COM/FutureTense/Servlet/JDBCResult.GetRowCount(JDBCResult.java:77)
at COM/FutureTense/Servlet/SContentServer._loadSystemLocaleString(SContentServer.java:98)
at COM/FutureTense/Servlet/SContentServer.init(SContentServer.java:73)
at javax/servlet/GenericServlet.init(GenericServlet.java:241)
...
When the managed server is started, it first reads the entire SystemLocaleString table into cache. This is a relatively large table, but under normal circumstances it should not take more than a few seconds to read. The server will not get into RUNNING state until the thread is done reading the table.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |