Why JBoss is not able to create a JMS bridge via CLI ?

Solution Verified - Updated -

Issue

  • While creating a JMS bridge connecting from EAP 6.3 to EAP4.3 by following the article [1] getting the following failure message while executing the below CLI command to create the JMS bridge:
[standalone@localhost:10099 /] /subsystem=messaging/jms-bridge=myBridge/:add(module="org.jboss.legacy",source-destination="/queue/sourceQueue",source-connection-factory="ConnectionFactory",source-user="guest",source-password="guest",source-context={"java.naming.factory.initial" => "org.jnp.interfaces.NamingContextFactory","java.naming.provider.url" => "jnp://localhost:1099","java.naming.factory.url.pkgs" => "org.jboss.naming:org.jnp.interfaces"},target-destination="java:jboss/jms/queue/targetQueue",target-connection-factory="java:/ConnectionFactory",quality-of-service=AT_MOST_ONCE,failure-retry-interval=20 000,max-retries=-1,max-batch-size=500,max-batch-time=500,add-messageID-in-header=true)
{
    "outcome" => "failed",
    "failure-description" => "org.jboss.legacy:main",
    "rolled-back" => true
}

Environment

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

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.