Forum Stats

  • 3,838,631 Users
  • 2,262,385 Discussions
  • 7,900,715 Comments

Discussions

Weblogic unable to connect to SOA-Infra application

User_B445Z
User_B445Z Member Posts: 1 Green Ribbon

Hi,

I have installed Oracle DB 19c & SOA-CS version 12.2.1.3 locally on an AWS instance.

After the launch of weblogic, at the admin console of weblogic & EM console, the SOA-Infra application is not started. Multiple efforts to start the SOA-Infra application manually did not yield any success.

Following errors are noticed at the diagnostic logs of weblogic (soa_server1-diagnostic.log):

=================================

at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:643) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:594) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:587) at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.fetchConnection(JNDIConnectionManagerImpl.java:306) ... 58 more

]] [2021-05-03T21:05:35.969+08:00] [soa_server1] [ERROR] [WSM-02313] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '48' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 31a98bf6-6236-4577-8bfd-8717869d9cb0-000001fc,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] The documents used by a policy subject cannot be recorded due to underlying error "The object identified by: '317' could not be found. Either it was not exported or it has been collected by the distributed garbage collector."[[ java.rmi.NoSuchObjectException: The object identified by: '317' could not be found. Either it was not exported or it has been collected by the distributed garbage collector. at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:249) at weblogic.rmi.internal.CollocatedRemoteRef.getOutboundRequest(CollocatedRemoteRef.java:75)

​   at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:301)        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)        at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)        at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)        at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)        at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)        at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)        at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)

===================================

We are unable to establish a connection with the datasource due to the error 'Unable to connect to host' , though we have checked that the instance is connected & reachable.

Any help in fixing this issue is appreciated.


Thanks,

Kunal

Tagged:

Answers