APAR status |
Closed as program error.
| Error description
Customer receives the following error when trying to start an ap
plication server:
[02.02.27 15:07:18:805 CST] edbe7aa8 ActiveEJBServ
W Failed to initialize a server: "MREEJB" com.ibm.ejs.
EJSException: Could not register with Location Service
Daemon; nested exception is:plication server:[02.02.27 15:07:18:805 CST], edbe7aa8 ActiveEJBServW Failed to initialize a server: "MREEJB" com.ibm.ejs.EJSException: Could not register with Location Service
java.rmi.MarshalException: CORBA BAD_PARAM 1 No;
nested exception is:Daemon; nested exception is:java.rmi.MarshalException: CORBA BAD_PARAM 1 No;
org.omg.CORBA.BAD_PARAM:. nested exception is:org.omg.CORBA.BAD_PARAM:. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All Websphere Application Server users *
* re-starting application servers *
****************************************************************
* PROBLEM DESCRIPTION: When restarting an application server, *
* an application server re-registration *
* failure error is occuring. This error *
* does not occur when starting the *
* application server first time. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Service context TCS Svc Ctx bearing TCS character information is
exchanged between client and server on the first message from
client to server. Client would stop sending this service context
information upon a successful round-trip to server, presuming
that server would remember the service context information for
that connection hence forth, as a part of client optimization
algorithm. This scenario fails when a request message with
service context containing TCS character is flowing between
Admin Server as a client and LSD as a server, running on
separate ORB instances within the same JVM. In this scenario,
the Admin Server opens a new connection to the LSD (port 9000)
and makes two requests... the first is an invokeActiveObject()
request that goes to the LSD and correctly receives a
LOCATION_FORWARD response redirecting to another port (in an
Application Server JVM) on the same machine. The second request
is the registerServer() flow to the LSD's servant without
service context containing TCS character. LSD Server is replying
with SYSTEM_EXCEPTION reply message. The actual error message as
seen by customer is as given below:
02.02.08 16:53:39:452 JST 65ed13dc ActiveEJBServ W Failed to
initialize a server: "ASARE1002" com.ibm.ejs.EJSException:seen by customer is as given below:02.02.08 16:53:39:452 JST 65ed13dc ActiveEJBServ W Failed to
Could not register with Location Service Daemon; nested
exception is:initialize a server: "ASARE1002" com.ibm.ejs.EJSException:Could not register with Location Service Daemon; nested
java.rmi.MarshalException: CORBA BAD_PARAM 1 No; nested
exception is: org.omg.CORBA.BAD_PARAM: minor code: 1
completed: No
java.rmi.MarshalException: CORBA BAD_PARAM 1 No; nested
exception is:exception is:java.rmi.MarshalException: CORBA BAD_PARAM 1 No; nestedexception is: org.omg.CORBA.BAD_PARAM: minor code: 1completed: Nojava.rmi.MarshalException: CORBA BAD_PARAM 1 No; nested
org.omg.CORBA.BAD_PARAM: minor code: 1 completed: No
org.omg.CORBA.BAD_PARAM: minor code: 1 completed: No
at java.lang.reflect.Constructor.NewInstance(Native Method)
at com.ibm.CORBA.iiop.ReplyMessage.getSystemException
(ReplyMessage.java(Compiled Code))
at com.ibm.rmi.iiop.ClientResponseImpl.getSystemException
(ClientResponseImpl.java:89)
at com.ibm.CORBA.iiop.ClientDelegate.
invoke(ClientDelegate.java (Compiled Code))
at org.omg.CORBA.portable.ObjectImpl.
_invoke(ObjectImpl.java:250)
at com.ibm.CORBA.services.lsd._LocationService_Stub.
registerServer(_LocationService_Stub.java:217)
at com.ibm.CORBA.services.lsd.LocationServiceClient.
reRegisterServer (LocationServiceClient.java:222)
at com.ibm.ejs.oa.LocationService.registerManagedServer
(LocationService.java:246)
The inference is that an incoming request bearing TCS Svc Ctx
and which is returned with LOCATION_FORWARD is not storing the
TCS information for that connection on the server, yet the
client end is treating the LOCATION_FORWARD as a successful
round-trip to the server and therefore not sending the TCS info
on further requests (the optimisation algorithm).
Actual Exception Seen In ORB Trace
org.omg.CORBA.BAD_PARAM: minor code: 1 completed: No.
at com.ibm.rmi.iiop.CDRInputStream.convertFromTcsWChar(CDRInput
Stream.java(Compiled Code))
at com.ibm.rmi.iiop.CDRInputStream.read_wstring(CDRInputStream.
java (Compiled Code))
at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.
java(CompiledCode))
at com.ibm.CORBA.services.lsd._LocationServant_Tie._invoke
(_LocationServant_Tie.java:78)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(Extended
ServerDelegate.java(Compiled Code))
at com.ibm.CORBA.iiop.ORB.process(ORB.java(Compiled Code))
at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java(
Compiled Code))
at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.
java(Compiled Code)).....K.......
IDL:omg.org/CORBA/BAD_PARAM:1.0. exception is:org.omg.CORBA.BAD_PARAM: minor code: 1 completed: Noorg.omg.CORBA.BAD_PARAM: minor code: 1 completed: Noat java.lang.reflect.Constructor.NewInstance(Native Method)at com.ibm.CORBA.iiop.ReplyMessage.getSystemException(ReplyMessage.java(Compiled Code))at com.ibm.rmi.iiop.ClientResponseImpl.getSystemException(ClientResponseImpl.java:89)at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java (Compiled Code))at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:250)at com.ibm.CORBA.services.lsd._LocationService_Stub.registerServer(_LocationService_Stub.java:217)at com.ibm.CORBA.services.lsd.LocationServiceClient.reRegisterServer (LocationServiceClient.java:222)at com.ibm.ejs.oa.LocationService.registerManagedServer(LocationService.java:246)The inference is that an incoming request bearing TCS Svc Ctxand which is returned with LOCATION_FORWARD is not storing theTCS information for that connection on the server, yet theclient end is treating the LOCATION_FORWARD as a successfulround-trip to the server and therefore not sending the TCS infoon further requests (the optimisation algorithm).Actual Exception Seen In ORB Traceorg.omg.CORBA.BAD_PARAM: minor code: 1 completed: No.at com.ibm.rmi.iiop.CDRInputStream.convertFromTcsWChar(CDRInputStream.java(Compiled Code))at com.ibm.rmi.iiop.CDRInputStream.read_wstring(CDRInputStream.java (Compiled Code))at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java(CompiledCode))at com.ibm.CORBA.services.lsd._LocationServant_Tie._invoke(_LocationServant_Tie.java:78)at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java(Compiled Code))at com.ibm.CORBA.iiop.ORB.process(ORB.java(Compiled Code))at com.ibm.CORBA.iiop.WorkerThread.run(WorkerThread.java(Compiled Code))at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java(Compiled Code)).....K.......IDL:omg.org/CORBA/BAD_PARAM:1.0. Problem conclusion
Required making code change that performs validation to see if
the request is of locate type to ClientDelegate.java file. Temporary fixComments
APAR information | APAR number | PQ60317 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-04-19 | Closed date | 2002-06-28 | Last modified date | 2002-07-08 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|