Bugs item #979869, was opened at 2004-06-25 10:20
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=979869&group_id=22866
Category: JBossMQ
Group: v3.2
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: David Boon (davidmboon)
Assigned to: Nobody/Anonymous (nobody)
Summary: hajndi-jms-ds.xml has hardcoded reference to jndi port 1100
Initial Comment:
jboss version 3.2.4
hajndi-jms-ds.xml has hardcoded reference to jndi port
1100, this file should use the ServiceBindingManager to
determine the jndi port.
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
<attribute
name="ProviderName">DefaultJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>
<!-- The queue connection factory -->
<attribute
name="QueueFactoryRef">XAConnectionFactory</attribute>
<!-- The topic factory -->
<attribute
name="TopicFactoryRef">XAConnectionFactory</attribute>
<!-- Access JMS via HAJNDI -->
<attribute name="Properties">
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=localhost:1100
</attribute>
</mbean>
----------------------------------------------------------------------
>Comment By: Scott M Stark (starksm)
Date: 2004-08-11 08:19
Message:
Logged In: YES
user_id=175228
In addition, the Properties can be overriden by the
ServiceBindingManager config:
<service-config
name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config>
<attribute name="Properties">
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces^M
java.naming.provider.url=${host}:${port}
</attribute>
</delegate-config>
<binding port="1100" host="somehost"/>
</service-config>
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2004-07-13 08:44
Message:
Logged In: YES
user_id=9459
ping, or I will close this.
----------------------------------------------------------------------
Comment By: Adrian Brock (ejort)
Date: 2004-06-28 11:21
Message:
Logged In: YES
user_id=9459
What difference would this make?
It is not defining a port binding here, it is defining which
port to use.
Even if the VM running HAJNDI on 1100 was down, it would use
discovery to locate an instance running HAJNDI.
In fact, you could leave out the java.naming.provider.url
altogether and it would still work.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=979869&group_id=22866
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
