3:19 a.m.
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Clebert Suconic
Fix For: 7.0.2.Final
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
New subject: [JBoss JIRA] Closed: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic closed AS7-1899.
--------------------------------
Resolution: Rejected
if you send messages non-persistently, they are gone after a shutdown.
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Clebert Suconic
Fix For: 7.0.2.Final
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Andrés Pereiro commented on AS7-1899:
-------------------------------------
Why have you closed this issue?
The description states clearly that the messages are sent as PERSISTENT messages.
http://community.jboss.org/thread/172575?tstart=0
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Clebert Suconic
Fix For: 7.0.2.Final
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 a.m.
New subject: [JBoss JIRA] Reopened: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic reopened AS7-1899:
----------------------------------
I misunderstood the issue, sorry
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Clebert Suconic
Fix For: 7.0.2.Final
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:28 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic updated AS7-1899:
---------------------------------
Assignee: Andy Taylor (was: Clebert Suconic)
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.0.2.Final
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-1899:
------------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.0.2.Final)
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:27 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Andy Taylor commented on AS7-1899:
----------------------------------
This is because the JMSQueueService (and other destination/cf services) delete the queue
on shutdown via the stop(...) method. This means when the message journal is reloaded,
which happens before the queue is redeployed by the AS, the messages are discarded.
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Andy Taylor commented on AS7-1899:
----------------------------------
for destinations you should probably call jmsManager.removeQueueFromJNDI(queueName);
instead. Its probably ok to destroy connection factories
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:05 a.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Andy Taylor resolved AS7-1899.
------------------------------
Resolution: Done
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
9:53 p.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1899:
---------------------------------------
https://github.com/jbossas/jboss-as/commit/55c3c2a8feddf010b614a6bdb0c39e...
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
9:43 a.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
David Wery commented on AS7-1899:
---------------------------------
As I understand, this issue is resolved but in JBoss 7.1.0.Beta1 :(
I'm currently using JBoss 7.0.1 (and having this issue). Is it possible to have the
module update (messaging module JAR updates) to apply this fix ? Or, do you have a link
where to download the JBoss 7.1.0.Beta1 ?
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
9:49 a.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
Rico Neubauer commented on AS7-1899:
------------------------------------
@David Beta1 is scheduled for today; when it's done it will be made available on the
usual download page. If you want a continuous build, you can get it from here:
https://ci.jboss.org/hudson/job/JBoss-AS-7.0.x/
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
5:22 a.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
David Wery commented on AS7-1899:
---------------------------------
@Rico Ok thanks. I was already aware of the CI link but it was labeled JBoss-AS-7.0.x (and
not JBoss-AS-7-1.x) ;)
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
5:30 a.m.
New subject: [JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
[
https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1899:
-----------------------------------
{quote}
@Rico Ok thanks. I was already aware of the CI link but it was labeled JBoss-AS-7.0.x (and
not JBoss-AS-7-1.x)
{quote}
Kind of "fixed" that recently http://community.jboss.org/message/636779#636779.
P.S: AS 7.1.0.Beta1 has just been released
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-November/004667.html
HornetQ deletes all JMS messages after shutdown
-----------------------------------------------
Key: AS7-1899
URL: https://issues.jboss.org/browse/AS7-1899
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Reporter: Fabrizio Benedetti
Assignee: Andy Taylor
Fix For: 7.1.0.Beta1
After sending a persistent JMS message to a queue, and the message is not consumed, after
reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to
false in standalone.xml, or sometimes the entire element is deleted.
Following messaging subsystem configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<journal-type>NIO</journal-type>
<persistence-enabled>true</persistence-enabled>
<acceptors>
<netty-acceptor name="netty"
socket-binding="messaging"/>
<netty-acceptor name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<address-settings>
<address-setting match="#">
<dead-letter-address>
jms.queue.DLQ
</dead-letter-address>
<expiry-address>
jms.queue.ExpiryQueue
</expiry-address>
<redelivery-delay>
0
</redelivery-delay>
<max-size-bytes>
10485760
</max-size-bytes>
<message-counter-history-day-limit>
10
</message-counter-history-day-limit>
<address-full-policy>
BLOCK
</address-full-policy>
</address-setting>
</address-settings>
<connectors>
<netty-connector name="netty"
socket-binding="messaging"/>
<netty-connector name="netty-throughput"
socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue"
roles="guest"/>
<permission type="deleteNonDurableQueue"
roles="guest"/>
</security-setting>
</security-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="netty"/>
</connectors>
<entries>
<entry name="RemoteConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
<jms-queue name="MyQueue">
<entry name="queue/MyQueue"/>
</jms-queue>
</jms-destinations>
</subsystem>
{code}
--
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
4699
days inactive
4761
days old
13 comments
10 participants
participants (10)
-
Andrés Pereiro (JIRA) -
Andy Taylor (JIRA)
-
Andy Taylor (Resolved) (JIRA)
-
Brian Stansberry (Commented) (JIRA)
-
Clebert Suconic (JIRA)
-
David Wery (Commented) (JIRA)
-
Fabrizio Benedetti (JIRA)
-
jaikiran pai (Commented) (JIRA)
-
Jason Greene (JIRA)
-
Rico Neubauer (Commented) (JIRA)