1 Reply Latest reply: Oct 6, 2013 11:02 PM by Rosario RSS

    soa network issue

    972017

        Hi All,

       

           this issue from my production enveronment some time network connection going to down please any body help on this issue .

       

      <Oct 4, 2013 12:20:23 PM GMT> <Info> <EJB> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1228B61536E160994897> <6a64a370db9cb4a0:-5b4492d9:1417defbc9f:-8000-000000000003715b> <1380889223663> <BEA-010227> <EJB Exception occurred during invocation from home or business: oracle.sdpinternal.messaging.storage.MessagingStore_urkbp2_HomeImpl@7415bcc6 threw exception: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException

      Internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection

      Error Code: 0

      Call: SQLCall(SELECT DRIVER_NAME, MIME_TYPES, PROTOCOLS, CARRIERS, SENDER_ADDRESSES, COST, DELIVERY_TYPES, SPEED, STATUS_TYPES, CHECKSUM, SUPPORTS_CANCEL, ENCODINGS, SUPPORTS_REPLACE, SUPPORTS_TRACKING, SUPPORTS_STATUS_POLLING, DEFAULT_SENDER, CAPABILITY, LOCK_VERSION FROM DRIVER_INFO)

      Query: ReadAllQuery(oracle.sdpinternal.messaging.config.DriverInfo)>

      ####<Oct 4, 2013 12:20:44 PM GMT> <Warning> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '82' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-5b4492d9:1417defbc9f:-8000-000000000003715d> <1380889244302> <BEA-001129> <Received exception while creating connection for pool "AIAJMSDS-rac0": IO Error: The Network Adapter could not establish the connection.>

      ####<Oct 4, 2013 12:20:44 PM GMT> <Info> <JDBC> <EPGCRMITG1> <soa_server1> <[ACTIVE] ExecuteThread: '82' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6a64a370db9cb4a0:-5b4492d9:1417defbc9f:-8000-000000000003715d> <1380889244303> <BEA-001156> <Stack trace associated with message 001129 follows:

       

      java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

              at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:482)

              at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)

              at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)

              at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)

              at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)

              at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)

              at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:239)

              at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)

              at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2790)

              at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)

              at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

              at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

      Caused By: oracle.net.ns.NetException: The Network Adapter could not establish the connection

              at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:398)

              at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:438)

              at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:711)

              at oracle.net.ns.NSProtocol.connect(NSProtocol.java:257)

       

      Thank you,

      Ram

        • 1. Re: soa network issue
          Rosario

          Hello Ram,

           

          you need to involve your network team and DB team to get this resolved.

           

          Try checking whether all DB services are running properly(DB Instance, DB  TNS Listener) in the same Listen Address and Port number given in the weblogic configuration. If every thing is running, then try to use a stand alone java program to check if you are able to connect to db from the machine where weblogic machine is running.

           

          Regards

          Rosario