APAR status |
Closed as program error.
| Error description
Error message customer received did not propogate back to
client code. This prolonged finding the actual problem.
Opened against ORB component. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of ORB *
* plugins such as JTS, WLM, etc. *
****************************************************************
* PROBLEM DESCRIPTION: When starting a stand alone WebSphere *
* client, ORB plugins such JTS or WLM *
* are not successfully loaded due to *
* thread stack size being too small. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a stand-alone client application expects to use the JTS
component to access a back-end WebSphere server, the
instantiation of the JTS component will be unsuccessful due
to the JVM stacksize's limitation.
.
The flow of client side is, the client application initializes
an WebSphere ORB instance whenever it calls the initialContext
the very first time. InitialContext, in turn, tries to
instantiate client side ORB instance to make communication to
the back-end EJB server. During this instantiation period, ORB
starts all required plug-ins such as WLM, JTS, etc. Since
the default JVM stack size is too small, JTS was unable to start
and the client was unable to use JTS component to complete
transaction. Problem conclusion
Using the efix won't resolve the problem. This efix only
allows an error message to be visible to the users. In order to
make the client start and run successfully, users need to
increase the stack size of client side JVM to 1 MegaByte or
larger. For example, "$java -Xss1M -classpath
c:/myTestFiles/test.jar myTestClient". Temporary fixComments
APAR information | APAR number | PQ60103 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-04-15 | Closed date | 2002-04-24 | Last modified date | 2002-04-25 |
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:
PQ60517
Modules/Macros APAR is sysrouted TO one or more of the following:PQ60517Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|