2 Replies Latest reply on Jan 26, 2009 11:10 AM by jmesnil

    Connection Factory Configuration problem in JBoss Messaging

    siddharth_2279

      Hi All,
      I have my own connection factory entry in (jboss-5.0.0.GA\server\default\deploy\messaging\connection-factories-service.xml)

      <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
       name="jboss.messaging.connectionfactory:service=MyExampleConnectionFactory"
       xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
      
       <constructor>
      
       <!-- You can specify the default Client ID to use for connections created using this factory -->
      
       <arg type="java.lang.String" value="MyClientID"/>
      
       </constructor>
      
       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
      
       <!-- The transport to use - can be bisocket, sslbisocket or http -->
      
       <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
      
       <depends>jboss.messaging:service=PostOffice</depends>
      
       <!-- The connection factory will be bound in the following places in JNDI -->
      
       <attribute name="JNDIBindings">
      
       <bindings>
      
       <binding>/QueueConnectionFactory</binding>
      
       </bindings>
      
       </attribute>
      
       </mbean>
      


      When I run the Java code I get the following exception :

      JNDI lookup failed: javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.jms.client.JBossConnectionFactory (no security manager: RMI class loader disabled)]


      I even saw the solution to this as per given in the site :

      https://jira.jboss.org/jira/browse/JBMESSAGING-339

      But even the solution 1 given here in the site namely :

      1) Enable JNDI call by reference semantics.

      To do that, modify the Naming (JNDI) service configuration and set its "CallByValue" attribute to "false".

      The Naming configuration file is $JBOSS_HOME/server/default/deploy/naming-service.xml for an installer-generated JBoss configuration and the $JBOSS_HOME/server/conf/jboss-service.xml (the JNDI section, search for "jboss:service=Naming") for a raw installation.


      is not working.

      Even this is giving a exception in the java program.

      Please Help me in solving this problem.

      I am using JBoss-5.0.0.GA app server.

      Thanks in advance.

        • 1. Re: Connection Factory Configuration problem in JBoss Messag
          siddharth_2279

          1) Any update on this topic. Please Help !!!

          2) Also does JBoss 5.0.0-G.A. not give us a default QueueConnectionFactory and TopicConnectionFactory. This seems to be the case as its giving QueueConnectionFactory not bound. But in JBoss-4.2.2 G.A. we used to get a default QueueConnectionFactory and TopicConnectionFactory.

          Please reply and thanks in advance.

          • 2. Re: Connection Factory Configuration problem in JBoss Messag
            jmesnil

             

            "siddharth_2279" wrote:
            1) Any update on this topic. Please Help !!!


            Have you checked that the client application has all the required jars listed in the documentation?

            "siddharth_2279" wrote:

            2) Also does JBoss 5.0.0-G.A. not give us a default QueueConnectionFactory and TopicConnectionFactory. This seems to be the case as its giving QueueConnectionFactory not bound. But in JBoss-4.2.2 G.A. we used to get a default QueueConnectionFactory and TopicConnectionFactory.


            In JBoss AS 5, connection factories are defined in server/$CONFIG/deploy/messaging/connection-factories-service.xml