Hi,
I am trying to use the ws-notification service in servicemix 3.2.3 with
axis2 1.4.1. I was able to configure an http binding similar to the
example, and test it with the example test client (slightly modified) over
the network. Here's the http://www.nabble.com/file/p24923399/xbean.xml
xbean.xml file. I'm using XP on all machines.
Using axis2 I generated a client from the wsdl's servicemix exposed. I am
able to create a pull point and subscribe using that pull point without any
issues.
When I send a notification message I get this warning message:
WARN - DeliveryChannelImpl - Error calling listener: null
java.lang.NullPointerException
at
org.apache.servicemix.jbi.monitoring.StatisticsService.onExchangeAcce
pted(StatisticsService.java:307)
at
org.apache.servicemix.jbi.monitoring.StatisticsService$3.exchangeAcce
pted(StatisticsService.java:186)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
d(DeliveryChannelImpl.java:608)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
w.java:172)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
ava:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav
a:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:651)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:676)
at java.lang.Thread.run(Thread.java:595)
Then later this error show up:
ERROR - HttpComponent - Error processing exchange InOnly[
id: ID:134.253.165.148-1230a3fb7ba-19:22
status: Active
role: provider
endpoint:
http://servicemix.org/wsnotification/PullPoint/ID-stacy-4096-1250007
424663-8-5
in: <?xml version="1.0" encoding="UTF-8"?><ns2:Notify
xmlns:ns2="http://docs.o
asis-open.org/wsn/b-2" xmlns="http://www.w3.org/2005/08/addressing";
xmlns:ns3="h
ttp://docs.oasis-open.org/wsn/t-1"
xmlns:ns4="http://docs.oasis-open.org/wsrf/bf
-2"><ns2:NotificationMessage><ns2:Topic
Dialect="http://docs.oasis-open.org/wsn/
t-1/TopicExpression/Simple">SAR</ns2:Topic><ns2:Message><ped:SAR
xmlns:ped="http
://www.sandia.gov/ped/services/types">Test</ped:SAR></ns2:Message></ns2:Notifica
tionMessage></ns2:Notify>
]
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:367)
at java.net.Socket.connect(Socket.java:524)
at java.net.Socket.connect(Socket.java:474)
at java.net.Socket.<init>(Socket.java:371)
at java.net.Socket.<init>(Socket.java:244)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.c
reateSocket(DefaultProtocolSocketFactory.java:79)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.c
reateSocket(DefaultProtocolSocketFactory.java:121)
at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java
:706)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$Http
ConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Htt
pMethodDirector.java:386)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMe
thodDirector.java:170)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav
a:396)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav
a:346)
at
org.apache.servicemix.http.processors.ProviderProcessor.process(Provi
derProcessor.java:168)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLi
feCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(Async
BaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLife
Cycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
d(DeliveryChannelImpl.java:620)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
w.java:172)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
ava:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav
a:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:651)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:676)
at java.lang.Thread.run(Thread.java:595)
It looks like the notification service engine is unable to connect to the
created pull point.
I can send a 'get messages request' to the pullpoint and get a
NoCurrentMessageOnTopicFault, so it is up and responding. Everything also
works fine when I used the example test client, which I modified to point
over the network instead of to localhost.
One difference between the test client and axis is the test client has who
(pull point address) to send the notification to. In axis2 the client
subscribes to a topic, though this seems to be working because the
notification service engine tries to send the message to the pull point.
Thanks for any help.
Any ideas would be appreciated.
--
View this message in context:
http://www.nabble.com/PullPoint-Timeout-tp24923399p24923399.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
