You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Andreas (Jira)" <ji...@apache.org> on 2021/04/23 06:38:00 UTC

[jira] [Created] (TOMEE-3726) Queue is visible in JNDI Tree (java://id-resource)

Andreas created TOMEE-3726:
------------------------------

             Summary: Queue is visible in JNDI Tree (java://id-resource)
                 Key: TOMEE-3726
                 URL: https://issues.apache.org/jira/browse/TOMEE-3726
             Project: TomEE
          Issue Type: Bug
          Components: TomEE Core Server
    Affects Versions: 8.0.6
         Environment: Windows 10 Prof.
            Reporter: Andreas


Hi,

In *line 316* of *org.apache.openejb.server.ejbd.JndiRequestHandler* you use *java.util.Queue* instead *javax.jms.Queue* to compare (instaceof) the Object loaded from JNDITree.

The bug results in the following consequence:

If you have configured a *Queue* as resource, you can call this queue by a remote client (over RemoteInitialFactory->jndi-name: java://id-resource).

In contrast a *Topic* you cannot called by this way (results in null as instance).

The method "*doLookup(final JNDIRequest req, final JNDIResponse res, final String prefix)*" returns for a Queue *JNDI_OK* an for a Topic *JNDI_RESOURCE* as result.

So you can get a queue remote from the ejbd connector (not the right way i think) and a topic not.

Greetings
 Andreas Riesel



--
This message was sent by Atlassian Jira
(v8.3.4#803005)