My Oracle Support Banner

Tuxedo Java Client Is Getting CORBA Exception Once Daylight Savings Time Change Occurs. (Doc ID 1474522.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Tuxedo - Version 10.3.0 and later
Microsoft Windows (32-bit)

Symptoms

Tuxedo application server running on Windows platforms with automated Daylight Savings Time configured(DST). Once DST occurs an exception is returned to the Java CORBA client as follows:

org.omg.CORBA.BAD_OPERATION:   vmcid: 0x0  minor code: 0 completed: Maybe     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

==========Msg (7) for Server calls Handler - End  ==========      at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(Unknown Source)
     at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(Unknown Source)
     at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(Unknown Source)
     at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
     at xxxxxxx._xxxxxServiceStub.login(Unknown Source)


If OBB tracing is turned on the exception can be seen in the trace log for the Tuxedo application server:

04/18/2012 14:30:40: tid.3792 ServerRequestImpl::SetCtxValues
04/18/2012 14:30:40: tid.3792 ServerRequestImpl::OBB__set_exception
04/18/2012 14:30:40: tid.3792 Set err
04/18/2012 14:30:40: tid.3792 ErrorInfo:
04/18/2012 14:30:40: tid.3792     IOPError
04/18/2012 14:30:40: tid.3792         m_completed = 2
04/18/2012 14:30:40: tid.3792         m_minor = 0
04/18/2012 14:30:40: tid.3792         m_status = 98304
04/18/2012 14:30:40: tid.3792     IOPError
04/18/2012 14:30:40: tid.3792         id = IDL:omg.org/CORBA/BAD_OPERATION:1.0
04/18/2012 14:30:40: tid.3792         IOPRoot:
04/18/2012 14:30:40: tid.3792             m_refcount = 1
04/18/2012 14:30:40: tid.3792 ServerRequestImpl::Reply
04/18/2012 14:30:40: tid.3792 TGIOPReqSender::Reply:
04/18/2012 14:30:40: tid.3792 Assuming error
04/18/2012 14:30:40: tid.3792 ErrorInfo:
04/18/2012 14:30:40: tid.3792     IOPError
04/18/2012 14:30:40: tid.3792         m_completed = 2
04/18/2012 14:30:40: tid.3792         m_minor = 0
04/18/2012 14:30:40: tid.3792         m_status = 98304
04/18/2012 14:30:40: tid.3792     IOPError
04/18/2012 14:30:40: tid.3792         id = IDL:omg.org/CORBA/BAD_OPERATION:1.0
04/18/2012 14:30:40: tid.3792         IOPRoot:
04/18/2012 14:30:40: tid.3792             m_refcount = 1
04/18/2012 14:30:40: tid.3792 TGIOPReqSender::Reply: server request had exception

 

Workaround:
Disable automated DST configuration on the windows platform and manually do the time change.

Changes

 Daylight savings time

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.