Skip to Main Content

Security Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

HTTP/1.1: 10.4.5 404 Not Found Error while accessing the odsm url

974057Jun 25 2013

Hi experts,

I 've installed OID 11.1.1.6 on weblogic server 10.6.. on Oracle linux 6.0

The Installation went fine And I am able to lauch the odsm default url http:\\localhost:7005/odsm  and  even chnaged the cn=orcladmin User password.

Also created few user and Groups using odsm,

However when i tried to access the odsm url after restarting the Admin & managed server . I am unable to access the  odsm url. for that i tired to deploy the odsm.ear on Admin server but it failed  getting the following error.

in the Adminserver.log file

2013 8:33:59 AM IST> <Error> <Console> <idm.oracle.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1371956639366> <BEA-240003> <Console encountered the following error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].

        at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)

        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)

        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)

        at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)

        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)

        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)

        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)

        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)

        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperati

     ...............................................

<Warning> <Deployer> <idm.oracle.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1371956639265> <BEA-149004> <Failures were detected while initiating deploy task for application 'odsm [Version=11.1.1.2.0]'.>

####<Jun 23, 2013 8:33:59 AM IST> <Warning> <Deployer> <idm.oracle.com> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1371956639268> <BEA-149078> <Stack trace for message 149004

And in wls_ods1.log file got the following error

<BEA-149265> <Failure occurred in the execution of deployment request with ID '1371955199392' for task '0'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].'

weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].

        at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)

        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)

        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)

        ...................................................................

    Than i tired to deploy the odsm.ear on managed server i.e wls_ods1 and later on both but got the same error.

    

   Also  There is no issue with the oidsrv or oidladpd proccess as with the start/stop of oid*  related proccesses using opmnctl

   Please see the following.

e@idm stage]$ oidctl connect=OIDDB status -diag

oidctl : INSTANCE_NAME   is not set, defaulting to inst1

oidctl : COMPONENT_NAME  is not set, defaulting to oid1

NLS_LANG not set in environment

Setting NLS_LANG to AMERICAN_AMERICA.AL32UTF8

  +--------------------------------------------------------------------------+

  | Process      |  PID   |   InstName    |  CompName   |Inst#| Port | Sport |

  +--------------------------------------------------------------------------+

  | oidmon       |  25968 |      asinst_1 |        oid3 |    0|      |       |

  +--------------------------------------------------------------------------+

  | oidldapd disp|  26010 |      asinst_1 |        oid3 |    1| 3060 |  3131 |

  | oidldapd serv|  26021 |      asinst_1 |        oid3 |    1| 3060 |  3131 |

  | Config   DN  | cn=oid3,cn=osdldapd,cn=subconfigsubentry                  |

  +--------------------------------------------------------------------------+

  +--------------------------------------------------------------------------+

  |Printing LDAP Operation in progress status ...                          |

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 9 DBSID: 263 DBPID: 26075 ==> IDLE

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 11 DBSID: 527 DBPID: 26078 ==> IDLE

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 8 DBSID: 8 DBPID: 26080 ==> IDLE

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 13 DBSID: 133 DBPID: 26108 ==> IDLE

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 10 DBSID: 526 DBPID: 26056 ==> IDLE

  +--------------------------------------------------------------------------+

    OIDLDAPD_PID: 26021 WorkerID: 12 DBSID: 650 DBPID: 26058 ==> IDLE

  +--------------------------------------------------------------------------+

          Cache Max Size                     : 209716224

          Max Entries configured             : 100000

          Max Entries cached                 : 0

          Num Entries in Cache               : 0

          Num Entries in GC                  : 0

          Page size                          : 102392

          Entry cache Hit count              : 0

          Entry cache Mis count              : 0

          Hash Area bytes used               : 13031472

          Hash Area blocks used              : 138

          ResultSet cache bytes used         : 0

          Resultset cache blocks used        : 0

          Entry cache bytes used             : 0

Cache memory used           : 13031472

[oracle@idm stage]$ opmnctl status -l

Processes in Instance: asinst_1

---------------------------------+--------------------+---------+----------+------------+----------+-----------+------

ias-component             | process-type|pid | status   |
uid |  memused |uptime | ports

---------------------------------+--------------------+---------+----------+------------+----------+-----------+------

ohs1                      | OHS         |   25970 | Alive|

1803561142 |  2127440 |  38:11:26 | https:9999,https:4443,http:7777

oid3                      | oidldapd    |   26021 | Alive|

1803561144 |  1425784 |  38:11:26 | N/A

oid3                      | oidldapd    |   26010 | Alive|

1803561143 |   435572 |  38:11:26 | N/A

oid3                      | oidmon      |   25968 | Alive|

1803561141 |   888088 |  38:11:26 | LDAPS:3131,LDAP:3060

EMAGENT                   | EMAGENT     |   25967 | Alive|

1803561140 |   106100 |  38:11:26 | N/A

$ netstat -an |grep 3060

tcp 00 :::3060              :::*

LISTEN

[oracle@idm stage]$ ps -ef |grep 3060

oracle7368  2130  0 05:53 pts/000:00:00 grep 3060
oracle   260211  9 Jun24 ? 03:33:54 oidldapd

control=26010 connect=oiddb debug=0 configset=0 instance=1 key=26748

host=idm.oracle.com logchange=TRUE port=3060 sport=3131

[oracle@idm stage]$ tnsping OIDDB

TNS Ping Utility for Linux: Version 11.1.0.7.0 - Production on 26-JUN-2013

05:53:20

Copyright (c) 1997, 2008, Oracle.  All rights reserved.

Used parameter files:

/idm/Middleware/Oracle_IDM2/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=idm.oracle.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=idmoid.oracle.com)))

OK (0 msec)

  Also I am able to access oracle HTTP server web page i.e

http://idm.oracle.com:7777/

Could anyone suggest as why after restarting the server am not able to access the odsm url and getting error in deploying the odsm.ear file.

Also after struggling with this error for 3 days i tried to Reinstall the oid after completely uninstalling it. But as soon as i restarted the  server  The odsm url become inaccessible

and getting the same Old error.

   Also one Important things that i observed that before restarting the Admin & managed server when the odsm url was accessible when i do grep the port 3060 i.e

root@idm config]# netstat -an |grep 3060

tcp        0      0 :::3060                     :::*

LISTEN

tcp        0      0 ::ffff:192.168.122.13:3060  ::ffff:192.168.122.13:24645

ESTABLISHED

tcp        0      0 ::ffff:192.168.122.13:24645 ::ffff:192.168.122.13:3060

ESTABLISHED

tcp        0      0 ::ffff:192.168.122.13:3060  ::ffff:192.168.122.13:58065

ESTABLISHED

tcp        0      0 ::ffff:192.168.122.13:58065 ::ffff:192.168.122.13:3060

ESTABLISHED

  After the restart of server i got this  output of 3060 port

$ netstat -an |grep 3060

tcp    0 :::3060                 :::*

LISTEN

I could not understand why this truncated output of 3060 port even though  all opmn manged proccess working fine as it's obvious from the out put from

$ oidctl connect=OIDDB status -diag And $ opmnctl status -l commands output which i 've posted above.

and am able start/stop oid related proccess from opmnct command



Please Help.  as am really struggling to work around the issue.

Thanks & Regards

Priya

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 23 2013
Added on Jun 25 2013
0 comments
1,007 views