NullPointerException during failover on 5.7MP2

Question

I just saw this error (below) today during the failover of the primary engine to the backup engine. This message was in the backup engine's log file (soon to be primary engine) and occurred right after the "[SSM] Primary server is not responding. Attempting to take over ..." message. We are running 5.7MP2 as a standalone enterprise installation. Thanks for any insight you can provide.
An exception occurred while executing a transaction. Details:
java.lang.NullPointerException
java.lang.NullPointerException
     at fuego.fengine.FEngineConnectedClient.clean(FEngineConnectedClient.java:224)
     at fuego.server.service.ConnectedClientService.clean(ConnectedClientService.java:243)
     at fuego.server.ConnectedClient$1.execute(ConnectedClient.java:178)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:290)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:462)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:540)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:117)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1478)
     at fuego.lang.JavaObject.invoke(JavaObject.java:185)
     at fuego.component.Message.process(Message.java:585)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:759)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:734)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:140)
     at fuego.fengine.service.FEngineExecution$1.processBatch(FEngineExecution.java:105)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:818)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:397)

Answer 1

Contact [email protected] and reference CR081579.
Tom LeRoux wrote:
Has anyone seen this NPE when creating an InitialContext? We got this for about
a day on one of our cluster instances, and then it magically went away (the other
server in the cluster worked fine).. Solaris, Weblogic 5.1 service pack 10.
java.lang.NullPointerException
at weblogic.rjvm.RJVMFinder.equals(RJVMFinder.java:98)
at java.util.Hashtable.get(Hashtable.java:323)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:190)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:195)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support