[JBoss JIRA] Created: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
4:18 a.m.
InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Carlo de Wolf
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]
Dimitris Andreadis updated JBAS-4805:
-------------------------------------
Fix Version/s: (was: JBossAS-5.0.0.Beta3)
(was: JBossAS-4.2.2.GA)
Don't set the fix versions!
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Carlo de Wolf
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381139 ]
Galder Zamarreno commented on JBAS-4805:
----------------------------------------
Ok, ok, ok... :)
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: Carlo de Wolf
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]
Carlo de Wolf reassigned JBAS-4805:
-----------------------------------
Assignee: William DeCoste (was: Carlo de Wolf)
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381679 ]
Galder Zamarreno commented on JBAS-4805:
----------------------------------------
This can easily be reproduced by having a Resource injected that
it's only deployed in one of the nodes, for example, an HA Singleton
MBean like JBoss MQ in a clustered environment.
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381769 ]
Galder Zamarreno commented on JBAS-4805:
----------------------------------------
This issue has a secondary side effect where SessionContext.lookup() calls within
the bean that had the Resource injected also throws a
javax.naming.CommunicationException.
InitialContextFactory.getHAContext():
Hashtable env = ctx.getEnvironment(); // this is the Container's getEnc();
...
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
This call changes the EJB container's Context.PROVIDER_URL, so SessionContext.lookup
calls after this are gonna try to go localhost first. If they fail, they'll try do a
new InitIalContext()
which will probably succeed (it did in my tests)
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382223 ]
William DeCoste commented on JBAS-4805:
---------------------------------------
I've got this fixed for Branch_4_2 and Trunk - what other branches should I be
merging??
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382383 ]
Galder Zamarreno commented on JBAS-4805:
----------------------------------------
Potentially the 4.2 CP branch, but depends on Patch Triage Team
approving it. See JBPAPP-356.
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]
Galder Zamarreno updated JBAS-4805:
-----------------------------------
Workaround Description:
+ Workaround for injecting ConnectionFactory instances - Inject JmsXA instead of
ConnectionFactory
@Resource(mappedName="java:/JmsXA", type=javax.jms.ConnectionFactory.class)
private ConnectionFactory factory;
+ Workarounds for injecting Queue/Topic instances:
1.- Not to inject Queue and instead, assuming the queue name is "queue/A" use
the
following code to initialise it the first time you use the Queue instance variable:
String bindAddress = System.getProperty("jboss.bind.address") == null ?
"localhost" : System.getProperty("jboss.bind.address");
InitialContext ic = new InitialContext();
Queue queueA = (Queue)ic.lookup("jnp://" + bindAddress +
":1100/queue/A");
2.- For this second option, let's assume the queue name is "queue/B". In
this case,
you can add META-INF/jboss.xml to your EJB jar deployment, which looks like this:
<?xml version="1.0"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>InhaltPruefungVerwaltungBean</ejb-name>
<resource-ref>
<res-ref-name>queue/ref/B</res-ref-name>
<jndi-name>jnp://${jboss.bind.address:localhost}:1100/queue/B</jndi-name>
</resource-ref>
</session>
</enterprise-beans>
</jboss>
And inject the Queue in your EJB this way:
@Resource(mappedName="java:comp/env/queue/ref/B")
private Queue queueB;
was:
A possible workaround (that the customer is trying out at the moment is):
in deploy/cluster-service.xml:
<mbean code="org.jboss.ha.jndi.HANamingService"
name="jboss:service=HAJNDI">
...
<!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
<attribute name="BindAddress">localhost</attribute>
Updated with workarounds from support case.
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4805) InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
[ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]
William DeCoste closed JBAS-4805.
---------------------------------
Fix Version/s: JBossAS-4.2.3.GA
Resolution: Done
I made this fix in JBPAPP_4_2_0_GA_CP for EAP 4.2.0 CP02
InitialContextFactory.getHAContext() should not use hardcoded
localhost for lookup
----------------------------------------------------------------------------------
Key: JBAS-4805
URL: http://jira.jboss.com/jira/browse/JBAS-4805
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
Reporter: Galder Zamarreno
Assigned To: William DeCoste
Fix For: JBossAS-4.2.3.GA
org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);
The code should not have hardcoded localhost because as soon as someone binds JBoss
to something different, a localhost lookup will fail.
This could should instead check HAJNDI service's BindAddress attribute and use that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6826
days inactive
6855
days old
9 comments
4 participants
participants (4)
-
Carlo de Wolf (JIRA) -
Dimitris Andreadis (JIRA)
-
Galder Zamarreno (JIRA)
-
William DeCoste (JIRA)