SAP Knowledge Base Article - Preview

1942202 - Oracle Weblogic Application Server Crashes Immediately During Startup


  • When starting a Weblogic server, getting the error message below:

  • <Nov 18, 2013 9:01:35 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 18, 2013 9:01:35 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Nov 18, 2013 9:01:36 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /build/home/ahan/Oracle/Middleware/user_projects/domains/base_domain2/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    # A fatal error has been detected by the Java Runtime Environment:
    #  SIGSEGV (0xb) at pc=0xd28b33b0, pid=1951, tid=12
    # JRE version: 6.0_29-b11
    # Java VM: Java HotSpot(TM) Client VM (20.4-b02 mixed mode solaris-sparc )
    # Problematic frame:
    # C  []  Java_weblogic_socket_DevPollSocketMuxer_initDevPoll+0x260
    # An error report file with more information is saved as:
    # /build/home/ahan/Oracle/Middleware/user_projects/domains/base_domain2/hs_err_pid1951.log
    # If you would like to submit a bug report, please visit:
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    Abort - core dumped



  • OS: Oracle Solaris 10 SPARC
  • Application Server: Weblogic 10.3.6
  • Java: JDK 1.6.0_29


WEBLOGIC BY BEA all versions


oracle, weblogic, application, server, app server, BEA, wls, crash, core, dump,, SIGSEGV , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.