-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException while initializing SOAP client #5059
Comments
Hi @peterpz1, Would you be able to reproduce your issue on the latest release 5.2020.7? Could you also provide a sample application to make reproducing for us easier? Thank you, |
We are now preparing installation pack for 5.2020.7 to check if this issue exsists. I don't know if I would be able to prepare app for testing because:
PS: Why you are removing production domain from Community version? Are you trying to force us to migrate to EE version? |
Hi @peterpz1, First, I would like to thank you for raising this issue. To help us find the cause and fix the issue, we need, as you have mentioned, a simple application that reproduces this issue on the latest release of Payara Community Edition. A reproducer should ideally follow the SSCCE rules: http://www.sscce.org/. Without any reproducer, I am afraid we won't be able to investigate this issue further. You can read about the rationale behind removing the Production domain from the Payara Community Edition by Steve Millidge, the founder and Director of Payara on https://groups.google.com/g/payara-forum/c/Uw5eiEFfF0Y/m/ccrqHZVoAgAJ. Many thanks for your understanding. Mero Rai |
@MeroRai
Other threads are OK. I'm looking at StandardContext.getResource(StandardContext.java:7409) and since it looks like that: |
@MeroRai what I did was to catch this NPE and after that try to force the context to be build. I just copied the code from metroglue and executed it mysfelf: After that I'm trying to build the WebService client again - and what is the suprise? There is no NPE... |
Also note that other resource* methods use different approach to get resource:
|
Currently I deployed a workaround for all SOAP clients. Each client is created like that:
|
Hi @peterpz1, You seem to be very familiar with our codebase, is this something you will be interested in creating a PR with a fix? You can read more on contributing to Payara here: https://github.com/payara/Payara/blob/master/.github/CONTRIBUTING.md |
Hi, since we haven’t received a reproducer, we’ll proceed to close this issue. Feel free to re-open it in the future if you are able to provide us with a simple reproducer using the current release of Payara Community Edition at that point in time. |
Description
We have auto generated JAX-WS client code (Apache CXF) like that:
And after 2 or 3 application redeployments there is nullpointer exception in the generic JAX-WS code:
java.lang.NullPointerException: null at org.apache.catalina.core.StandardContext.getResource(StandardContext.java:7354) at org.glassfish.webservices.metroglue.WebInfResourceLoader.getResource(WebInfResourceLoader.java:77) at com.sun.xml.ws.util.xml.XmlCatalogUtil.parseResourcesToCatalog(XmlCatalogUtil.java:104) at com.sun.xml.ws.util.xml.XmlCatalogUtil.createDefaultCatalogResolver(XmlCatalogUtil.java:78) at com.sun.xml.ws.util.xml.XmlUtil.createDefaultCatalogResolver(XmlUtil.java:296) at com.sun.xml.ws.client.WSServiceDelegate.createCatalogResolver(WSServiceDelegate.java:348) at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:334) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:292) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:201) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:182) at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:178) at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:89) at javax.xml.ws.Service.<init>(Service.java:82) at com.francetelecom.papyrus.getcpeinfos.v1.CPEManagementService.<init>(CPEManagementService.java:47)
The only way to resolve this issue is the server restart. After it everything starts to work properly until... a couple of application redeployments... Whas is causing this issue?
The text was updated successfully, but these errors were encountered: