commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michiel Kalkman (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-343) JNDIConfiguration::recursiveGetKeys goes out of stack (2)
Date Fri, 10 Dec 2010 15:15:02 GMT


Michiel Kalkman commented on CONFIGURATION-343:

I am unable to reproduce the original problem. However, I now have a problem which looks like
this one, where different Context instances are generated for the same JNDI name.

Because I work in a jdk 1.4 environment, I could not use the contents of the configuration2
branch for testing.

To solve the problem, I applied a few changes - see the attached patch. This patch is applied

In the patch I use getNameInNamespace() operation on contexts. If this operation is supported,
the result of the operation is used to register processed Contexts. Otherwise, whe the getNameInNamespace()
is not supported, the Contexts are used to register processed Contexts.

> JNDIConfiguration::recursiveGetKeys goes out of stack (2)
> ---------------------------------------------------------
>                 Key: CONFIGURATION-343
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.5
>            Reporter: Michiel Kalkman
>            Priority: Minor
>             Fix For: 1.7
> See
> I think the maxDepth feature should be implemented.
> The reason for this is that in WebSphere it seems possible that some contexts seem te
be generated on the fly, like
> thisNode.cell -->
> thisNode.cell.cell -->
>  ...-->
>  thisNode.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell
> etc.
> (anybody any idea why this is so ?)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message