SOAP Provider throws Server returned HTTP response code: 500 for URL XYZ - 500 Error in WSDL

Yogeshwar.Kabra · January 8, 2024, 3:29pm

Hi Team,

On the Production environment, SOAP Provider throws Server returned HTTP response code: 500 for URL XYZ, once you open the Web Service Descriptor and navigate to the WSDL section, getting a HTTP 500 error.

Mostly all the SOAP Provider WSDLs throw 500 HTTP errors and all the SOAP consumer WSDLs are working fine.

We tried to simulate the issue from SOAP UI and got the same 500 HTTP error, if we debug the flow service directly using the required inputs, the service works fine.

We moved some other integrations to our existing integration server (v10.3 to 9.9) and after that, it has not worked, but during this migration, this WSDL and process were not changed or impacted.

Also whenever we create a new WSDL on the default folder, first it will not allow you to create and once you refresh the folder/server you can see the WSDL is created and then will get the same 500 error.
if you try to delete WSDLs it’s not allowing us to delete from the default folder.

I know some workarounds but want to know if this can be fixed as mostly many SOAP providers’ WSDLs are not working so Could you please let me know how we can resolve this issue?

Note: Servers are running in cluster environment (2 nodes), below are the IS details:

wM Version - 9.9.0.0
Current IS Fixes:
IS_9.9_Core_Fix6
IS_9.9_SPM_Fix1
IS_9.9_SPM_Fix2

Java Version - 1.8.0_101 (52.0)

SOAP WSDL Binder Properties:

SOAP WSDL Operations Property:

WSDL Error:

we can also see below error on IS:

Getting below errors on IS Server:

com.softwareag.wsstack.deployer.API.exceptions.DynamicDeployerException: Axis configuration is not available. DeployerConfigurationContext is not initialized explicitly, no default configuration context exists and no valid MessageContext is present.
Caused by: com.softwareag.wsstack.deployer.API.exceptions.DynamicDeployerException: Axis configuration is not available. DeployerConfigurationContext is not initialized explicitly, no default configuration context exists and no valid MessageContext is present.

java.lang.NullPointerException: null
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at com.wm.app.b2b.server.wss.HTTPTransportListener.process(HTTPTransportListener.java:133)
at com.softwareag.pg.axis2.transports.PGHTTPTransportListener.process(PGHTTPTransportListener.java:85)
at com.wm.app.b2b.server.HTTPRootWebServicesHandler.process(HTTPRootWebServicesHandler.java:49)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:170)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:364)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:745)

Yogeshwar.Kabra · January 9, 2024, 6:00am

Hi Team, Could you please help me to resolve the above issue? Your quick turnaround is highly appreciated. Thanks

Arpitha_Bhat · January 10, 2024, 3:34am

Hi Yogeshwar, when you say - “We moved some other integrations to our existing integration server (v10.3 to 9.9) and after that, it has not worked, but during this migration, this WSDL and process were not changed or impacted”, have you moved your integrations from IS 10.3v to 9.9v? In which case it is possible that some functionality will not work.
Also, from the error, it looks like the axis2.xml is not available during runtime processing.

Yogeshwar.Kabra · January 10, 2024, 6:47am

@Arpitha_Bhat, @abhat - Thanks for the reply. Yes, we moved some of the integrations from IS 10.3v to 9.9v, but during this migration the WSDL which is failing we didn’t touch and ideally migration will not impact this WSDL, Both are on completely different packages.

How to run axis2.xml file during runtime, can you please suggest?

Below are a couple of observations on the current issue:

We have a PROD environment in a cluster environment (2 nodes), so on the 01 node all WSDL (Provide/Consumer) works fine but on node 02 most of the SOAP Providers are not working.

Note: On the 02 node some SOAP providers’ WSDLs are working and most of them are not, All Consumers WSDLs works fine on 02 node.

When we try to create a new Web Service Descriptor → select the existing IS service and hit next and try to click on the finish button, Web Service Descriptor window/page is still open and unable to proceed further, but once you cancel the process (getting the below error) and referesh the package/server will see like Web Service Descriptor is created.

After creating the Web Service Descriptor, once you open and navigate Operation to WSDL section get error as - Server returned HTTP response code: 500 for URL XYZ . we can save the flow service changes but not the Web Service Descriptor on 02 node.

Even if we make any changes to the existing Web Service Descriptor or newly created - Changes are not saving to Web Service Descriptor, getting below error.

com.softwareag.wsstack.deployer.API.exceptions.DynamicDeployerException: Axis configuration is not available. DeployerConfigurationContext is not initialized explicitly, no default configuration context exists and no valid MessageContext is present.
Caused by: com.softwareag.wsstack.deployer.API.exceptions.DynamicDeployerException: Axis configuration is not available. DeployerConfigurationContext is not initialized explicitly, no default configuration context exists and no valid MessageContext is present.

On existing/new Web Service Descriptor, if you navigate Operation to WSDL section get an error as

java.lang.NullPointerException: null
at org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
at org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
at com.wm.app.b2b.server.wss.HTTPTransportListener.process(HTTPTransportListener.java:133)
at com.softwareag.pg.axis2.transports.PGHTTPTransportListener.process(PGHTTPTransportListener.java:85)
at com.wm.app.b2b.server.HTTPRootWebServicesHandler.process(HTTPRootWebServicesHandler.java:49)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:170)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:364)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:745)

Looks like there some issue is with Web Service Descriptor itself as on the 02 node it’s not allowing us to make the changes and WSDL (xml file) also not generating.

Is there a way to reset the configuration for Web Service Descriptor or how to resolve this specific issue?

Arpitha_Bhat · January 10, 2024, 9:55am

You may try using the “Refresh Web Service Descriptor” option. In your case, there might not be any problem with the WSD/WSDL itself, just that the deployment has not happened correctly on node2.

Yogeshwar.Kabra · January 10, 2024, 10:08am

The “Refresh Web Service Descriptor” option is disabled for me.

I think refresh option will be available only when we create the Web Service Descriptor using File/URL. When we create using the Existing IS service I think the referesh option is disabled.

Will the “Refresh Web Service Descriptor” option should be enabled on both conditions?

Looks like there some issue is with Web Service Descriptor itself as on the 02 node, SOAP web service descriptor changes are not saving on node 02 and we are getting the above axis configuration error.

I created a test Web Service Descriptor using the File/URL and the refresh button was enabled but when I tried to refresh the WSDL without changing the source URI, refresh failed with the below error.

Refresh Error:
wm.server.ws:refreshWSD =
java.lang.NullPointerException: null
at wm.server.wsd.RefreshNSWSDescriptor.init(RefreshNSWSDescriptor.java:140)
at wm.server.wsd.RefreshNSWSDescriptor.(RefreshNSWSDescriptor.java:89)
at wm.server.ws.refreshWSD(ws.java:7419)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:407)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:650)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:303)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:371)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:549)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:238)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:156)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:170)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:364)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang…