[JBoss JIRA] (AS7-2361) It appears there is no external JNDI port like 1099, even though the ports are in the console
3:04 p.m.
It appears there is no external JNDI port like 1099, even though the ports are in the
console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
David Lloyd resolved AS7-2361.
------------------------------
Resolution: Rejected
RMI-based JNDI is not supported in AS7.
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:10 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell updated AS7-2361:
-----------------------------
Attachment: Screen shot 2011-10-26 at 3.08.19 PM.png
Please see the attached screen shot for a JNDI port listing.
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-2361:
----------------------------------
It appears in the console that 1099 is being shown/used, however, in netstat it does not
show up in the listing so nothing appears to be listening on it. It is also listed in the
domain.xml as you can see here:
<socket-binding-groups>
<socket-binding-group name="standard-sockets"
default-interface="public">
<socket-binding name="http" port="8080"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="jacorb" port="3528"/>
<socket-binding name="jacorb-ssl" port="3529"/>
<socket-binding name="jmx-connector-registry"
port="1090" interface="management"/>
<socket-binding name="jmx-connector-server" port="1091"
interface="management"/>
<socket-binding name="jndi" port="1099"/>
<socket-binding name="messaging" port="5445"/>
<socket-binding name="messaging-throughput"
port="5455"/>
<socket-binding name="osgi-http" port="8090"
interface="management"/>
<socket-binding name="remoting" port="4447"/>
<socket-binding name="txn-recovery-environment"
port="4712"/>
<socket-binding name="txn-status-manager"
port="4713"/>
</socket-binding-group>
I am very confused.....please help...
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:14 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-2361:
----------------------------------
Also, how do you do external JNDI lookups? Or what is the recommended way?
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Summary: Remove JNDI port from standalone.xml (was: It appears there is no external
JNDI port like 1099, even though the ports are in the console)
Remove JNDI port from standalone.xml
------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene reopened AS7-2361:
-------------------------------
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 p.m.
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-2361:
-----------------------------------
Yeah the jndi port isn't used, it needs to be removed. JNDI lookups are now local they
only go remote in certain situations, and they go over the remoting port
It appears there is no external JNDI port like 1099, even though the
ports are in the console
---------------------------------------------------------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Issue Type: Task (was: Feature Request)
Remove JNDI port from standalone.xml
------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Naming
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Assignee: Jason Greene (was: John Bailey)
Fix Version/s: 7.1.0.Beta1
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: Jason Greene
Labels: eap6-ux
Fix For: 7.1.0.Beta1
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Description:
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
was:Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today.
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2361:
------------------------------
Summary: Remove JNDI port from standalone.xml/domain.xml (was: Remove JNDI port
from standalone.xml)
Component/s: Domain Management
(was: Naming)
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: John Bailey
Labels: eap6-ux
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
Many many customers use client lookups of JNDI contexts to get at what used to be called
remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is
this be design? If so, this is going to be a problem for many current customers, as they
do this today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-2361:
-----------------------------------
AS7-1936 is related to your other question about how you lookup a remote EJB. Also there
is standard EE app client support.
Both of these things will have docs but they aren't available yet
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: Jason Greene
Labels: eap6-ux
Fix For: 7.1.0.Beta1
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-2361:
----------------------------------
Jason, thank you for all the insight.
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: Jason Greene
Labels: eap6-ux
Fix For: 7.1.0.Beta1
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 p.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2361:
-------------------------------------
Assignee: Brian Stansberry (was: Jason Greene)
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Labels: eap6-ux
Fix For: 7.1.0.Beta1
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 a.m.
New subject: [JBoss JIRA] (AS7-2361) Remove JNDI port from standalone.xml/domain.xml
[
https://issues.jboss.org/browse/AS7-2361?page=com.atlassian.jira.plugin.s...
]
jaikiran pai reassigned AS7-2361:
---------------------------------
Assignee: jaikiran pai (was: Brian Stansberry)
Remove JNDI port from standalone.xml/domain.xml
-----------------------------------------------
Key: AS7-2361
URL: https://issues.jboss.org/browse/AS7-2361
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Jim Tyrrell
Assignee: jaikiran pai
Labels: eap6-ux
Fix For: 7.1.0.Beta1
Attachments: Screen shot 2011-10-26 at 3.08.19 PM.png
JNDI port was erroneously included in configuration files. It is not used and must be
removed (leads to confusion).
Original Description:
"Many many customers use client lookups of JNDI contexts to get at what used to be
called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this
work? Is this be design? If so, this is going to be a problem for many current
customers, as they do this today."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5366
days inactive
5374
days old
15 comments
9 participants
participants (9)
-
Brian Stansberry (Assigned) (JIRA) -
David Lloyd (Resolved) (JIRA)
-
jaikiran pai (Assigned) (JIRA)
-
Jason Greene (Commented) (JIRA)
-
Jason Greene (Reopened) (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Jim Tyrrell (Commented) (JIRA)
-
Jim Tyrrell (Created) (JIRA)
-
Jim Tyrrell (Updated) (JIRA)