Follow-up: I did a new SM installation and tried again. Still, the log gives an error during deployment*).
What puzzles me is that an (external) HTTP endpoint for the NotificationBroker does get established and even shows the correct WSDL when being requested via the Web console. Nevertheless, looking at the jetty-URL (http://localhost:8192/), I only can see the other deployed service. Please note that deploying other-, JSR181-provided HTTP consumer services on the same port is working fine. Nevertheless, for the WSN-provided service, it is only working if I choose a different port. Could it be that the servicemix-http component needs a different port for each component it is providing services for? Ciao, Philipp *) 12:34:47,454 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | DeploymentService | bi.framework.DeploymentService 459 | Moving C:\3.1.1\data\smx\tmp\wsn-broker-sa-0.1-SNAPSHOT.0.tmp to C:\3.1.1\data\smx\service-assemblies\wsn-broker-sa\version_1\install 12:34:47,454 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | DeploymentService | bi.framework.DeploymentService 509 | Unpack service unit archive C:\3.1.1\data\smx\service-assemblies\wsn-broker-sa\version_1\install\wsn -broker-http-0.1-SNAPSHOT.zip to C:\3.1.1\data\smx\service-assemblies\wsn-broker-sa\version_1\sus\service mix-http\wsn-broker-http 12:34:47,501 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | .common.BaseServiceUnitManager 61 | Deploying service unit 12:34:47,501 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | on.xbean.AbstractXBeanDeployer 53 | Looking for C:\3.1.1\data\smx\service-assemblies\wsn-broker-sa\version_1\sus\service mix-http\wsn-broker-http\xbean.xml: true 12:34:47,548 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | .common.BaseServiceUnitManager 75 | Service unit deployed 12:34:47,595 | INFO | RMI TCP Connection(6)-10.49.7.32 | DescriptorFactory | deployment.DescriptorFactory$1 104 | Validation error on file:/C:/3.1.1/data/smx/service-assemblies/wsn-broker-sa/version_1/sus/s ervicemix-http/wsn-broker-http/META-INF/jbi.xml: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'interface-name' must appear on element 'consumes'. 12:34:47,595 | INFO | RMI TCP Connection(6)-10.49.7.32 | DescriptorFactory | deployment.DescriptorFactory$1 104 | Validation error on file:/C:/3.1.1/data/smx/service-assemblies/wsn-broker-sa/version_1/sus/s ervicemix-http/wsn-broker-http/META-INF/jbi.xml: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'interface-name' must appear on element 'consumes'. 12:34:47,611 | INFO | RMI TCP Connection(6)-10.49.7.32 | ServiceAssemblyLifeCycle | ework.ServiceAssemblyLifeCycle 109 | Starting service assembly: wsn-broker-sa 12:34:47,611 | INFO | RMI TCP Connection(6)-10.49.7.32 | ServiceUnitLifeCycle | framework.ServiceUnitLifeCycle 78 | Initializing service unit: wsn-broker-http 12:34:47,611 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | .common.BaseServiceUnitManager 100 | Initializing service unit 12:34:47,611 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | .common.BaseServiceUnitManager 118 | Service unit initialized 12:34:47,611 | INFO | RMI TCP Connection(6)-10.49.7.32 | ServiceUnitLifeCycle | framework.ServiceUnitLifeCycle 97 | Starting service unit: wsn-broker-http 12:34:47,626 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | .common.BaseServiceUnitManager 137 | Starting service unit 12:34:47,626 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | e.servicemix.soap.SoapEndpoint 276 | Retrieving proxied endpoint definition 12:34:47,626 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | WSNComponent | mix.wsn.component.WSNComponent 71 | Querying service description for ServiceEndpoint[service={http://servicemix.org/wsnotification}Notificati onBroker,endpoint=Broker] 12:34:47,642 | DEBUG | RMI TCP Connection(6)-10.49.7.32 | HttpComponent | e.servicemix.http.HttpEndpoint 171 | WSDL only defines a PortType, using this one 12:34:47,861 | INFO | RMI TCP Connection(6)-10.49.7.32 | jetty | ervicemix.http.jetty.JCLLogger 80 | jetty-6.0.1 12:34:47,876 | WARN | RMI TCP Connection(6)-10.49.7.32 | jetty | ervicemix.http.jetty.JCLLogger 98 | failed SelectChannelConnector @ localhost:8192 12:34:47,892 | WARN | RMI TCP Connection(6)-10.49.7.32 | jetty | ervicemix.http.jetty.JCLLogger 98 | failed [EMAIL PROTECTED] 12:34:47,907 | INFO | RMI TCP Connection(6)-10.49.7.32 | DeploymentService | bi.framework.DeploymentService 376 | Error in start > -----Mensaje original----- > De: Rossmanith, Philipp > Enviado el: viernes, 17 de agosto de 2007 18:34 > Para: [email protected] > Asunto: Multiple servicemix-http service units: java.net.BindException > Importancia: Baja > > Dear all, > > I have a setup where I have to deploy multiple (in the beginning: 2) > servicemix-http service units packaged in different SAs. > > One is a SU publishing the wsn-NotificationBroker as an external > endpoint. Its xbean.xml file is copied from the examples*). > > The second SU is publishing an HTTP consumer endpoint which is supposed > to forward its input to a servicemix.xml-hard coded publisher. Its > xbean.xml is custom.**) > > I tried to deploy the SAs with both hot-deployment and mvn > jbi:projectDeploy deployment. In both cases, I get a > java.net.BindException***). > > Now I did some research in the forum****), and it seems that jetty is > starting up different instances attempting to connect to the same port. > > One recommendation was to make sure to deploy all SAs to the same > component. I used Maven tooling, supplying the same component dependency > and specifying the property "componentName". Nevertheless, it didn't > work. > > Also, as there will be more HTTP SUs in the future, giving a different > port to each of them can't be the solution, either. > > QUESTION: Is there another way to make sure that they end up in the same > component? > > About my environment: it is pretty standard*****). > > Any help on the issue (related to the other one just posted, as well) > would be highly appreciated. > > Thanks in advance, > Ciao, > Philipp > > *) > wsn-http-binding > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns:http="http://servicemix.apache.org/http/1.0"; > xmlns:mag="http://mag.icing.eu/notification/1.0"; > > xmlns:csapi="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/noti > fication/v2_0/service" > xmlns:pub="http://iisys.icing.eu/publisher/1.0"; > > xmlns:impl="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notif > ication/v2_0/service"> > <classpath> > <location>.</location> > </classpath> > > <http:endpoint service="impl:IMMessageNotificationService" > endpoint="IMMessageNotification" role="consumer" > > locationURI="http://0.0.0.0:8192/IMMessageNotificationService/"; > soap="true" > wsdlResource="classpath:IMMessageNotification.wsdl" > targetService="pub:IMMessagePublisher" > targetEndpoint="ep" /> > </beans> > > **) > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns:http="http://servicemix.apache.org/http/1.0"; > xmlns:mag="http://mag.icing.eu/notification/1.0"; > > xmlns:csapi="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/noti > fication/v2_0/service" > xmlns:pub="http://iisys.icing.eu/publisher/1.0"; > > xmlns:impl="http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notif > ication/v2_0/service"> > <classpath> > <location>.</location> > </classpath> > > <http:endpoint service="impl:IMMessageNotificationService" > endpoint="IMMessageNotification" role="consumer" > > locationURI="http://0.0.0.0:8192/IMMessageNotificationService/"; > soap="true" > wsdlResource="classpath:IMMessageNotification.wsdl" > targetService="pub:IMMessagePublisher" > targetEndpoint="ep" /> > </beans> > > ***) > </task-status-msg> > <exception-info> > <nesting-level>1</nesting-level> > <msg-loc-info> > <loc-token/> > <loc-message>Address already in > use: bind</loc-message> > > <stack-trace><![CDATA[java.net.BindException: Address already in use: > bind > at sun.nio.ch.Net.bind(Native Method) > at > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119 > ) > at > sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) > at > org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector > .java:152) > at > org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:313) > at > org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnec > tor.java:124) > at > org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) > at org.mortbay.jetty.Server.doStart(Server.java:217) > at > org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38) > at > org.apache.servicemix.http.jetty.JettyContextManager.createServer(JettyC > ontextManager.java:342) > at > org.apache.servicemix.http.jetty.JettyContextManager.createContext(Jetty > ContextManager.java:143) > at > org.apache.servicemix.http.processors.ConsumerProcessor.start(ConsumerPr > ocessor.java:111) > at > org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:348) > at > org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:55) > at > org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUni > tManager.java:151) > at > org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUn > itLifeCycle.java:103) > at > org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Servi > ceAssemblyLifeCycle.java:130) > at > org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentSe > rvice.java:374) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive( > AutoDeploymentService.java:337) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirecto > ry(AutoDeploymentService.java:646) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(Aut > oDeploymentService.java:62) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDepl > oymentService.java:609) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > ]]></stack-trace> > </msg-loc-info> > </exception-info> > </task-result-details> > </component-task-result-details> > </component-task-result> > </jbi-task-result> > </jbi-task> > > ****) > http://www.nabble.com/multiple-HTTP-SA-tf3964627s12049.html#a11252096 > http://www.nabble.com/Running-multiple-jsr181-webservices-on-the-same-po > rt-tf2064026s12049.html#a5686205 > > *****) > SM 3.1.1, standard configuration with servicemix.xml-configured > servicemix-wsn2005 as well as several servicemix.xml-configured topic > publishers. > > This e-mail and any attachments may contain confidential or > privileged information. Any unauthorised copying, use or distribution of > this information is strictly prohibited. This e-mail and any attachments may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
