0

I am running an application in WebSphere 6.1.0.29 and am getting a com.sun.xml.ws.spi.ProviderImpl not found error. Unfortunately the application isn't written by us so resolving this is proving to be a little difficult.

In another environment (6.1.0.27) we deleted the javax.xml.bind_2.1.1.jar and javax.xml.ws_2.1.1.jar from the application's library and that resolved the issue, but in this one we get NoClassDefFoundError on javax.xml.ws.spi.FactoryFinder.

I read online that we could reference com.ibm.jaxws.thinclient_6.1.0.jar in our Shared Library but then that prevents the application being accessible via the browser and instead shows a SRVE0255E error.

Any ideas?

DanielBarbarian
  • 5,093
  • 12
  • 35
  • 44
hshah
  • 842
  • 4
  • 14
  • 35
  • SRVE0255E A WebGroup/Virtual Host to handle /abc has not been defined - means that you used wrong context-root or port combination, not that you have problem in application. Check context-root and verify how you are trying to access application. – Gas Nov 02 '14 at 17:35
  • @Gas, the error only occurs if I reference com.ibm.jaxws.thinclient_6.1.0.jar in the Shared Library, so I doubt it is an issue with the context-root or port configuration. – hshah Nov 02 '14 at 19:50
  • 1
    Did you try to run with Parent last classloader setting for the application? You have some conflicting jars in the app. Add listing with jars you have in the app. – Gas Nov 02 '14 at 20:00
  • @Gas, yes I did but same symptoms as mentioned in the topic. What do you mean by add listing? – hshah Nov 02 '14 at 22:34
  • List of jars that you have in WEB-INF/lib. As you have jars there which shouldn't be there. You should remove all xml and jax-ws related jars from there as WAS already provides Jax-ws implementation. Or you could try to disable provided runtime see http://www-01.ibm.com/support/knowledgecenter/SSAW57_6.1.0/com.ibm.websphere.nd.doc/info/ae/ae/twbs_thirdparty.html?cp=SSAW57_6.1.0%2F1-7-9-4-1-14-0&lang=en – Gas Nov 02 '14 at 23:10

1 Answers1

0

@Gas was correct. There were two Parent Class Loader settings in WAS, and setting them both to Parent First resolved the issue :)

hshah
  • 842
  • 4
  • 14
  • 35