APAR status
Closed as program error.
Error description
1. WAS is running and one client is running in separate JVM.
2. Client tries to authenticate itself (using JAAS) ->
authentication
succeeds ok.
3. WAS is restarted
4. Same client tries to authenticate itself again (using JAAS)
->
authentication FAILS!
Client is running while WAS is restarted. The workaround for
this is to
restart the client.
Sometimes it happens so that the client authentication succeeds
once
after WAS restart but then all subsequent authentications fail.
The exception that the client receives follows:
"
Dec 16, 2003 1:29:10 PM SessionManager<1>: (Login)
loginContext.login
NOT ok: com.ibm.websphere.security.auth.WSLoginFailedException:
CORBA
COMM_FAILURE 0x49421070 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: CONNECT_FAILURE_ON_SSL_CLIENT_SOCKET
-
JSSL0130E: java.io.IOException: Signals that an I/O exception of
some
sort has occurred. Reason: Connection refused minor code:
49421070
completed: No
"
Local fix
Change from dynamic to fixed orb and csiv2 port setup.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who have *
* enabled security and are utilizing *
* programmatic login. *
****************************************************************
* PROBLEM DESCRIPTION: After the server is restarted, the *
* client application fails to login any *
* new users. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The client caches server's ORB port. However, the server's ORB
port is dynamically generated whenever server is started. Thus,
after server restart, the client fails to connect to new ORB
port.
Problem conclusion
After failing login with a org.omg.CORBA.SystemException,
one retry will be made by the client after the port has been
cleared from the cache.
Temporary fix
test by customer and in local lab
Comments
APAR information |
APAR number |
PQ83679 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-01-23 |
Closed date |
2004-02-02 |
Last modified date |
2004-03-29 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|