2 Replies Latest reply on Jan 20, 2007 11:18 AM by burrsutter

    CR2 Trailblazer Problems

      All,

      I had the previous version of Trailblazer working fine but unfortunately can't get the current one to work. When I start it up (runESB) I lots of the output such as ....

      [java] 08:56:05,713 INFO [Registry] Initializing jUDDI components.
      [java] 08:56:05,713 INFO [ConnectionManager] Not using Datasource as juddi
      .isUseDataSource=false
      [java] 08:56:09,329 INFO [LocalTransport] Calling org.apache.juddi.registr
      y.local.InquiryService#inquire locally
      [java] 08:56:09,329 INFO [Registry] Loading jUDDI configuration.
      [java] 08:56:09,329 INFO [Registry] Resources loaded from: /juddi.properti
      es
      [java] 08:56:09,339 INFO [Registry] Initializing jUDDI components.
      [java] 08:56:09,339 INFO [ConnectionManager] Not using Datasource as juddi
      .isUseDataSource=false


      When I go to the traliblazer page I get the following

      [java] 08:56:33,906 ERROR [GatewayListenerController] Cannot launch <org.jb
      oss.soa.esb.listeners.gateway.JmsGatewayListener>
      [java]
      [java] java.lang.reflect.InvocationTargetException
      [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
      Method)
      [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeC
      onstructorAccessorImpl.java:39)
      [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Del
      egatingConstructorAccessorImpl.java:27)
      [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:49
      4)
      [java] java.lang.reflect.InvocationTargetException
      [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController
      .tryToLaunchGateway(GatewayListenerController.java:361)
      [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
      Method)
      [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController
      .run(GatewayListenerController.java:303)
      [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeC
      onstructorAccessorImpl.java:39)
      [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Del
      egatingConstructorAccessorImpl.java:27)
      [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:49
      4)
      [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController
      .tryToLaunchGateway(GatewayListenerController.java:361)
      [java] at org.jboss.soa.esb.listeners.gateway.GatewayListenerController
      .run(GatewayListenerController.java:303)
      [java] at java.lang.Thread.run(Thread.java:595)
      [java] Caused by: java.lang.OutOfMemoryError: Java heap space
      [java] at java.lang.Thread.run(Thread.java:595)
      [java] Caused by: java.lang.OutOfMemoryError: Java heap space
      [java] 08:56:45,193 INFO [RegistryException] Going to load org.jboss.inter
      nal.soa.esb.services.registry.JAXRRegistryImpl


      Can anyone shed any light on this. I am using MySQL as the registry and have changed the juddi property file on the server to reflect that as well as the juddi in trailblazer. Any suggestions ?

      Thanks,
      John

        • 1. Re: CR2 Trailblazer Problems

          BTW - I created my own app based on the trailblazer but with a JMS front end and had the same problems. However, if I deploy it in JBossAS then everything seems to work fine so I guess it must be a config thing

          • 2. Re: CR2 Trailblazer Problems
            burrsutter

            I have personally experienced this before. However, there is no set solution. I would suggest you break your solution into very small and discreet steps like so:
            - receive a message via JMS (or FTP or File drop or whatever)
            - send the message through an Action (display to console to see that it arrives)
            - change the action so that it does something with the message (pushes it to a database)
            - send a message back out to whomever cares
            Note: we don't support sync request/reply MEP via a gateway, only the TwoWay courier does this and it isn't well documented yet). It is best to establish a request/reply "queue" and use the correlationid feature of JMS to simulate sync.

            Have you had a chance to review the quickstarts as they break down these problems into small, easy to understand (I hope) examples? This might get you started quicker and then you can build up your solution over time.

            Burr