I did debug my app and it is submitting an object that is not null, which is
why this is puzzling.  Initially I thought maybe I was trying to through a
null object in there.  I'll do some poking around and see if I can find
where it might be going haywire.

On 9/20/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>
> The client does not send anything for an unknown reason.
> You can see that because the in message has a null content.
> This is what causes the exception.
> I suggest to remote debug the app to see what happens...
> Just set the environment variable SERVICEMIX_DEBUG to TRUE, launch
> servicemix and debug from eclipse or your favorite ide...
>
> On 9/20/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> > I don't get much more, but here is what I see now:
> >
> > DEBUG - WSNComponent                   - Received exchange: status:
> Active,
> > role: provider
> > DEBUG - WSNComponent                   - Retrieved correlation id: null
> > ERROR - WSNComponent                   - Error processing exchange
> InOnly[
> >   id: ID:10.40.16.154-1152419544a-28:1
> >   status: Active
> >   role: provider
> >   endpoint: Broker
> >   in: null
> > ]
> > java.lang.IllegalArgumentException: source parameter must not be null
> >         at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(
> > AbstractUnmarshallerImpl.java:98)
> >         at org.apache.servicemix.wsn.component.WSNEndpoint.process(
> > WSNEndpoint.java:128)
> >         at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(
> > AsyncBaseLifeCycle.java:538)
> >         at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> > AsyncBaseLifeCycle.java:490)
> >         at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(
> > BaseLifeCycle.java:46)
> >         at
> > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(
> > DeliveryChannelImpl.java:610)
> >         at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
> > AbstractFlow.java:170)
> >         at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(
> > SedaFlow.java:167)
> >         at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(
> > SedaQueue.java:134)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> > ThreadPoolExecutor.java:650)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > ThreadPoolExecutor.java:675)
> >         at java.lang.Thread.run(Thread.java:595)
> > DEBUG - DeliveryChannelImpl            - Send ID:
> 10.40.16.154-1152419544a-28:1
> > in DeliveryChannel{servicemix-wsn2005}
> > DEBUG - SedaFlow                       - Called Flow send
> > DEBUG - SedaQueue                      -
> > [EMAIL PROTECTED] dequeued
> > exchange: I
> > nOnly[
> >   id: ID:10.40.16.154-1152419544a-28:1
> >   status: Error
> >   role: consumer
> >   endpoint: Broker
> >   in: null
> >   error: java.lang.IllegalArgumentException: source parameter must not
> be
> > null
> > ]
> > DEBUG - DeliveryChannelImpl            - Notifying exchange ID:
> > 10.40.16.154-1152419544a-28:1(e99889) in DeliveryChannel{I
> > D:10.40.16.154-1152419544a-0:1} from processInboundSynchronousExchange
> > DEBUG - DeliveryChannelImpl            - Notified: ID:
> > 10.40.16.154-1152419544a-28:1(e99889) in DeliveryChannel{ID:10.40.1
> > 6.154-1152419544a-0:1} from sendSync
> >
> > On 9/20/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > >
> > > It seems that nothing is received by then WS-Notification component.
> > > Can you raise the log level to DEBUG and see what is displayed ?
> > >
> > > On 9/20/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> > > > It's actually the JAXB objects I generated with CXF for my
> webservices.
> > > > Those should be JAXB2 elements.  They are the elements I return from
> my
> > > > webservice to a connected client.
> > > >
> > > > On 9/20/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > What kind of object do you send ? IIRC it has to be a DOM element
> or a
> > > > > JAXB2 pojo so that JAXB2 can marshal it to xml.
> > > > >
> > > > > On 9/20/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> > > > > > I'm having some trouble when attempting to publish a
> > > notification.  When
> > > > > I
> > > > > > do, I get this error:
> > > > > >
> > > > > > ERROR - WSNComponent                   - Error processing
> exchange
> > > > > InOnly[
> > > > > >   id: ID:192.168.1.2-11520deb240-28:0
> > > > > >   status: Active
> > > > > >   role: provider
> > > > > >   endpoint: Broker
> > > > > >   in: null
> > > > > > ]
> > > > > > java.lang.IllegalArgumentException: source parameter must not be
> > > null
> > > > > >         at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal
> > > (
> > > > > > AbstractUnmarshallerImpl.java:98)
> > > > > >         at
> org.apache.servicemix.wsn.component.WSNEndpoint.process(
> > > > > > WSNEndpoint.java:128)
> > > > > >         at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess
> > > (
> > > > > > AsyncBaseLifeCycle.java:538)
> > > > > >         at
> > > > > org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(
> > > > > > AsyncBaseLifeCycle.java:490)
> > > > > >
> > > > > > My code that causes this is:
> > > > > >
> > > > > > private void sendNotification(Object notification) {
> > > > > >     try {
> > > > > >       if(wsnBroker == null)
> > > > > >         createWsnBroker();
> > > > > >       wsnBroker.notify("notificationTopic", notification);
> > > > > >     } catch (Exception e) {
> > > > > >       e.printStackTrace();
> > > > > >     }
> > > > > >   }
> > > > > >
> > > > > >
> > > > > > I've looked and my notification object isn't null, is there
> > > something
> > > > > called
> > > > > > source somewhere that I need to set?
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Cheers,
> > > > > Guillaume Nodet
> > > > > ------------------------
> > > > > Blog: http://gnodet.blogspot.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > > ------------------------
> > > Blog: http://gnodet.blogspot.com/
> > >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>

Reply via email to