“No transport provider registered with ID” TransportException Workaround.

“No transport provider registered with ID” TransportException Workaround.
0 votes, 0.00 avg. rating (0% score)

If you are using Oracle Service Bus(In Oracle Service Bus 10g Release 3) or earlier versions and using custom transports like tcp , db transports etc.  you may get exceptions like “No transport provider registered with ID” in server startup .


The Stack of exceptions will be like :


TransportManagerImpl.endChangeNotification,
com.bea.wli.sb.transports.TransportException:
No transport provider registered with ID: <ID>


The cause of this exception is about deployment orders.


During server startup, modules with a lower Deployment Order value are deployed before modules with a higher deployment order value.
Modules which have the same Deployment Order value are deployed in alphabetical order.
If you dont change during the deployment ,  new  modules are configured with a default Deployment Order value of 100.


To workaround this problem change the deployment order of your custom transport.

This value must be lower than ALSB Framework Starter Application deployment order value.

Finally restart your application server.

Tagged with: , , ,
Posted in Blog

Leave a Reply

Your email address will not be published. Required fields are marked *

*


three + 9 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>