Null returned from axis client call

[Justin Lawler <jl...@amdocs.com>]

Hi,

We’re seeing an issue when making a call to an axis service, where maybe 50% of the time when calls are made, the call doesn’t go through & just returns null from the service. Strange thing is that we don’t see any exceptions thrown when it returns null. Also, the response time is 1 millisecond when making the call (as opposed to 200 milliseconds on a successful call), so it seems like it’s not even going out to the network at all.

We’re using axis version 1.4 with JDK 1.6 in a linux environment.

We’re using the HTTPSender & we don’t cache the service locator objects, re-creating them for each call (contrary to best practice as documented in many mails/wiki pages/etc – I will be fixing this).

I’ve found a bug logged for this before – bug 2225 – but it was marked as closed & doesn’t seem to have been reproducible.
https://issues.apache.org/jira/browse/AXIS-2225

We’re looking into changing this so we cache the service locators & use CommonsHTTPSender instead, so it’ll use connection pooling as well. However, as we’re seeing this issue in a production environment, and as it’s very hard to reproduce it in a non-live environment, I want to make 100% that this will fix the issue before we ask the customer to apply the patch. I would be much more happy if someone could confirm that this is a known issue before we apply the patch?

Any help much appreciated.

Thanks and regards,
Justin



This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp