ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srijith Kochunni (JIRA)" <>
Subject [jira] Created: (AXIS2-4809) NullPointerException in internalSerializeAndConsume
Date Thu, 02 Sep 2010 06:34:53 GMT
NullPointerException in internalSerializeAndConsume

                 Key: AXIS2-4809
             Project: Axis2
          Issue Type: Bug
          Components: om
    Affects Versions: 1.4
         Environment: A centralized server hosting the web -service, with multiple clients
consuming the same. JAVA 1.6 runtime.
            Reporter: Srijith Kochunni
            Priority: Critical

We invoke one of our our web services using Axis2, without any databinding, because the response
payload might be too huge. This is how we invoke the same.

			clientOptions = new Options();
	        	clientOptions = setReuseHTTPClient(clientOptions);

			EndpointReference targetEPR = new EndpointReference(endpointURI);

			setHTTPKeepAlive(clientOptions, keepAlive);
			ServiceClient svcClient = new ServiceClient();

			result = svcClient.sendReceive(requestOmElement);

The request OM Element is derived from the Adb generated source code, from the WSDL. It was
working correctly for quite some time, but recently randomly it is seen that we get this following

        at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(
        at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
        at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(
        at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(
        at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(
        at org.apache.commons.httpclient.HttpMethodBase.writeRequest(
        at org.apache.commons.httpclient.HttpMethodBase.execute(
        at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(
        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(
        at org.apache.commons.httpclient.HttpClient.executeMethod(
        at org.apache.commons.httpclient.HttpClient.executeMethod(
        at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(
        at org.apache.axis2.transport.http.HTTPSender.sendViaPost(
        at org.apache.axis2.transport.http.HTTPSender.send(
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
        at org.apache.axis2.engine.AxisEngine.send(
        at org.apache.axis2.description.OutInAxisOperationClient.send(
       at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
        at org.apache.axis2.client.OperationClient.execute(
        at org.apache.axis2.client.ServiceClient.sendReceive(
        at org.apache.axis2.client.ServiceClient.sendReceive(

Following this we looked into the Axiom sources as well, and see that in OMSourcedElementImpl,
the dataSource is becoming null for some reason. We are creating a new datasource and in our
auto-generated code, we could see that the data Source is set in the request OMElement

public getOMElement (
               final javax.xml.namespace.QName parentQName,
               final factory) throws org.apache.axis2.databinding.ADBException{

       dataSource =
                       new org.apache.axis2.databinding.ADBDataSource(this,MY_QNAME){

                 public void serialize(org.apache.axis2.databinding.utils.writer.MTOMAwareXMLStreamWriter
xmlWriter) throws {
               return new

       This issue has become very critical for us and any help / ideas / patches would be
much appreciated. We had posted the same on Axis-user mailing list. There have been no responses
so far. We are willing to provide any further information required.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message