[
https://issues.jboss.org/browse/AS7-1846?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1846:
-----------------------------------
Just checked the latest upstream which has these configs (in standalone-full.xml):
{code:xml}
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
....
<entries>
<entry name="java:/JmsXA"/>
</entries>
{code}
and they get bound (correctly) to:
{code}
13:04:44,760 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound
messaging object to jndi name java:/ConnectionFactory
13:04:44,952 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-1)
JBAS010406: Registered connection factory java:/JmsXA
{code}
So this no longer appears to be an issue.
JMS connection factories bad configuration
------------------------------------------
Key: AS7-1846
URL:
https://issues.jboss.org/browse/AS7-1846
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final, 7.1.0.Alpha1
Reporter: Martin Vecera
Assignee: Andy Taylor
Priority: Blocker
Connection factories (ConnectionFactory and JmsXA) are configured in the following way in
standalone*.xml:
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
<entries>
<entry name="java:/JmsXA"/>
</entries>
That makes them to be bound under java:/java:/ConnectionFactory and java:/java:/JmsXA.
RemoteConnectionFactory is configured properly and removing the java:/ prefix fixes the
binding location.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira