SeeBeyond 4.5.3 and SeeBeyond ICAN 5.0

Help
2004-06-30
2004-08-25
  • danhatfield
    danhatfield
    2004-06-30

    I was able to successfully connect to both of these JMS implementations and browse JMS messages.

    The topic configs are below. The first is ICAN and the second is 4.5.3.

        <factory>
            <provider className="com.stc.jms.client.STCTopicConnectionFactory">
                <properties>
                    <property name="host" value="localhost"/>
                    <property name="port" value="18008"/>
                </properties>
            </provider>
            <connection>
                <session transacted="true" reconnects="0" audit="false" id="SeeBeyondTopic"/>
            </connection>
            <destination name="Dan" domain="2"/>
        </factory>
        <factory>
            <provider className="com.seebeyond.jms.client.STCTopicConnectionFactory">
                <properties>
                    <property name="host" value="localhost"/>
                    <property name="port" value="24053"/>
                </properties>
            </provider>
            <connection>
                <session transacted="true" reconnects="0" audit="false" id="SeeBeyond4.5.3"/>
            </connection>
        </factory>

     
    • Colin Crist
      Colin Crist
      2004-06-30

      Excellent news, thanks for sharing.

      If you could send me a screenshot I'll add it to the providers page for 1.7.

      Colin.

       
    • Eske
      Eske
      2004-07-23

      Thanks for the info. I succeeded in connecting to Seebeyond 4.5.3 with STCQueueConnectionFactory but this is as far as I got. Whenever i click 'browse' on a queue I have entered I get a message saying: "Not implemented". The hermes.log with the error is pasted in below. I think it indicates that seebeyond has not implemented some method used for browsing the JMS queues or maybe I'm just missing something vital.. Any ideas?

      Eske

      <hermes.log>
      2004-07-23 13:51:59,734 [Hermes ThreadPool-2] ERROR hermes.browser.AbstractActionImpl - in doAction(): Not implemented
      javax.jms.JMSException: Not implemented
          at com.seebeyond.jms.client.STCQueueSession.createBrowser(STCQueueSession.java:211)
          at hermes.impl.jms102.AbstractSessionManager.createBrowser(AbstractSessionManager.java:299)
          at hermes.impl.DefaultHermesImpl.createBrowser(DefaultHermesImpl.java:155)
          at hermes.browser.BrowserAction.doQueueBrowse(BrowserAction.java:261)
          at hermes.browser.BrowserAction.doAction(BrowserAction.java:507)
          at hermes.browser.AbstractActionImpl.run(AbstractActionImpl.java:90)
          at hermes.impl.ThreadPool.run(ThreadPool.java:183)
          at java.lang.Thread.run(Thread.java:536)
      </hermes.log>

       
    • Colin Crist
      Colin Crist
      2004-07-28

      It looks that way - that exception is coming from within the Seebeyond provider.

      Check the release notest etc. to see if QueueBrowser is implemented in this version.

      Colin.

       
    • Eske
      Eske
      2004-08-19

      You might have a point. Here is the "fantastic" QueueBrowser implementation in SeeBeyond 4.5.3:

      package com.seebeyond.jms.client;

      import java.util.Enumeration;
      import javax.jms.*;

      public class STCQueueBrowser
          implements QueueBrowser
      {

          public STCQueueBrowser()
          {
          }

          public Queue getQueue()
              throws JMSException
          {
              return null;
          }

          public String getMessageSelector()
              throws JMSException
          {
              return null;
          }

          public Enumeration getEnumeration()
              throws JMSException
          {
              return null;
          }

          public void close()
              throws JMSException
          {
          }
      }

      Is that a problem?? ;-)

       
    • Colin Crist
      Colin Crist
      2004-08-25

      I reckon so. Shame on those who thought they could release that provider!

      Colin.

       
    • Colin Crist
      Colin Crist
      2004-08-25

      I reckon so. Shame on those who thought they could release that provider!

      Colin.