Two soap message entries in log file

I am calling a web service.
And when I checked the log file, I found soap messages (in XML format), two times like below:
_________________________________________________________________________________

[2012-01-06 09:26:02 , 290] (Call.java:2762) DEBUG - <SOAP Message Request in XML format>

_________________________________________________________________________________

[2012-01-06 09:26:02 , 864] (HTTPSender.java:519) DEBUG - POST /beta/Service HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: <hostname>
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "serviceName"
Content-Length: 527

<SOAP Message Request in XML format>
_________________________________________________________________________________

Above are the appearance of the SOAP Message I was able to find in the log file. Both were exactly same.
Furthermore, I found only one response message in the log file.

I am wondering if the service is being called two times!

Please help!

It's hard to tell what caused this. There can be many reasons, how the logging is done in the application, what kind of logging is done by the libraries used etc... You may need to give more details (TellTheDetails).

And welcome to the CodeRanch

Logging was done in the most basic way:

With due respect, I think this has nothing to do with the logging.

I wanted to ask, it seems, from log files, that the service is being called two times.
In other way, what happens exactly when a service is being called?
Is it like: The elements in the XSD related to the WSDL file are at first parsed, then the request XML is formed, and then that XML is sent over HTTP?
I am not aware of the details.
It would be very helpful if I get to know the exact mechanism.

And thanks for the welcome :-)

For a high-level view I suggest you read the WS Architecture. For your case if you provide details of the system with it's boundaries, components etc... then it might be helpful to identify the cause.

But as a developer you don't need to know much about the internals of the libraries used. If you still need to know then you might first try with enhanced debugging configuration to see what is being used and where etc... (of course if the libraries has those debug information).