Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'

Question

Hello,
I hope I am posting this in the right place, if not please forgiv and point me to the right place.
Yesterday we did a live upgrade on a system that is running WebLogic 9.2, OSM 6.3.1 and Oracle DB 10.2.0.2, those applications are on a seperate system slice, we did a complete upgrade from Solaris 10/9 (update 6) to the latest Solaris 8/11 (update 10), on SPARC. After the upgrade everything was working and applications are able to start, but weblogic server is spewing the following error message:
<Aug 1, 2012 12:03:58 PM CEST> <Error> <oms.core> <600022> <EJB Create exception thrown while creating object=EventDispatcherEJB.>
<01-Aug-2012 12:03:58,982 CEST PM> <ERROR> <poller.a> <Timer-4> <Failed to process events>
java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'. Resolved 'mslv.oms.oms1.internal.jms'
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:724)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:220)
at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:64)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.java:485)
at com.mslv.oms.poller.a.handleNotification(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1652)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
we went back and activated Solaris update 8, and we still got that problem. The requests that the clients that connect via OSM frontend application that communicates with WebLogic arent being processed.
The oracle db is working and listening to port 1521, I can connect to it and can connect with the user defined in the WebLogic connection pool.
This is the first time working on this system, the application and integration was done by someone else who are not available to help us out, I hope someone here on the forum will be able to help us out with this problem.
Regards,
Omar

Answer 1

Often ConnectionFactory errors are caused by an inability to connect with the database hosting the OSM schema and user.
Check the database and make sure that both it and its listener are accepting connections. If that is ok you can also check the oms_pool configuration in WebLogic. Make sure the JNDI connection is valid. In my environments I see that DHCP often screws things up. If I install OSM on a host that has a DHCP assigned address (I'm guilty of being lazy when working in VMs and not statically assigning IP addresses) I often break the JNDI when I reboot the VM and get a new IP.
In WebLogic Admin Console:
Domain > Services > JDBC >Connection Pool > URL
and make sure the JDBC connection string is correct.