javax.naming.NameNotFoundException after 14.5 upgrade Identity Manager on Weblogic
search cancel

javax.naming.NameNotFoundException after 14.5 upgrade Identity Manager on Weblogic

book

Article ID: 378016

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

After upgrade from 14.4 CP2 to 14.5 standalone Identity Manager system installed on Weblogic application you can see error during IM startup:

ERROR [ims.Main] javax.naming.NameNotFoundException: While trying to lookup 'iam.im.jms.factory.com/netegrity/idm/GeneralMonitorCF' didn't find subcontext 'factory'. Resolved 'iam.im.jms'; remaining name 'factory/com/netegrity/idm/GeneralMonitorCF'

Further investigation of startup in server log shows error during Weblogic startup of IM (before IM startup):

<Error> <Deployer> <XXX-YYYYYY> <Unable to set the activation state to true for the application "iam_im_imJMSModule".
weblogic.application.ModuleException: Error Activating

Caused by: weblogic.descriptor.BeanUpdateRejectedException: The proposed JNDI name <Name>@iam/im/jms/queue/queue/statusNotificationsQueue for destination iam_im imJMSModule!iam_im <Name>@iam_im Status Notifications
is already bound by another object of type weblogic.jms.common.DestinationImpl

Environment

14.4 Standalone IM installed on Weblogic application server

Cause

Duplicated JMS entry in configuration.

Resolution

Examine the configuration to find entries that are configured to use same jave class this time it were StatusNotificationQueues.

Backup the information and delete one of them.