I tried the below work around but its not passing.
I mean if (message.containsKey("logging was done")) is false when it enters
next time.
On Wed, Oct 28, 2009 at 4:03 PM, Daniel Kulp <[email protected]> wrote:
> On Wed October 28 2009 3:47:07 pm deepika vadapalli wrote:
> > No.the request is huge but the resposne is just confirmation number.
> > I get the resposne, log it once and then I get Null pointer Exception.
> >
> > This happens in a composite.
> > I do not know how to provide a test case.
>
> Without a testcase that I can run, I really don't think there is anything I
> can do to fix it. The best I can suggest is a workaround for you.
>
> In your loggers handleMessage, do something like:
> if (message.containsKey("logging was done")) {
> return;
> }
> message.put("logging was done", Boolean.TRUE);
>
>
> That should prevent the second logging from triggering.
>
> I'd really like to know why it's even occurring. No idea on that and
> without
> a test case, not much I can do.
>
> Dan
>
>
>
> >
> >
> >
> > Thanks,
> > Laxmi
> >
> > On Wed, Oct 28, 2009 at 3:36 PM, Daniel Kulp <[email protected]> wrote:
> > > Without a reproducible test case, I'm not sure if there is anything I'm
> > > going
> > > to be able to do.
> > >
> > > One thought: is the message coming back a fault? (hard to imagine a
> > > fault
> > > that big, but I suppose it's possible)
> > >
> > > Dan
>
> --
> Daniel Kulp
> [email protected]
> http://www.dankulp.com/blog
>
