Hi, persistent is not a valid "client side" option. Try leaving it out.
Cheers -- Dejan Bosanac www.scriptinginjava.net On Thu, Jun 19, 2008 at 7:07 AM, Suchitha Koneru (sukoneru) < [EMAIL PROTECTED]> wrote: > Hello Active Mq users , > We are using active mq version 4.1.1. The broker is > started using a URI > broker.addConnector(tcp://10.66.254.90:78695?trace=true&wireFormat.maxIn > activityDuration=1800000&jms.useAsyncSend=true&jms.dispatchAsync=true&pe > rsistent=false<http://10.66.254.90:78695?trace=true&wireFormat.maxInactivityDuration=1800000&jms.useAsyncSend=true&jms.dispatchAsync=true&persistent=false> > ); > > When I try to connect to the same URI using jndi.properties I get the > exceptions included in the end . > > //JNDI properties > > java.naming.provider.url = > tcp://10.66.254.90:78695?trace=true&wireFormat.maxInactivityDuration=180 > 0000&jms.useAsyncSend=true&jms.dispatchAsync=true&persistent=false<http://10.66.254.90:78695?trace=true&wireFormat.maxInactivityDuration=1800000&jms.useAsyncSend=true&jms.dispatchAsync=true&persistent=false> > > //code for connecting to broker > > Context jndiContext = new InitialContext(); > > TopicConnectionFactory conFactory = (TopicConnectionFactory) > jndiContext.lookup("ConnectionFactory"); > > conFactory.createTopicConnection(); > > The exceptions are > > javax.jms.JMSException: Could not create Transport. Reason: > java.lang.IllegalArgumentException: Invalid connect parameters: > {persistent=false} > > Please let me know , if I need to change anything. > > thanks, > > Suchitha. > >
