APAR status |
Closed as user error.
| Error description
In WAS 3.5.4 when XMLConfig API is used to manage
applications, it gives javax.naming.NamingException, whereas
everything works fine when command-line procedure is used.
During through analysis, I found that the problem lies in
XMLConfig(String adminNodeName, boolean _advanced, String
nameServiceHost, int nameServicePort) constructor, which the
customer is using in it's application(here, TestXmlConfig)
for instantiating
In the above constructor, if the line
ctx = new InitialContext(p);
is replaced with
ctx = new InitialContext();
it starts working as expected. But then, the constructor looses
its main purpose.
When I used XMLConfig(String adminNodeName, boolean _advanced)
constructor,in the testcase, everything worked fine.
I would like to mention here that same line
ctx = new InitialContext(p);
works fine in WAS352. Local fix
No local fix available...customer has urgently requested an
eFix Problem summaryProblem conclusionTemporary fixComments
In 3.5.4, it is now necessary to secure a jsp if it wants to
access a secured resource. Doing so will take care of the
root cause of this issue.
APARS PQ49227,PQ49845 address the errors that they
were seeing spring up from the security.
APAR information | APAR number | PQ49648 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED USE | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-06-13 | Closed date | 2001-07-05 | Last modified date | 2001-07-05 |
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
Applicable component levels |
|