Ok, I'll look a little deeper into the logs. I wanted to make sure there wasn't something little that I'm missing. I'll see if I can find anything and post back what I find.
On Wed, May 14, 2008 at 1:51 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > I guess you'll find an exception logged somewhere that occurs when > smx/activemq > is started. Without it, i can't really do much ... > > On Wed, May 14, 2008 at 2:39 AM, Ryan Moquin <[EMAIL PROTECTED]> > wrote: > > Sorry, I should have mentioned that the error is what I get even with > the > > activemq.xml imported in servicemix.xml just like in the standalone > one. So > > I've already tried that, it is reading it since it started failing on a > > number of other jars. After it stopped complaining though, there is > still > > nothing running on the 61616 port as it specified in that file. > > > > > > > > On Tue, May 13, 2008 at 4:48 PM, Guillaume Nodet <[EMAIL PROTECTED]> > wrote: > > > > > Well, i meant it should work if you included the activemq.xml > > > configuration file from the > > > main xml file, else as you said, no broker will be started. > > > > > > On Tue, May 13, 2008 at 10:39 PM, Ryan Moquin <[EMAIL PROTECTED] > > > > > wrote: > > > > Ok, so it should work then, which is what I was hoping was the > answer. > > > > Basically, with the stand alone servicemix, I drop my jars into > hot > > > deploy, > > > > and after they are deployed, I start up a little test harness I > have > > > which > > > > makes an activemq connection to servicemix, to send test messages. > > > When I > > > > drop my component into the servicemix war, and tried to run the > test > > > > harness, I get a connection refused: > > > > > > > > Caused by: javax.jms.JMSException: Could not connect to broker > URL: > > > > tcp://localhost:61616. > > > > > > > > I'm assuming that even with no jbi components of my deployed, I > still > > > > shouldn't have a connection problem right? This makes me thing > I'm > > > missing > > > > something. I had noticed the war seems to not include the > majority of > > > > configuration files that the standalone one includes. > > > > > > > > > > > > > > > > On Tue, May 13, 2008 at 4:22 PM, Guillaume Nodet <[EMAIL PROTECTED] > > > > > wrote: > > > > > > > > > On Tue, May 13, 2008 at 10:05 PM, Ryan Moquin < > [EMAIL PROTECTED] > > > > > > > > > wrote: > > > > > > I'm still trying to work through getting the servicemix war up > and > > > > > running > > > > > > with our jbi components. I had to move a bunch of jar files > into > > > > > tomcat's > > > > > > lib/ext to make the classes that JBI components depend on in > the > > > > > standalone > > > > > > servicemix distribution classpath. But I'm not sure if I got > > > > > everything > > > > > > since my JBI components still don't work. The problem I'm > hitting > > > now, > > > > > is > > > > > > that it looks like the servicemix war doesn't start up an > activemq > > > > > broker? > > > > > > Or if it does, it starts it on a different port than the > > > standalone one > > > > > > does? I tried importing the activemq.xml config file from > the > > > > > standalone > > > > > > version, but that doesn't help. > > > > > > > > > > What kind of problems did you hit in doing so ? It should work > if you > > > put > > > > > the > > > > > needed jars in the war. > > > > > > > > > > > > > > > > > I'm a little puzzled on how to get the servicemix war to have > the > > > same > > > > > > functionality as the stand alone distribution. Has anyone > > > successfully > > > > > done > > > > > > this? > > > > > > > > > > > > Thanks! > > > > > > > > > > > > Ryan > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Cheers, > > > > > Guillaume Nodet > > > > > ------------------------ > > > > > Blog: http://gnodet.blogspot.com/ > > > > > > > > > > > > > > > > > > > > > -- > > > Cheers, > > > Guillaume Nodet > > > ------------------------ > > > Blog: http://gnodet.blogspot.com/ > > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
