WebSphere errors during fixpack install

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
stuartjvnorton
Participant
Posts: 527
Joined: Thu Apr 19, 2007 1:25 am
Location: Melbourne

WebSphere errors during fixpack install

Post by stuartjvnorton »

Hi all,

I've got 8.7 on a VM running Windows Server 2008 R2 64-bit.
Everything appears to be working fine, but I want to install fixpack 1 to get the BG workflow and latest IA fixes.

I have put the latest installer (328) on.
When I run the installer (as Administrator), it passes all of the pre-req's and copies/unpacks everything fine.
However, whenever it tries to deploy any of the applications into WebSphere, it gives the following error:
java.lang.Exception: Exit Code: 11, Info: *** Exception::ASB_admin_client:com.ascential.asb.admin.service.tools::Code(11), Message=An error occurred trying to instantiate an object of the entry point client implementation "com.ascential.asb.admin.service.ejb.EJBServiceAdmin"
ServiceAdminCommand:Exit(11), Error: com.ascential.asb.util.invocation.EntryPointInstantiationException: An error occurred trying to instantiate an object of the entry point client implementation "com.ascential.asb.admin.service.ejb.EJBServiceAdmin"
at com.ascential.asb.util.invocation.EntryPointFactory.createImplementation(EntryPointFactory.java:269)
at com.ascential.asb.admin.service.ServiceAdminFactory.getImplementation(ServiceAdminFactory.java:278)
at com.ascential.asb.admin.service.tools.ServiceCommandCommon.getServiceAdmin(ServiceCommandCommon.java:133)
at com.ascential.asb.admin.service.tools.ServiceAdminCommand.processDeploy(ServiceAdminCommand.java:181)
at com.ascential.asb.admin.service.tools.ServiceAdminCommand.handleRequest(ServiceAdminCommand.java:478)
at com.ascential.asb.admin.service.tools.ServiceAdminCommand.main(ServiceAdminCommand.java:562)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
at com.ascential.asb.util.invocation.EntryPointFactory.createImplementation(EntryPointFactory.java:257)
... 5 more
Caused by: com.ascential.asb.util.invocation.EntryPointInstantiationException: An error occurred trying to instantiate an object of the entry point client implementation "com.ascential.asb.admin.service.ejb.EJBServiceAdmin"
at com.ascential.asb.util.invocation.ejb.EJBServiceCreator.<init>(EJBServiceCreator.java:125)
at com.ascential.asb.admin.service.ejb.EJBServiceAdmin.<init>(EJBServiceAdmin.java:39)
... 10 more
Caused by: com.ibm.ws.naming.util.InvalidObjectException: Some object reference in the name "ascential/asb/ejb/impl/ServiceAdmin" relative to the context "IS87Node01Cell/nodes/IS87Node01/servers/server1" is invalid. Some possible causes include a context binding in the name which refers to a destroyed context, or an object binding which contains an invalid EJBHome reference. [Root exception is org.omg.CORBA.INV_OBJREF:
>> SERVER (id=4773e3aa, host=IS87) TRACE START:
>> org.omg.CORBA.INV_OBJREF: Could not resolve IOR string. vmcid: 0x0 minor code: 0 completed: No
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:2001)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolve_binding(WsnOptimizedNamingImpl.java:1681)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:583)
>> at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2163)
>> at com.ibm.WsnOptimizedNaming._NamingContextImplBase._invoke(_NamingContextImplBase.java:286)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
>> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
>> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
>> SERVER (id=4773e3aa, host=IS87) TRACE END.
vmcid: 0x0 minor code: 0 completed: No]
at com.ibm.ws.naming.jndicos.CNContextImpl.mapINV_OBJREF(CNContextImpl.java:4396)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1808)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1749)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1500)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:637)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.ascential.asb.util.invocation.ejb.EJBServiceCreator.<init>(EJBServiceCreator.java:120)
... 11 more
Caused by: org.omg.CORBA.INV_OBJREF:
>> SERVER (id=4773e3aa, host=IS87) TRACE START:
>> org.omg.CORBA.INV_OBJREF: Could not resolve IOR string. vmcid: 0x0 minor code: 0 completed: No
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolveUnresolvedBinding(WsnOptimizedNamingImpl.java:2001)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.resolve_binding(WsnOptimizedNamingImpl.java:1681)
>> at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:583)
>> at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:2163)
>> at com.ibm.WsnOptimizedNaming._NamingContextImplBase._invoke(_NamingContextImplBase.java:286)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
>> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
>> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
>> SERVER (id=4773e3aa, host=IS87) TRACE END.
vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
at com.ibm.rmi.iiop.ReplyMessage._getSystemException(ReplyMessage.java:250)
at com.ibm.rmi.iiop.ReplyMessage.getSystemException(ReplyMessage.java:198)
at com.ibm.rmi.iiop.ClientResponseImpl.getSystemException(ClientResponseImpl.java:230)
at com.ibm.rmi.corba.ClientDelegate.intercept(ClientDelegate.java:999)
at com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:453)
at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:1193)
at com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:795)
at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:1223)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:484)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:492)
at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2797)
at com.ibm.ws.naming.jndicos.CNContextImpl$2.run(CNContextImpl.java:2793)
at com.ibm.ws.naming.util.CommonHelpers.retry(CommonHelpers.java:762)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:2791)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1790)
... 18 more
It looks like the class in question isn't where it's expected to be. 8.7 managed to install and work fine in the first place, and I haven't touched WebSphere itself.

Retrying the failed action makes no difference, and it does this for every application it tries to deploy.
Not surprisingly, several of the components no longer work after the failed installation.

Any ideas? Google has practically nothing about this, and I'm not even sure where to look.

TIA.
Top
Gazelle
Premium Member
Premium Member
Posts: 108
Joined: Mon Nov 24, 2003 11:36 pm
Location: Australia (Melbourne)

Post by Gazelle »

How did you resolve this?
We're getting a similar problem applying Fixpack 3 to v8.5.
Top
Gazelle
Premium Member
Premium Member
Posts: 108
Joined: Mon Nov 24, 2003 11:36 pm
Location: Australia (Melbourne)

Post by Gazelle »

If anyone is interested, we got past the error by:
1. Restoring xmeta and the filesystems to the state prior to the upgrade.
Apparently one of the failed upgrades was tagged as "successful", which caused the upgrade utility some grief.

We then got another error, "Caused by: org.xml.sax.SAXParseException: cvc-id.2: There are multiple occurrences of ID value 'UINSTALL_create.iadb.directory_1'.", which was resolved by the following:

2. Remove the file .../_uninstall/payloads/InformationAnalyzer/IADB/RollbackActions.xml
3. Remove the "InformationServer/_uninstall/inprogress" directory (and contents)
4. Reapply the FixPack.

Refer: http://www-01.ibm.com/support/docview.w ... wg21591876

Edit: It seems that cancelling an upgrade does not completely rollback the work. Some checkpoints are maintained in the "inprogress" and "RollbackActions", but from the errors we received, it looks like things still get out of sync. Restoring the filesystem (and the XMETA database) is the safest approach, after a failed upgrade.
Last edited by Gazelle on Wed Sep 11, 2013 7:52 pm, edited 2 times in total.
Top
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Post by roy »

Thanks for sharing!
I took the liberty of marking the topic resolved.
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
Top
Post Reply

Return to “General”