11 Replies Latest reply: Nov 15, 2012 9:03 PM by Dhananjay Neeraj2 RSS

    Unable to open oim web console (404 error)

    961125
      Hi,

      I have started oim server but after getting it in running state am getting the following exception.

      <Nov 15, 2012 12:45:26 AM IST> <Warning> <JDBC> <BEA-001129> <Received exception
      while creating connection for pool "oimOperationsDB": IO Error: The Network Ada
      pter could not establish the connection>

      FYI- in weblogic admin console i see oim serverin running state, but after goin to deployments in oim_server1 i find that OIM metadata and OIM are in failed state, kindly suggest what to do.

      Regards,
      KK
        • 1. Re: Unable to open oim web console (404 error)
          Kevin Pinsky
          Check your Data Resources section of weblogic. Click the resource identified in the error and then click the monitoring/testing tab and make sure it's available. You can also check the parameters on the connection pool tab for the database connection.

          -Kevin
          • 2. Re: Unable to open oim web console (404 error)
            Dhananjay Neeraj2
            I have faced similar issues... In my case the passwords of DEV_OIM etc were expired...

            So, I solved it by following method:-

            (1) Stopped ALL 3 servers... oim_server1 , soa_server1 and AdminServer

            (2) By using SYS AS SYSDBA, reset the same password again... ALTER DEV_OIM IDENTIFIED BY Abcd1234; (Previous password too was Abcd1234)

            Similarly for others like DEV_MDS, DEV_SOAINFRA etc

            (3) Start the server in the following order: AdminServer --> soa_server1 --> oim_server1

            Also, The Network Adapter could not establish the connection typically comes when (1) Database is not available (2) Or Database host not pingable due to some Firewall issue etc (3) Database server is not running... In that case restart the database too...
            • 3. Re: Unable to open oim web console (404 error)
              Nishith Nayan
              can you verify MetaLink ID: 1342814.1

              find below steps and see if this helps

              1. export oim-config.xml using weblogicExportMetadata utility
              2. update the oim-config.xml in your MDS with correct values for url, @dburl and username, @dbuser and maxConnections to 20:
              3. import oim-config.xml back to MDS using weblogicImportMetadata utility


              MDS path of oim-config.xml=/db/oim-config.xml

              update weblogic.properties before running export/import utility
              metadata_files=/db/oim-config.xml
              metadata_to_loc=location_where_you_want to export (ex /export/tmp)
              metadata_from_loc=same given for export (ex: /export/tmp)
              • 4. Re: Unable to open oim web console (404 error)
                Gyanprakash Pandey
                Make sure your database is up and running. Verify by connecting them using sqldeveloper using same credentials specified in your data sources.

                regards,
                GP
                • 5. Re: Unable to open oim web console (404 error)
                  961125
                  Database is up and am able to connect to database from sql developer.

                  Kindly suggest.

                  FYI

                  Caused By: javax.naming.NameNotFoundException: While trying to lookup 'DocumentM
                  anager#oracle.wsm.policymanager.bean.ejb.IRemoteDocumentManager' didn't find sub
                  context 'DocumentManager#oracle'. Resolved ''; remaining name 'DocumentManager#o
                  racle/wsm/policymanager/bean/ejb/IRemoteDocumentManager'
                  at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
                  NamingNode.java:1139)
                  at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
                  a:247)
                  at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
                  ava:182)
                  at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:20
                  6)
                  at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
                  ava:254)
                  at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
                  at javax.naming.InitialContext.lookup(InitialContext.java:392)
                  at oracle.wsm.policymanager.BeanFactory$2.run(BeanFactory.java:660)
                  at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
                  at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccAction
                  Executor.java:47)
                  at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivil
                  egedExceptionAction.run(CascadeActionExecutor.java:79)
                  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
                  dSubject.java:363)
                  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
                  146)
                  at weblogic.security.Security.runAs(Security.java:61)
                  at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecu
                  tor.java:48)
                  at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(Casca
                  deActionExecutor.java:52)
                  at oracle.wsm.policymanager.BeanFactory.getJndiObj(BeanFactory.java:652)

                  at oracle.wsm.policymanager.BeanFactory.lookupJndiObj(BeanFactory.java:9
                  10)
                  at oracle.wsm.policymanager.BeanFactory.getDocumentManagerBeanEJB(BeanFa
                  ctory.java:567)
                  at oracle.wsm.policymanager.BeanFactory.getBeanEJB(BeanFactory.java:461)

                  at oracle.wsm.policymanager.BeanFactory.getBean(BeanFactory.java:381)
                  at oracle.wsm.policymanager.BeanFactory.getBean(BeanFactory.java:327)
                  at oracle.wsm.policyaccess.ConfigurationFramework.getBean(ConfigurationF
                  ramework.java:1635)
                  at oracle.wsm.policyaccess.ConfigurationFramework.access$500(Configurati
                  onFramework.java:133)
                  at oracle.wsm.policyaccess.ConfigurationFramework$ContextualAccessor.con
                  figure(ConfigurationFramework.java:452)
                  at oracle.wsm.policyaccess.ConfigurationFramework$ContextualAccessor.acc
                  ess$1400(ConfigurationFramework.java:299)
                  at oracle.wsm.policyaccess.ConfigurationFramework.initializeAccessors(Co
                  nfigurationFramework.java:1915)
                  at oracle.wsm.policyaccess.ConfigurationFramework.access$200(Configurati
                  onFramework.java:133)
                  at oracle.wsm.policyaccess.ConfigurationFramework$ContextualAccessor.isV
                  alid(ConfigurationFramework.java:607)
                  at oracle.wsm.policyaccess.ConfigurationFramework$ContextualAccessor.acc
                  ess$800(ConfigurationFramework.java:299)
                  at oracle.wsm.policyaccess.ConfigurationFramework$VirtualAccessor.valida
                  teAccessor(ConfigurationFramework.java:1075)
                  at oracle.wsm.policyaccess.ConfigurationFramework$VirtualAccessor.retrie
                  veDocuments(ConfigurationFramework.java:1044)
                  at oracle.wsm.policymanager.bean.util.PolicySetBuilder.generateReference
                  s(PolicySetBuilder.java:421)
                  at oracle.wsm.policymanager.bean.util.PolicySetBuilder.<init>(PolicySetB
                  uilder.java:248)
                  at oracle.wsm.policyaccess.PolicyAccessPoint.registerListener(PolicyAcce
                  ssPoint.java:366)
                  at oracle.wsm.policyaccess.impl.PolicyAccessorImpl$1.run(PolicyAccessorI
                  mpl.java:238)
                  at oracle.wsm.policyaccess.impl.PolicyAccessorImpl$1.run(PolicyAccessorI
                  mpl.java:234)
                  at oracle.wsm.policyaccess.impl.PolicyAccessorImpl.getPolicySetMap(Polic
                  yAccessorImpl.java:233)
                  at oracle.wsm.policyaccess.impl.PolicyAccessorImpl.getPolicySet(PolicyAc
                  cessorImpl.java:193)
                  at oracle.integration.platform.common.mgmt.PolicyCacheImpl$CacheNode.ref
                  reshIfStale(PolicyCacheImpl.java:166)
                  at oracle.integration.platform.common.mgmt.PolicyCacheImpl.getPolicySet(
                  PolicyCacheImpl.java:267)
                  at oracle.j2ee.ws.server.mgmt.runtime.SuperServerInterceptorPipeline.for
                  cePolicyLoad(SuperServerInterceptorPipeline.java:194)
                  at oracle.j2ee.ws.server.mgmt.runtime.SuperServerInterceptorPipeline.<in
                  it>(SuperServerInterceptorPipeline.java:70)
                  at oracle.j2ee.ws.server.provider.GenericProviderInterceptorPipeline.cre
                  ateServerPipeline(GenericProviderInterceptorPipeline.java:133)
                  at oracle.j2ee.ws.server.provider.management.AbstractProviderInterceptor
                  Pipeline.<init>(AbstractProviderInterceptorPipeline.java:121)
                  at oracle.j2ee.ws.server.provider.GenericProviderInterceptorPipeline.<in
                  it>(GenericProviderInterceptorPipeline.java:103)
                  at oracle.j2ee.ws.server.provider.GenericProviderPlatform.createProvider
                  InterceptorPipeline(GenericProviderPlatform.java:194)
                  at oracle.j2ee.ws.server.provider.management.ProviderInterceptorPipeline
                  Manager.createProviderInterceptorPipeline(ProviderInterceptorPipelineManager.jav
                  a:101)
                  at oracle.j2ee.ws.server.provider.management.ProviderInterceptorPipeline
                  Manager.createProviderInterceptorPipeline(ProviderInterceptorPipelineManager.jav
                  a:80)
                  at oracle.j2ee.ws.server.provider.ProviderProcessor.configureProviderMan
                  agement(ProviderProcessor.java:353)
                  at oracle.j2ee.ws.server.provider.ProviderProcessor.init(ProviderProcess
                  or.java:198)
                  at oracle.j2ee.ws.server.provider.ProviderServlet.initializeProcessor(Pr
                  oviderServlet.java:543)
                  at oracle.j2ee.ws.server.provider.ProviderServlet.init(ProviderServlet.j
                  ava:268)
                  at oracle.j2ee.ws.server.provider.ProviderServlet.init(ProviderServlet.j
                  ava:200)
                  at javax.servlet.GenericServlet.init(GenericServlet.java:241)
                  at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
                  ubSecurityHelper.java:283)
                  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
                  dSubject.java:321)
                  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
                  120)
                  at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
                  tyHelper.java:64)
                  at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
                  ifecycleHelper.java:58)
                  at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
                  per.java:48)
                  at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
                  mpl.java:539)
                  at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
                  ervletContext.java:1985)
                  at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(
                  WebAppServletContext.java:1959)
                  at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAp
                  pServletContext.java:1878)
                  at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletCon
                  text.java:3153)
                  at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.jav
                  a:1508)
                  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
                  at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
                  teDriver.java:425)
                  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
                  river.java:52)
                  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
                  eDriver.java:119)
                  at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedMod
                  uleDriver.java:200)
                  at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
                  ListenerInvoker.java:247)
                  at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
                  teDriver.java:425)
                  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
                  river.java:52)
                  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
                  eDriver.java:119)
                  at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
                  ulesFlow.java:27)
                  at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
                  va:636)
                  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
                  river.java:52)
                  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
                  java:205)
                  at weblogic.application.internal.EarDeployment.activate(EarDeployment.ja
                  va:58)
                  at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
                  entStateChecker.java:161)
                  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
                  pContainerInvoker.java:79)
                  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicD
                  eployment.java:184)
                  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromSer
                  verLifecycle(BasicDeployment.java:361)
                  at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(De
                  ploymentAdapter.java:51)
                  at weblogic.management.deploy.internal.DeploymentAdapter.activate(Deploy
                  mentAdapter.java:200)
                  at weblogic.management.deploy.internal.AppTransition$2.transitionApp(App
                  Transition.java:30)
                  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionA
                  pps(ConfiguredDeployments.java:240)
                  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(Co
                  nfiguredDeployments.java:169)
                  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(Conf
                  iguredDeployments.java:123)
                  at weblogic.management.deploy.internal.DeploymentServerService.resume(De
                  ploymentServerService.java:180)
                  at weblogic.management.deploy.internal.DeploymentServerService.start(Dep
                  loymentServerService.java:96)
                  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
                  at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
                  >
                  <Nov 15, 2012 11:35:39 PM IST> <Notice> <Log Management> <BEA-170027> <The Serve
                  r has established connection with the Domain level Diagnostic Service successful
                  ly.>
                  <Nov 15, 2012 11:35:41 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
                  ate changed to ADMIN>
                  <Nov 15, 2012 11:35:41 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
                  ate changed to RESUMING>
                  <Nov 15, 2012 11:35:42 PM IST> <Warning> <Server> <BEA-002611> <Hostname "Karan-
                  PC", maps to multiple IP addresses: 192.168.1.2, fe80:0:0:0:a1b3:668d:5c69:ca1f%
                  11, fe80:0:0:0:835:d8ba:87c4:edcf%13, 2001:0:9d38:953c:835:d8ba:87c4:edcf>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  6]" is now listening on fe80:0:0:0:d98d:d791:6273:822c:14000 for protocols iiop,
                  t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  7]" is now listening on fe80:0:0:0:a1b3:668d:5c69:ca1f:14000 for protocols iiop,
                  t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  2]" is now listening on fe80:0:0:0:0:5efe:c0a8:102:14000 for protocols iiop, t3,
                  ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  4]" is now listening on fe80:0:0:0:c95e:e5e:4c46:dc45:14000 for protocols iiop,
                  t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  8]" is now listening on 127.0.0.1:14000 for protocols iiop, t3, ldap, snmp, http
                  .>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default"
                  is now listening on 2001:0:9d38:953c:835:d8ba:87c4:edcf:14000 for protocols iio
                  p, t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  5]" is now listening on fe80:0:0:0:835:d8ba:87c4:edcf:14000 for protocols iiop,
                  t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  9]" is now listening on 0:0:0:0:0:0:0:1:14000 for protocols iiop, t3, ldap, snmp
                  , http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  1]" is now listening on 192.168.1.2:14000 for protocols iiop, t3, ldap, snmp, ht
                  tp.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[
                  3]" is now listening on fe80:0:0:0:d4a4:cc13:2d57:a2e1:14000 for protocols iiop,
                  t3, ldap, snmp, http.>
                  <Nov 15, 2012 11:35:42 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started W
                  ebLogic Managed Server "oim_server1" for domain "idmdomain" running in Productio
                  n Mode>
                  <Nov 15, 2012 11:36:22 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
                  ate changed to RUNNING>
                  <Nov 15, 2012 11:36:22 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server st
                  arted in RUNNING mode>
                  <Nov 15, 2012 11:36:45 PM IST> <Warning> <JDBC> <BEA-001129> <Received exception
                  while creating connection for pool "oimOperationsDB": IO Error: The Network Ada
                  pter could not establish the connection>
                  <Nov 15, 2012 11:38:11 PM IST> <Warning> <JDBC> <BEA-001129> <Received exception
                  while creating connection for pool "oimOperationsDB": IO Error: The Network Ada
                  pter could not establish the connection>
                  <Nov 15, 2012 11:39:36 PM IST> <Warning> <JDBC> <BEA-001129> <Received exception
                  while creating connection for pool "oimOperationsDB": IO Error: The Network Ada
                  pter could not establish the connection>
                  <Nov 15, 2012 11:41:01 PM IST> <Warning> <JDBC> <BEA-001129> <Received exception
                  while creating connection for pool "oimOperationsDB": IO Error: The Network Ada
                  pter could not establish the connection>



                  Kindly suggest..

                  Edited by: 958122 on Nov 16, 2012 12:07 AM
                  • 6. Re: Unable to open oim web console (404 error)
                    BikashBagaria
                    Check the status of the wsm-pm application from weblogic console. This application should be deployed and in running state on the soa server in the domain. You can also validate by hitting the url: http://<weblogicSOAhost:SOAPort>/wsm-pm/

                    If the policy manager is not active, you should start it and then start OIM.

                    -Bikash
                    • 7. Re: Unable to open oim web console (404 error)
                      961125
                      wsm-pm, OIM metadata and oim are in failed state...
                      • 8. Re: Unable to open oim web console (404 error)
                        BikashBagaria
                        First make sure that your SOA server is up and all the applications deployed on SOA server are running fine. Once you have that then you can start your OIM.

                        -Bikash
                        • 9. Re: Unable to open oim web console (404 error)
                          961125
                          Bikash, from the past times am not using soa server at all, am just working on oim and it was working fine but now this error came.

                          kindly suggest...

                          regards,
                          KK
                          • 10. Re: Unable to open oim web console (404 error)
                            BikashBagaria
                            Sorry my bad, Policy manager is deployed on OIM Server as well. So you will have to diagnose why it is not starting OIM server. Monitor the logs when you start OIM server to check for each application failures and correct those individually.

                            -Bikash
                            • 11. Re: Unable to open oim web console (404 error)
                              Dhananjay Neeraj2
                              Try making Connection pool 0 instead of default 10000 via Weblogic Admin console --> Data Source --> Connection Pool.... (all 10 connection pools)...