You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Chilson <je...@inetco.com> on 2007/03/05 21:31:25 UTC
WS Notification Broker in ServiceMix 3.1 not behaving as I would
expect
Of course, it may be because I'm expecting the wrong thing.
Using the WSN HTTP Binding example (which does not work straight out of the
distribution, as the JNDI.xml file under ServiceMix/Conf is missing the
import security.xml reference), I have a notification broker set up. I can
subscribe to topics fine.
However, if I attempt to register a publisher, I get a null pointer
exception returned. No matter what options I specify in the registration.
If I send notify messages in without registering the publisher first, I get
a "illegal operation status: done" response, and any subscribers will
receive a notification of the message, however the actual message portion of
the notification will be blank.
I've looked through to see if there are any outstanding issues related to
this, or if anyone else has seen this behaviour, but I have seen nothing.
ServiceMix 3.0 behaves the exact same way. I'm using the releases, not
snapshots, and am running under Windows.
Can anyone help or give me some guidance?
Cheers
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9319812
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I
would expect
Posted by Chilson <je...@inetco.com>.
See? I knew it'd be something simple.
Thanks for the help, that's got it going for anonymous. I'll try the
registered publisher again further down the road, this is just fine for now.
gnodet wrote:
>
> If you have turned off soap, you need to make sure the defaultMep
> attriebute
> on your http endpoint is set to InOnly, else an InOut mep will be send
> and cause the exception you have seen.
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9362200
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I would expect
Posted by Guillaume Nodet <gn...@gmail.com>.
If you have turned off soap, you need to make sure the defaultMep attriebute
on your http endpoint is set to InOnly, else an InOut mep will be send
and cause the exception you have seen.
On 3/7/07, Chilson <je...@inetco.com> wrote:
>
>
> I'm using the Wsn-Http-Binding example, unchanged except for turning SOAP
> off.
>
> For the notification message, I'm just trying the one off of the wsn
> servicemix page.
>
> POST /Broker/ HTTP/1.1
> Host: localhost:8192
> Content-Type: text/xml; charset="utf-8"
> Content-Length: 210
>
> <wsnt:Notify
> xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2
> "><wsnt:NotificationMessage><wsnt:Topic>myTopic</wsnt:Topic><wsnt:Message><hello>world</hello></wsnt:Message></wsnt:NotificationMessage></wsnt:Notify>
>
>
>
>
> gnodet wrote:
> >
> >
> > Yeah, you're quite right, the problem comes from a MEP mismatch.
> > I guess that the servicemix-http BC sends an InOut MEP, but the
> operation
> > invoked is an InOnly MEP. This should be checked earlier and reported
> > with
> > a more understandable error (can you raise a JIRA please ?).
> >
> > Not sure how you configured your HTTP endpoint, but the problem may come
> > from the fact that the WSDL is not correctly recognized, so that the
> > informations
> > can not be retrieved. Did you use the one from the example in the
> > distribution ?
> > What request did you send ?
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Architect, LogicBlaze (http://www.logicblaze.com/)
> > Blog: http://gnodet.blogspot.com/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9360759
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I
would expect
Posted by Chilson <je...@inetco.com>.
I'm using the Wsn-Http-Binding example, unchanged except for turning SOAP
off.
For the notification message, I'm just trying the one off of the wsn
servicemix page.
POST /Broker/ HTTP/1.1
Host: localhost:8192
Content-Type: text/xml; charset="utf-8"
Content-Length: 210
<wsnt:Notify
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"><wsnt:NotificationMessage><wsnt:Topic>myTopic</wsnt:Topic><wsnt:Message><hello>world</hello></wsnt:Message></wsnt:NotificationMessage></wsnt:Notify>
gnodet wrote:
>
>
> Yeah, you're quite right, the problem comes from a MEP mismatch.
> I guess that the servicemix-http BC sends an InOut MEP, but the operation
> invoked is an InOnly MEP. This should be checked earlier and reported
> with
> a more understandable error (can you raise a JIRA please ?).
>
> Not sure how you configured your HTTP endpoint, but the problem may come
> from the fact that the WSDL is not correctly recognized, so that the
> informations
> can not be retrieved. Did you use the one from the example in the
> distribution ?
> What request did you send ?
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9360759
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I would expect
Posted by Guillaume Nodet <gn...@gmail.com>.
On 3/7/07, Chilson <je...@inetco.com> wrote:
>
>
> Once I feel like I've actually learned some of this I'll hopefully have
> some
> time and knowledge to donate to the project :)
>
> I would prefer to register the publisher, but I'll get it working
> anonymously first and then reach for the more advanced registration ;)
One step at a time ...
Ok, I can publish anonymously and the subscribed consumers receive the data
> properly, except every time I send in a notify message, I get an "illegal
> exchange status: done" exception. From what I've searched and found, this
> exception occurs when a component is accepting inbound data when it is
> outbound only, or sending data when it is inbound only? Or am I off? At
> any rate, here is a trace stack of it.
Yeah, you're quite right, the problem comes from a MEP mismatch.
I guess that the servicemix-http BC sends an InOut MEP, but the operation
invoked is an InOnly MEP. This should be checked earlier and reported with
a more understandable error (can you raise a JIRA please ?).
Not sure how you configured your HTTP endpoint, but the problem may come
from the fact that the WSDL is not correctly recognized, so that the
informations
can not be retrieved. Did you use the one from the example in the
distribution ?
What request did you send ?
Caused by:java.lang.Exception: javax.jbi.messaging.MessagingException:
> illegal exchange status: done
> at
> org.apache.servicemix.http.processors.ConsumerProcessor.process(
> ConsumerProcessor.java:214)
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
> :71)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
> :123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:269)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
> :333)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
> :270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
> :475)
> Caused by: javax.jbi.messaging.MessagingException: illegal exchange
> status:
> done
> at
> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(
> MessageExchangeImpl.java:583)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(
> DeliveryChannelImpl.java:370)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(
> DeliveryChannelImpl.java:417)
> at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java
> :162)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
> :176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
> :134)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)
>
>
>
> gnodet wrote:
> >
> > This is the only documentation we have :-(
> > But any help to improve it is welcome ...
> >
> > So, back to your point.
> > Registering a publisher is not mandatory, so you can just publish
> > messages to the WS-NotificationBroker and it will use an
> > anonymous publisher if not specified.
> > If you want to register a publisher, the address supplied in
> > the wsa:Address uri must point to a valid JBI endpoint.
> > See http://incubator.apache.org/servicemix/uris.html
> > for some examples of URIs you can use to represent jbi endpoints.
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Architect, LogicBlaze (http://www.logicblaze.com/)
> > Blog: http://gnodet.blogspot.com/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9345481
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I
would expect
Posted by Chilson <je...@inetco.com>.
Once I feel like I've actually learned some of this I'll hopefully have some
time and knowledge to donate to the project :)
I would prefer to register the publisher, but I'll get it working
anonymously first and then reach for the more advanced registration ;)
Ok, I can publish anonymously and the subscribed consumers receive the data
properly, except every time I send in a notify message, I get an "illegal
exchange status: done" exception. From what I've searched and found, this
exception occurs when a component is accepting inbound data when it is
outbound only, or sending data when it is inbound only? Or am I off? At
any rate, here is a trace stack of it.
Caused by:java.lang.Exception: javax.jbi.messaging.MessagingException:
illegal exchange status: done
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:214)
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: javax.jbi.messaging.MessagingException: illegal exchange status:
done
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(MessageExchangeImpl.java:583)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:370)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:417)
at
org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:162)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
gnodet wrote:
>
> This is the only documentation we have :-(
> But any help to improve it is welcome ...
>
> So, back to your point.
> Registering a publisher is not mandatory, so you can just publish
> messages to the WS-NotificationBroker and it will use an
> anonymous publisher if not specified.
> If you want to register a publisher, the address supplied in
> the wsa:Address uri must point to a valid JBI endpoint.
> See http://incubator.apache.org/servicemix/uris.html
> for some examples of URIs you can use to represent jbi endpoints.
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9345481
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I would expect
Posted by Guillaume Nodet <gn...@gmail.com>.
This is the only documentation we have :-(
But any help to improve it is welcome ...
So, back to your point.
Registering a publisher is not mandatory, so you can just publish
messages to the WS-NotificationBroker and it will use an
anonymous publisher if not specified.
If you want to register a publisher, the address supplied in
the wsa:Address uri must point to a valid JBI endpoint.
See http://incubator.apache.org/servicemix/uris.html
for some examples of URIs you can use to represent jbi endpoints.
On 3/7/07, Chilson <je...@inetco.com> wrote:
>
>
> I just entered a JIRA.
>
> Yes, turns out I was supplying a totally invalid publisherreference. I
> corrected it to use a wsa:Address with the URI of my publisher
> application,
> but now I'm getting an error about it not being able to locate the
> consumer
> reference endpoint.
>
> org.apache.servicemix.wsn.jaxws.PublisherRegistrationFailedFault: Unable
> to
> resolve consumer reference endpoint
>
> It says consumer reference, but as it's in the validatePublisher function
> I
> would think that to be a typo, and so I'm interpreting it to mean
> publisher
> reference endpoint.
>
> This sounds like it's just a configuration issue or misunderstanding of
> the
> reference endpoint on my behalf, but any help would be appreciated. Do I
> need to configure this endpoint in ServiceMix? I wouldn't think so, but I
> can't really find good documentation describing what I need to do for
> this.
>
> Is there some more in depth WSN documentation for ServiceMix, besides the
> one page on the main site?
>
>
> gnodet wrote:
> >
> > When registering a publisher, the WS-Notification SE
> > expects a valid PublisherReference element to be in the
> > publisher registration request. Otherwise it should return
> > a fault at that time. But there may be some problems when
> > this is not done, as the publisher seems to be registered
> > nonetheless and the fault is thrown after that.
> > Could you raise a JIRA and copy your stack trace there please ?
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Architect, LogicBlaze (http://www.logicblaze.com/)
> > Blog: http://gnodet.blogspot.com/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9343721
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I
would expect
Posted by Chilson <je...@inetco.com>.
I just entered a JIRA.
Yes, turns out I was supplying a totally invalid publisherreference. I
corrected it to use a wsa:Address with the URI of my publisher application,
but now I'm getting an error about it not being able to locate the consumer
reference endpoint.
org.apache.servicemix.wsn.jaxws.PublisherRegistrationFailedFault: Unable to
resolve consumer reference endpoint
It says consumer reference, but as it's in the validatePublisher function I
would think that to be a typo, and so I'm interpreting it to mean publisher
reference endpoint.
This sounds like it's just a configuration issue or misunderstanding of the
reference endpoint on my behalf, but any help would be appreciated. Do I
need to configure this endpoint in ServiceMix? I wouldn't think so, but I
can't really find good documentation describing what I need to do for this.
Is there some more in depth WSN documentation for ServiceMix, besides the
one page on the main site?
gnodet wrote:
>
> When registering a publisher, the WS-Notification SE
> expects a valid PublisherReference element to be in the
> publisher registration request. Otherwise it should return
> a fault at that time. But there may be some problems when
> this is not done, as the publisher seems to be registered
> nonetheless and the fault is thrown after that.
> Could you raise a JIRA and copy your stack trace there please ?
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9343721
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I would expect
Posted by Guillaume Nodet <gn...@gmail.com>.
When registering a publisher, the WS-Notification SE
expects a valid PublisherReference element to be in the
publisher registration request. Otherwise it should return
a fault at that time. But there may be some problems when
this is not done, as the publisher seems to be registered
nonetheless and the fault is thrown after that.
Could you raise a JIRA and copy your stack trace there please ?
On 3/5/07, Chilson <je...@inetco.com> wrote:
>
>
> Thanks for the quick reply.
>
> Here's the output. Is there anything else that could be helpful to post
> up?
>
> [Fatal Error] :-1:-1: Premature end of file.
> ERROR - WSNComponent - Error processing exchange InOut[
> id: ID:MELBA-2288-1173131624682-2:0
> status: Active
> role: provider
> service: {http://servicemix.org/wsnotification}NotificationBroker
> endpoint: Broker
> in: Unable to display: org.xml.sax.SAXParseException: Premature end of
> file.
> ]
> java.lang.NullPointerException
> at
> org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(
> JbiPublisher.java:87)
> at
> org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java
> :90)
> at
>
> org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher
> (AbstractNotificationBroker.java:253)
> at
> org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(
> AbstractNotificationBroker.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> :39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java
> :137)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
> :176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
> :134)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)
> WARN - jetty - EXCEPTION
> javax.servlet.ServletException: Failed to process request:
> java.lang.Exception: java.lang.NullPointerException
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
> :79)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
> :123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:269)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
> :333)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
> :270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
> :475)
> WARN - jetty - Nested in
> javax.servlet.ServletException: Failed to process request:
> java.lang.Exception: java.lang.NullPointerException:
> java.lang.Exception: java.lang.NullPointerException
> at
> org.apache.servicemix.http.processors.ConsumerProcessor.process(
> ConsumerProcessor.java:214)
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
> :71)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
> :123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:269)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
> :333)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
> :270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
> :475)
> Caused by: java.lang.NullPointerException
> at
> org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(
> JbiPublisher.java:87)
> at
> org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java
> :90)
> at
>
> org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher
> (AbstractNotificationBroker.java:253)
> at
> org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(
> AbstractNotificationBroker.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> :39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java
> :137)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
> :176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
> :134)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)
> WARN - jetty - /Broker/:
> java.lang.Exception: java.lang.NullPointerException
> at
> org.apache.servicemix.http.processors.ConsumerProcessor.process(
> ConsumerProcessor.java:214)
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
> :71)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
> :123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:269)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
> :333)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
> :270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
> :475)
> Caused by: java.lang.NullPointerException
> at
> org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(
> JbiPublisher.java:87)
> at
> org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java
> :90)
> at
>
> org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher
> (AbstractNotificationBroker.java:253)
> at
> org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(
> AbstractNotificationBroker.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> :39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java
> :137)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
> :176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
> :134)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)
> WARN - jetty - /Broker/
> java.lang.Exception: java.lang.NullPointerException
> at
> org.apache.servicemix.http.processors.ConsumerProcessor.process(
> ConsumerProcessor.java:214)
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java
> :71)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> ContextHandlerCollection.java:149)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java
> :123)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> at org.mortbay.jetty.Server.handle(Server.java:269)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java
> :333)
> at
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java
> :270)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java
> :475)
> Caused by: java.lang.NullPointerException
> at
> org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(
> JbiPublisher.java:87)
> at
> org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java
> :90)
> at
>
> org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher
> (AbstractNotificationBroker.java:253)
> at
> org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(
> AbstractNotificationBroker.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> :39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java
> :137)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java
> :176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java
> :134)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:665)
> at
>
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:619)
>
> --
> View this message in context:
> http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9321934
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I
would expect
Posted by Chilson <je...@inetco.com>.
Thanks for the quick reply.
Here's the output. Is there anything else that could be helpful to post up?
[Fatal Error] :-1:-1: Premature end of file.
ERROR - WSNComponent - Error processing exchange InOut[
id: ID:MELBA-2288-1173131624682-2:0
status: Active
role: provider
service: {http://servicemix.org/wsnotification}NotificationBroker
endpoint: Broker
in: Unable to display: org.xml.sax.SAXParseException: Premature end of
file.
]
java.lang.NullPointerException
at
org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(JbiPublisher.java:87)
at
org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java:90)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher(AbstractNotificationBroker.java:253)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(AbstractNotificationBroker.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:137)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
WARN - jetty - EXCEPTION
javax.servlet.ServletException: Failed to process request:
java.lang.Exception: java.lang.NullPointerException
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
WARN - jetty - Nested in
javax.servlet.ServletException: Failed to process request:
java.lang.Exception: java.lang.NullPointerException:
java.lang.Exception: java.lang.NullPointerException
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:214)
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: java.lang.NullPointerException
at
org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(JbiPublisher.java:87)
at
org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java:90)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher(AbstractNotificationBroker.java:253)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(AbstractNotificationBroker.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:137)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
WARN - jetty - /Broker/:
java.lang.Exception: java.lang.NullPointerException
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:214)
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: java.lang.NullPointerException
at
org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(JbiPublisher.java:87)
at
org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java:90)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher(AbstractNotificationBroker.java:253)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(AbstractNotificationBroker.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:137)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
WARN - jetty - /Broker/
java.lang.Exception: java.lang.NullPointerException
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:214)
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:356)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:269)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:333)
at
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: java.lang.NullPointerException
at
org.apache.servicemix.wsn.jbi.JbiPublisher.validatePublisher(JbiPublisher.java:87)
at
org.apache.servicemix.wsn.AbstractPublisher.create(AbstractPublisher.java:90)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.handleRegisterPublisher(AbstractNotificationBroker.java:253)
at
org.apache.servicemix.wsn.AbstractNotificationBroker.registerPublisher(AbstractNotificationBroker.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.servicemix.wsn.component.WSNEndpoint.process(WSNEndpoint.java:137)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:619)
--
View this message in context: http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9321934
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: WS Notification Broker in ServiceMix 3.1 not behaving as I would expect
Posted by Guillaume Nodet <gn...@gmail.com>.
Sounds weird.
Can raise the log level and paste the stack trace (you should see an
exception somewhere) ...
On 3/5/07, Chilson <je...@inetco.com> wrote:
>
>
> Of course, it may be because I'm expecting the wrong thing.
>
> Using the WSN HTTP Binding example (which does not work straight out of
> the
> distribution, as the JNDI.xml file under ServiceMix/Conf is missing the
> import security.xml reference), I have a notification broker set up. I
> can
> subscribe to topics fine.
>
> However, if I attempt to register a publisher, I get a null pointer
> exception returned. No matter what options I specify in the registration.
>
> If I send notify messages in without registering the publisher first, I
> get
> a "illegal operation status: done" response, and any subscribers will
> receive a notification of the message, however the actual message portion
> of
> the notification will be blank.
>
> I've looked through to see if there are any outstanding issues related to
> this, or if anyone else has seen this behaviour, but I have seen nothing.
> ServiceMix 3.0 behaves the exact same way. I'm using the releases, not
> snapshots, and am running under Windows.
>
> Can anyone help or give me some guidance?
>
> Cheers
> --
> View this message in context:
> http://www.nabble.com/WS-Notification-Broker-in-ServiceMix-3.1-not-behaving-as-I-would-expect-tf3351459s12049.html#a9319812
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/