InvalidNameException: WFNAM00007: Invalid URL scheme name T3 in deployment in JBoss EAP 7

Solution Verified - Updated -

Issue

  • Can I use the T3 protocol in JBoss EAP?
  • Issue in accessing Weblogic server queue from JBoss server 7 during application EAR deployment in JBoss server. During the deployment, the connection bean configurations not loaded and throwing the following issue:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'onDemandConnectionFactory' defined in class path resource [com/example/config/ExampleApplicationConfigFile.class]: Invocation of init method failed; nested exception is javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "t3"
  • We packaged the Weblogic Client jar wlthint3client.jar in your application in JBoss EAP to invoke a remote EJB in Weblogic using the Weblogic t3 protocol and getting this error:
javax.naming.InvalidNameException: WFNAM00007: Invalid URL scheme name "t3"
  at org.wildfly.naming-client@1.0.14.Final-redhat-00001//org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:808)
  at org.wildfly.naming-client@1.0.14.Final-redhat-00001//org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:140)
  at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content