1 2 Previous Next 17 Replies Latest reply on Aug 10, 2009 10:00 AM by sanches Go to original post
      • 15. Re: Receiving XML from c++ sender
        timfox

        First of all, you are using JBoss Messaging 1.x , not JBoss MQ (default JMS provider in AS 5.0 is JBM) - I can see that in the stack trace.

        javax.jms.JMSException: There is no administratively defined topic with name:SERVER/TOP
        


        In JBM 1.x Having a forward slash in a destination name is illegal (there was a recent thread on this on this forum). You could try defining your topic as server.top, using a dot '.' to delimit words in a destination is also more consistent with how many other messaging systems define topic hierarchies.




        • 16. Re: Receiving XML from c++ sender
          sanches

           

          "timfox" wrote:
          First of all, you are using JBoss Messaging 1.x , not JBoss MQ (default JMS provider in AS 5.0 is JBM) - I can see that in the stack trace.

          Thanks for clarification, I was thinking that's MQ due to my declaration of JBoss' MBean:
           <mbean code="org.jboss.mq.server.jmx.Topic"
           name="jboss.mq.destination:service=Topic,name=SERVER/TOP">
           <attribute name="JNDIName">SERVER/TOP</attribute>
           <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
           </mbean>
          


          "timfox" wrote:
          In JBM 1.x Having a forward slash in a destination name is illegal (there was a recent thread on this on this forum). You could try defining your topic as server.top, using a dot '.' to delimit words in a destination is also more consistent with how many other messaging systems define topic hierarchies.


          Thank you, I've replaced slashes with dots and that's working well.

          P.S. I was not able to find topic you talked about. Search isn't working. Hope this issue is in plans to fix already.

          • 17. Re: Receiving XML from c++ sender
            sanches

            I just discovered that ActiveMQ's implementation of C++ Stomp client does not support Temporary Destinations...
            Thus, request - response model like described there:
            http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html does not work.
            C++ client attempting to create temporary destination fails:

            StompConnector::createTemporaryQueue - No Stomp Support
            FILE: ..\src\main\activemq\connector\stomp\StompConnector.cpp, LINE: 409
            FILE: ..\src\main\activemq\connector\stomp\StompConnector.cpp, LINE: 413
            FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 451

            StompConnector::createTemporaryTopic - No Stomp Support
            FILE: ..\src\main\activemq\connector\stomp\StompConnector.cpp, LINE: 392
            FILE: ..\src\main\activemq\connector\stomp\StompConnector.cpp, LINE: 396
            FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 479


            I can not create regular topic instead of temporary one:
            17:57:45,203 ERROR [ExceptionUtil] SessionEndpoint[bb-7v8q97yf-1-lbki67yf-bp1h6r-w30b3a] createTopic [db-nv8q97yf-1-lbki67yf-bp1h6r-w30b3a]
            javax.jms.JMSException: There is no administratively defined topic with name:tmpTopic01

            Seems like JBoss does not allow creating topics from outside.

            How could I implement [request from client - response from server] model then?..


            1 2 Previous Next