Hi, Also such problem may occur when servicemix jmx/rmi connector is running on non default port, even if you define valid port number with sm.port property. sm.port property is not passed to any ant tasks in default servicmix-ant-task.xml file.
I've just created a jira (https://issues.apache.org/activemq/browse/SM-1892) related to this issue. Ying wrote: > > Hi, > > I tried very hard to try to get at least one of the ant task (in 3.0-M2 ) > working, but no luck. Please help or advise. > > I used jdk1.5.0_07 and ant 1.6.5 to start a standalone servicemix. > > I called this on a command line and got following exception: > ant -f servicemix-ant-task.xml list-service-assemblies > > The exception on console is: > Buildfile: servicemix-ant-task.xml > > list-service-assemblies: > [echo] list-service-assemblies > [echo] list deployed Service Assemblies in Servicemix. > [echo] host=localhost > [echo] port=1099 > [echo] state= > [echo] componentName= > [echo] serviceAssemblyName= > [jbi-list-service-assemblies] Error accessing ServiceMix administration: > Failed > to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root > excep > tion is java.rmi.ConnectException: Connection refused to host: localhost; > nested > exception is: > [jbi-list-service-assemblies] java.net.ConnectException: Connection > refused: c > onnect] > > BUILD FAILED > > Any help would be highly appreciated. > -Ying > > -- View this message in context: http://www.nabble.com/servicemix-3.0_M2-servicemix-ant-task.xml-doesn%27t-work-tp5636491p25359307.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
