Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by Djay-OC, 1 year ago
via hivmr.com by Unknown author, 1 year ago
java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 667664
via Oracle Community by 840124, 1 year ago
java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 667664
via Oracle Community by 846061, 1 year ago
java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 1335312
via Oracle Community by 656211, 1 year ago
via Stack Overflow by AlwaysALearner
, 1 year ago
java.lang.OutOfMemoryError: GC overhead limit exceeded
>
####<Mar 24, 2014 5:13:22 AM EDT> <Warning> <Socket> <test-obiee-app> <bi_server1> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000056bad> <1395652402424> <BEA-000449> <Closing socket as no data read from it on 10.15.5.54:59,738 during the configured idle timeout of 5 secs>
####<Mar 24, 2014 5:13:46 AM EDT> <Critical> <Health> <test-obiee-app> <bi_server1> <weblogic.GCMonitor> <<anonymous>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000000017> <1395652426181> <BEA-310003> <Free memory in the server is 2,776,288 bytes. There is danger of OutOfMemoryError>
####<Mar 24, 2014 5:14:09 AM EDT> <Info> <Common> <test-obiee-app> <bi_server1> <RTD_Worker_841> <<anonymous>> <> <0000KJP6WK^E^Mh5xBH7iW1JAJrl000002> <1395652449710> <BEA-000628> <Created "1" resources for pool "rtd_datasource", out of which "1" are available and "0" are unavailable.>
####<Mar 24, 2014 5:15:10 AM EDT> <Error> <HTTP> <test-obiee-app> <bi_server1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000056bbe> <1395652510251> <BEA-101017> <[ServletContext@197025158[app:bipublisher module:xmlpserver path:/xmlpserver spec-version:2.5 version:11.1.1]] Root cause of ServletException.
java.lang.OutOfMemoryError: GC overhead limit exceeded
>
####<Mar 24, 2014 5:15:10 AM EDT> <Notice> <Diagnostics> <test-obiee-app> <bi_server1> <[STANDBY] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000056bbf> <1395652510254> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'bi_server1' has triggered
at Mar 24, 2014 5:15:10 AM EDT. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = Mar 24, 2014 5:15:10 AM EDT SERVER = bi_server1 MESSAGE = [ServletContext@197025158[app:bipublisher module:xmlpserver path:/xmlpserver spec-version:2.5 version:11.1.1]] Root cause of ServletException.
java.lang.OutOfMemoryError: GC overhead limit exceeded
SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = test-obiee-app TXID =  CONTEXTID = 0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000056bbe TIMESTAMP = 1395652510251
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
>
####<Mar 24, 2014 5:15:21 AM EDT> <Critical> <Health> <test-obiee-app> <bi_server1> <weblogic.GCMonitor> <<anonymous>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000000017> <1395652521980> <BEA-310003> <Free memory in the server is 2,808,168 bytes. There is danger of OutOfMemoryError>
####<Mar 24, 2014 5:15:21 AM EDT> <Error> <HTTP> <test-obiee-app> <bi_server1> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0c4290d9bb4c177a:18bf6a32:144d919f8aa:-8000-0000000000056bc3> <1395652521982> <BEA-101017> <[ServletContext@253456294[app:analytics module:analytics path:/analytics spec-version:2.5 version:11.1.1]] Root cause of ServletException.
java.net.SocketTimeoutException: Read timed out	at java.net.SocketInputStream.socketRead0(Native Method)	at java.net.SocketInputStream.read(SocketInputStream.java:129)	at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:177)	at java.io.InputStream.skip(InputStream.java:208)	at weblogic.servlet.internal.PostInputStream.skipUnreadBody(PostInputStream.java:207)