APAR status
Closed as program error.
Error description
Customer deleted his container managed authentication alias and
his component managed authentication alias from the queue
connection factory panel and stopped and restarted the
AppServer, but he got J2CA0114W errors. The reason is that the
resource reference indicated that the authentication is by the
container and not by the application.
.
The message J2CA0114W should list three different possible
reasons why this error is logged.
To correct the condition causing the J2CA0114W either
1) do a direct JNDI lookup of the QCF, TCF, or data source,
thereby bypassing the resource reference,
2) specify Application authentication on the resource
reference, so that WebSphere will not try to authenticate
with the container or component alias or
3) specify a container-managed authentication alias on the
QCF, TCF, or data source.
.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* JDBC, JCA and JMS Connections. *
****************************************************************
* PROBLEM DESCRIPTION: Update userAction for J2CA0114 message. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The J2CA0114 message was determined to be a little vague in
regard to userAction, to resolve the issue the message has
been updated as follows.
explanation=The application is using container-managed
authentication, but no container-managed authentication alias
was specified.
useraction=In some cases this may be ignored. Often this is
the results of a missing configuration option. If the
application is intended to use container-managed
authentication the Admin Console or scripting tools may be
used to configure a container-managed alias for the
ConnectionFactory or DataSource. If the application is
intended to use component-managed authentication then the
resource reference should be modified so that the
authentication mechanism is "component", "per connection
factory", or "application".
Problem conclusion
Updated english message file. The message will be translated
during the next translation phase.
Temporary fix Comments
APAR information |
APAR number |
PQ89976 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-06-10 |
Closed date |
2004-08-02 |
Last modified date |
2004-08-02 |
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 |
|