My Oracle Support Banner

Premature End Of File When Org.Collaxa.Thirdparty.Apache.Axis.Transport Is Debug (Doc ID 395315.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle(R) BPEL Process Manager 10g - Version and later
Information in this document applies to any platform.


On in Production:
When a BPEL process is invoking a web service, the message is successfully sent. However the BPELConsole reflects that it has not been sent. The logs show a "Premature end of file" error. This problem only occurs when the  org.collaxa.thirdparty.apache.axis.transport logger is set to 'DEBUG'. When it is set to 'INFO', there is no issue.

The issue can be reproduced at will with the following steps:
1. Create two simple async processes and deploy Process1 on Server1, and Process2 on Server2,
where Process1 invokes Process2 and Process2 responds.
2. Set the server logging levels (at BPELAdmin) to 'DEBUG', then execute Process1. You should see
'Premature end of file' in the BPELConsole and in the orabpel.log.
3. Then set the org.collaxa.thirdparty.apache.axis.transport logger to 'INFO' and re-execute the
test. There should be no error then.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.