Bhavana,
Could you try that again with Apache ServiceMix 4.4.0 - you can get it by downloading the JBI assembly from http://servicemix.apache.org/downloads/servicemix-4.4.0.html ? There was a bug in the NMR in 4.3.0 (cfr. https://issues.apache.org/jira/browse/SMX4NMR-260) that prevented the WSN component from working correctly and we also fixed a few more issues in both the WSN and HTTP components in this latest release. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Mon, Jan 9, 2012 at 7:48 PM, bhawnav <[email protected]> wrote: > Hi JB, > We are using servicemix-wsn component which is a JBI component in turn > available with servicemix. > We have been using since servicemix 3.2.1 onwards and upgraded recently to > servicemix 4.3.0. > > FYI following WARN message that we were getting earlier on DestroyPullPoint > call has been resolved. > > ....... > ....... > [2012-01-08 18:45:38,056] | INFO | > > pool-component.servicemix-wsn2005.consumer-thread-8 | > > nagementEndpointRegistry | ent.ManagementEndpointRegistry 142 | Unr > > egistering endpoint: > > org.apache.servicemix.nmr.core.InternalEndpointWrapper@a26a8210 with > > properties {ENDPOINT_NAME=ID10232165190134bcaf31b210, INTERFACE_NAME > > ={http://docs.oasis-open.org/wsn/bw-2}PullPoint, jbi.internal=true, > > NAME={ > http://servicemix.org/wsnotification}PullPoint:ID10232165190134bcaf31b210, > > objectCla > > ss=[Ljava.lang.String;@72b784, service.id=261, > > SERVICE_NAME={http://servicemix.org/wsnotification}PullPoint, > > WSDL_URL=document:6} > > *[2012-01-08 18:45:38,082] | WARN | 6651905@qtp-14895952-0 | NMR > > | ervicemix.nmr.core.ChannelImpl 293 | Error processing exchange [ > > id: 2fb56260-1c2d-4a89-a3a5-fcf837ba67f0 > > mep: InOut > > status: Done > > role: Consumer > > target: > > PropertyMatchingReference[{ENDPOINT_NAME=ID10232165190134bcaf31b210, > > SERVICE_NAME={http://servicemix.org/wsnotification}PullPoint}] > > operation: {http://docs.oasis-open.org/wsn/bw-2}DestroyPullPoint > > properties: [ > > javax.jbi.servicedesc.ServiceEndpoint = > > org.apache.servicemix.jbi.runtime.impl.EndpointImpl@1c2a7f5 > > org.apache.servicemix.senderEndpoint = > > {http://servicemix.org/wsnotification}NotificationBroker:Broker > > javax.jbi.messaging.MessageExchange = > > org.apache.servicemix.jbi.runtime.impl.InOutImpl@1ae9e9b > > javax.jbi.messaging.sendSync =<null> > > javax.jbi.InterfaceName =<null> > > javax.jbi.transaction.jta =<null> > > javax.jbi.ServiceEndpoint = > > org.apache.servicemix.jbi.runtime.impl.ServiceEndpointImpl@12ed60d > > org.apache.servicemix.correlationId = > > 2fb56260-1c2d-4a89-a3a5-fcf837ba67f0 > > javax.jbi.ServiceName =<null> > > ] > > ]*...... > ...... > > > Earlier we were sending request to https://IPADDRESS:8192/Broker. Now we > are > sending it to https://IPADDRESS:8192/CreatePullPoint and don;t see any > error. > In earlier case as well, Servicemix was not returning soap fault to client > but there was WARN message indicating that pull point destory request is > not > processed. > > But we are still facing HTTP request timeout problem after some time and > client fails to create pull point successfully. > > Regards, > Bhavana > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/WSN-pull-point-destroy-not-working-tp5130955p5132095.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
