0 Replies Latest reply on Jan 31, 2011 1:46 AM by Christian Scharr

    REST-Interface doesn't send messages to queue

    Christian Scharr Newbie

      Hi there,

       

      I'm using HornetQ embedded, configuring and initializing it directly in my source-code at runtime. I did the same with the REST interface, embedding it via the filter (@Jetty7) and did a small modification to the rest-bootstrapping class to include the configuration aspects.

       

      Testing HornetQ directly (using core methods) succeeded, getting informations about available queues via AJAX over the REST interface succeeds, too. But sending a message via AJAX over the REST interface results in a 201 (created) return-value but the message doesn't ever reaches the queue...

      I can't receive the message neither via REST interface nor HornetQ directly. It seems the message is lost somewhere on the way to it's destiny :-(

       

      Any idea why this happens or what I did wrong? I would be grateful for any informations or starting-point!

       

      Sitting on this bug whole 4 days in a row now just makes my brain feel squishy.

       

      Greetz,

      Christian

       


      P.s.

      The modified part of the HornetQRestBootstrapping class to handle the configuration looks like the following

       

      MessageServiceConfiguration msgConfig = new MessageServiceConfiguration();
      msgConfig.setInVmId("0");
      msgConfig.setUseLinkHeaders(false);
      msgConfig.setDefaultDurableSend(false);
      msgConfig.setDupsOk(true);
      msgConfig.setTopicPushStoreDirectory("./work/msg/topic-push-store");
      msgConfig.setQueuePushStoreDirectory("./work/msg/queue-push-store");
      msgConfig.setProducerSessionPoolSize(10);
      msgConfig.setTimeoutTaskInterval(1);
      msgConfig.setConsumerSessionTimeoutSeconds(300);
      msgConfig.setConsumerWindowSize(-1);
      
      manager.setConfiguration(msgConfig);