Hello, Thanks for the info, the issue is now fixed, it just needed a simple null check, since when handling in-only messages, there's no result, so the xmlWriter is null then. As for the service invocation, there wasn't any data loss happening, just that the exception occurring because of the null object and the message being printed.
Regards, Anjana. On Mon, Nov 9, 2009 at 9:46 AM, Samisa Abeysinghe <[email protected]> wrote: > And the line is > xmlWriter.flush(); > Looks like xmlWriter null?? > Samisa... > > On Mon, Nov 9, 2009 at 9:44 AM, Samisa Abeysinghe <[email protected]> wrote: >> >> Here is the exception: >> java.lang.NullPointerException >> at >> org.wso2.carbon.dataservices.dispatch.DSOMDataSource.serialize(DSOMDataSource.java:90) >> at >> org.wso2.carbon.dataservices.DBUtils.doNormalRequest(DBUtils.java:179) >> at org.wso2.carbon.dataservices.DBUtils.xinvoke(DBUtils.java:125) >> at >> org.wso2.carbon.dataservices.DBInOnlyMessageReceiver.invokeBusinessLogic(DBInOnlyMessageReceiver.java:44) >> at >> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178) >> at >> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167) >> at >> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >> at >> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >> at >> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) >> at >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) >> at >> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) >> at >> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) >> at >> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) >> at >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) >> at java.lang.Thread.run(Thread.java:619) >> >> On Mon, Nov 9, 2009 at 8:11 AM, Anjana Fernando <[email protected]> wrote: >>> >>> 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 >> >> >> >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "The Open Source SOA Company" > > > > -- > 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 > > _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
