Resolving deployment issues with Service Bus 12c - OSB-398016 - Error loading WSDL SNAGHTMLc3d51e6

Resolving deployment issues with Service Bus 12c – OSB-398016 – Error loading WSDL

I was completely stuck with Service Bus 12c project deployment from JDeveloper to the Service Bus run time. Every deployment met with the same fate: Conflicts found during publish – OSB-398016, Error loading the WSDL from the repository:  The WSDL is not semantically valid: Failed to read wsdl file from url due to — Unknown protocol: servicebus.

I was completely lost and frustrated – not even a simple hello_world could make it to the server.


Then, Google and Daniel Dias from Link Consulting to the rescue: He had run into the same problem – and he had a fix for it! Extremely hard to find if you ask me, but fairly easy to apply.

It turns out this is a known bug (18856204). The bug description refers to BPM and SB being installed in the same domain.

The resolution:

Open the Administration Console for the WebLogic Domain. From the Services node, select service OSGi Frameworks:


Click on the bac-svnserver-osgi-framework link. Note: if you run in production mode, you will now first have to create an edit session.

Add felix.service.urlhandlers=false in the Init Properties field for the configuration of this service. Then press the Save button.


If you run in Production Mode, you now have to commit the edit session.

Then, in order have this modification make any difference, you have to restart the WebLogic (Admin) Server.

This resolved the issue for me – a weight was lifted of my shoulders. Thanks to Daniel from Link!

Edit (28th December 2014): See for more details and a patch from Oracle this article by Jan van Zoggel:


  1. Mudhu krishna October 17, 2017
  2. Timothy February 16, 2017
  3. imgeeyaul September 12, 2016
  4. Amit Datta October 25, 2015
  5. fabrice August 19, 2014
    • Juan Pablo Vadell August 28, 2014
      • Giovani October 15, 2014