JBoss CLI messaging socket-binding attribute shows bound=false

Solution Unverified - Updated -

Issue

  • My configuration is based on standalone-full.xml, and I can see topics/connection factories are bound.
11:54:34,508 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

When I use JBoss CLI, and perform the following commands:

 ./socket-binding-group=standard-sockets/socket-binding=messaging:read-attribute(name=bound)

The result indicates it is not bound.

{
    "outcome" => "success",
    "result" => false
}

This results bound-port and bound-address are undefined.

I can clear see remoting and web are bound, but why messaging is not?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.3.1

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.