Hello, I've fixed the exception handling as per mentioned by Azeez, can you please check it now, you should be able to see the full stack trace of the exception.
Cheers, Anjana. On Mon, Nov 9, 2009 at 12:15 AM, Afkham Azeez <[email protected]> wrote: > Exceptions should never be consumed or logged this way. The exception > has to be logged; log.error(msg, e); and then rethrown, if applicable. > > Azeez > > On Sun, Nov 8, 2009 at 12:13 PM, Samisa Abeysinghe <[email protected]> wrote: >> This, I guess, comes form DS. >> I see the following line on DBInOnlyMessageReceiver.java >> log.error("Unexpected Error." + e.getMessage()); >> The error says only $subject, more more info. >> How can I get to know what is going wrong? I want to know which DS threw >> this and why. I see some data that I want to insert into the DB is there >> irrespective of the error. But I assume that there is some data loss as >> well. >> Thanks, >> Samisa... >> >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "The Open Source SOA Company" >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > > -- > -- > Afkham Azeez > [email protected] > WSO2 Inc. http://wso2.com > Blog: http://afkham.org > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
