You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "João Portela (JIRA)" <ax...@ws.apache.org> on 2005/07/28 15:27:18 UTC
[jira] Created: (AXIS-2150) Error calling web service after a re-deploy
Error calling web service after a re-deploy
-------------------------------------------
Key: AXIS-2150
URL: http://issues.apache.org/jira/browse/AXIS-2150
Project: Apache Axis
Type: Bug
Versions: 1.2.1
Environment: Java sdk1.4.2_06
JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0
Reporter: João Portela
After a redeploy of an application (that called a web service), when I try to call a web service the following error occurs:
“Unable to locate a valid EngineConfigurationFactory”
java.lang.NullPointerException
at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812)
at org.apache.axis.client.Service.getAxisClient(Service.java:103)
at org.apache.axis.client.Service.(Service.java:112)
at myapp.WebService1Soap_BindingStub.(Unknown Source)
...
Notes:
- I have an axis configuration file in my ear/war application file.
- It seems that after the redeploy it tries to use previous (load) configurations but due to the redeploy, the configuration no longer exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2150) Error calling web service after a
re-deploy
Posted by "Nils Hammar (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12368300 ]
Nils Hammar commented on AXIS-2150:
-----------------------------------
I have found out a workaround and that is to have a class load the Axis functionality in a separate jar-file that resides in common/endorsed. The trick here is to let that class make a permanent reference to the Axis class and then let the web service application use this class as an intermediate.
It's still stupid to need this hack, but it works.
Example workaround code snippet:
----
public class Comm
{
...
// Static makes a permanent reference and it is therefore not unloaded
// Slight memory leak - but only once.
private static ServiceLocator locator = null;
...
public void somemethod()
{
if (locator == null)
{
// It works the first time, and we only have to do this once.
locator = new ServiceLocator();
}
...
// This can be called multiple times.
service = locator.getfastscoringSoap(new URL(path));
...
}
}
----
> Error calling web service after a re-deploy
> -------------------------------------------
>
> Key: AXIS-2150
> URL: http://issues.apache.org/jira/browse/AXIS-2150
> Project: Apache Axis
> Type: Bug
> Versions: 1.2.1
> Environment: Java sdk1.4.2_06
> JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0
> Reporter: João Portela
>
> After a redeploy of an application (that called a web service), when I try to call a web service the following error occurs:
> ?Unable to locate a valid EngineConfigurationFactory?
> java.lang.NullPointerException
> at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812)
> at org.apache.axis.client.Service.getAxisClient(Service.java:103)
> at org.apache.axis.client.Service.(Service.java:112)
> at myapp.WebService1Soap_BindingStub.(Unknown Source)
> ...
> Notes:
> - I have an axis configuration file in my ear/war application file.
> - It seems that after the redeploy it tries to use previous (load) configurations but due to the redeploy, the configuration no longer exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2150) Error calling web service after a
re-deploy
Posted by "Bernier (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12368255 ]
Bernier commented on AXIS-2150:
-------------------------------
Hi,
I'm working on a Portal project with some webservices integrations on Sun One Web servers and App servers and I also face this issue.
I confirm that Axis 1.3 don't solve the issue.
I'm planning to find a solution for this, and for me there are only three ways :
* having a patch from axis. But When ? will this issue taken in account for the next Axis version ?
* finding a solution to make the Axis librairys work ....
* going on Sun Webservices librairys but this will be painfull
Can you tell me what I can do, do you have a solution to make this work or should I wait for a patch ?
Thank you for your answers,
> Error calling web service after a re-deploy
> -------------------------------------------
>
> Key: AXIS-2150
> URL: http://issues.apache.org/jira/browse/AXIS-2150
> Project: Apache Axis
> Type: Bug
> Versions: 1.2.1
> Environment: Java sdk1.4.2_06
> JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0
> Reporter: João Portela
>
> After a redeploy of an application (that called a web service), when I try to call a web service the following error occurs:
> ?Unable to locate a valid EngineConfigurationFactory?
> java.lang.NullPointerException
> at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812)
> at org.apache.axis.client.Service.getAxisClient(Service.java:103)
> at org.apache.axis.client.Service.(Service.java:112)
> at myapp.WebService1Soap_BindingStub.(Unknown Source)
> ...
> Notes:
> - I have an axis configuration file in my ear/war application file.
> - It seems that after the redeploy it tries to use previous (load) configurations but due to the redeploy, the configuration no longer exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-2150) Error calling web service after a
re-deploy
Posted by "Nils Hammar (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12363959 ]
Nils Hammar commented on AXIS-2150:
-----------------------------------
The problem is still in Axis 1.3, and a study of the source code reveals the following:
In Service.java, the problem is likely caused by EngineConfigurationFactoryFinder.newFactory() returning 'null', which ends up in EngineConfigurationFactoryFinder.newFactory(Object), and that method seems to be "incomplete" according to the comments given.
As I see it it may be caused by the line services.nextResourceClass().loadClass(), which seems to be throwing an Exception that in turn isn't handled at all, and the whole catch body is just a comment. The Exception seems to be triggered by trying to load an already loaded class. What's bad is that this condition should have been causing an exception instead of resulting in a returned null pointer with no notification whatsoever.
> Error calling web service after a re-deploy
> -------------------------------------------
>
> Key: AXIS-2150
> URL: http://issues.apache.org/jira/browse/AXIS-2150
> Project: Apache Axis
> Type: Bug
> Versions: 1.2.1
> Environment: Java sdk1.4.2_06
> JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0
> Reporter: João Portela
>
> After a redeploy of an application (that called a web service), when I try to call a web service the following error occurs:
> ?Unable to locate a valid EngineConfigurationFactory?
> java.lang.NullPointerException
> at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812)
> at org.apache.axis.client.Service.getAxisClient(Service.java:103)
> at org.apache.axis.client.Service.(Service.java:112)
> at myapp.WebService1Soap_BindingStub.(Unknown Source)
> ...
> Notes:
> - I have an axis configuration file in my ear/war application file.
> - It seems that after the redeploy it tries to use previous (load) configurations but due to the redeploy, the configuration no longer exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira