PQ49310: UNSATISFIEDLINKERROR FOR BBOLORB WHEN SERVLET TRIES TO ACCESS TO EJB IN LOCALE JA_JP.IBM-939

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Servlet ran in locale Ja_JP.IBM-939 got UnsatisfiedLinkError for
bbolorb when trying to access to EJB. "bbolorb" was not convert-
ed from ASCII to EBCDIC as expected to be passed to dllload.
WAS Level 2 bypassed this symptom by not loading bbolorb, but
hit similar incident later for another string.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: A customer attempted to issue a         *
*                      CBSeriesGlobalInit to connect           *
*                      to WebSphere 4.0 for z/OS to access     *
*                      the JNDI name                           *
*                      space from a servlet program running    *
*                      under WebSphere 3.5 SE.  This process   *
*                      works fine with the english code page   *
*                      of En_US.IBM-1047, but failed when      *
*                      using the Japanese code page of         *
*                      Ja_JP.IBM-939.  It received an          *
*                      UnsatisfiedLinkError for bbolorb.       *
*                      This will fail for any code page        *
*                      that supports double byte character     *
*                      set.                                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1) The String Manager was using the compiler functions __AtoE
and __EtoA. to do conversions.  This ran into problems when
the runtime code page was different than the compile time code
page. Because we would be comparing runtime converted strings
to compiled time converted strings and they would not match and
we would fail.
2) The serialization process for the String Manager was
inefficient to handle our current needs. When the string manager
was created it was not done so with the thought of multiple
threads coming in from Java at the same time, in mind. This
current possibility could have caused race conditions and
other problems to occur.
Problem conclusion
String Manager was modified to handled the conversion and
serilization problems reported by this APAR.

The following publication was revised as a result
of APAR PQ49310:
________________________________________________________________
WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-00
________________________________________________________________
This APAR requires changes to documentation.
NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:


http://www.ibm.com/software/webservers/appserv/

________________________________________________________________
Chapter 13, pg. 423 (new message)
C9C21C45
Explanation: bbolUtil.cpp iconv_open failed during ASCII to
EBCDIC process.
User Response: Gather documentation and contact the IBM support
center.
________________________________________________________________
Chapter 13, pg. 423 (new message)
C9C21C46
Explanation: bbolUtil.cpp iconv failed during ASCII to EBCDIC
process.
User Response: Gather documentation and contact the IBM support
center.
________________________________________________________________
Chapter 13, pg. 423 (new message)
C9C21C47
Explanation: bbolUtil.cpp iconv_open failed during ASCII to
EBCDIC process.
User Response: Gather documentation and contact the IBM support
center.
________________________________________________________________
Chapter 13, pg. 423 (new message)
C9C21C48
Explanation: bbolUtil.cpp iconv failed in ASCII to EBCDIC
process.
User Response: Gather documentation and contact the IBM support
center.

APAR PQ49310 is associated with SERVICE LEVEL W400024 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ49310
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-06-06
Closed date 2001-07-26
Last modified date 2001-09-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOJJU BBOLORB BBOLRT BBOLRTU BBOLSREQ BBOLSS
BBOLSYS BBOLUTIL BBOOEJSB BBOTTJCU BBOUBINF  

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ56287    UP01/08/08 P F108

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ49310
IBM Group: Software Group
Modified date: Sep 5, 2001