Bugs item #979869, was opened at 2004-06-25 17:20
Message generated for change (Comment added) made by ejort
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=979869&group_id=22866

Category: JBossMQ
Group: v3.2
Status: Open
Resolution: None
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: Adrian Brock (ejort)
Date: 2004-07-13 15:44

Message:
Logged In: YES 
user_id=9459

ping, or I will close this.

----------------------------------------------------------------------

Comment By: Adrian Brock (ejort)
Date: 2004-06-28 18: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


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to