that error seems more like multicast is not supported rather than there is no network. If you disable multicast discovery/publish, can the regular tcp transport connector start and listen?
Unfortunately there is no retry on the inital start procedure of activemq. If a configured services are not available the exception propagates through to effect a failure. I guess this is mainly this is because a broker with no network or no store, for example, is not very useful. 2009/10/26 Ryan Moquin <[email protected]> > Here's the relevant portion of the stack trace which will show you what > happens when starting up a broker in it's default configuration without a > network connection. This is also using the latest fuse distro (3.4.0.4). > on > windows btw. Basically, when the ActiveMQ Broker attempts to start, it > will > fail due to there being no network connection. It would be nice if maybe > the connection could be periodically restarted until the network connection > is available.. not sure what happens when the network connection goes down > if ActiveMQ is up, but it would be nice if it could handle it gracefully > and > restore the multicast connection when the network is available again. > Hopefully there is already someway that this can be dealt with gracefully. > > Ryan > > Loading Apache ServiceMix from servicemix.xml on the CLASSPATH > ERROR - BrokerService - Failed to start ActiveMQ JMS > Message Br > oker. Reason: java.net.SocketException: error setting options > java.net.SocketException: error setting options > at java.net.PlainDatagramSocketImpl.join(Native Method) > at > java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:17 > 2) > at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276) > at > org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryA > gent.start(MulticastDiscoveryAgent.java:297) > at > org.apache.activemq.broker.TransportConnector.start(TransportConnecto > r.java:244) > at > org.apache.activemq.broker.BrokerService.startTransportConnector(Brok > erService.java:1929) > at > org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerSer > vice.java:1875) > at > org.apache.activemq.broker.BrokerService.start(BrokerService.java:495 > ) > at > org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBean > BrokerService.java:56) > > On Fri, Oct 23, 2009 at 6:47 AM, Gary Tully <[email protected]> wrote: > > > can you expand on what you are seeing? > > > > 2009/10/23 Ryan Moquin <[email protected]> > > > > > I've had problems with the multicast discovery in activemq when a > network > > > connection isn't present, as well as others. Is that really an > expected > > > behavior? Is there any reason that activemq couldn't gracefully handle > > > that > > > situation by just logging a message until the network connection is > > > available? > > > > > > Ryan > > > > > > > > > > > -- > > http://blog.garytully.com > > > > Open Source Integration > > http://fusesource.com > > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
