Bug 1121093 - connection-ttl does not have any impact on in-vm connections
Summary: connection-ttl does not have any impact on in-vm connections
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Yong Hao Gao
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-18 10:46 UTC by Tyronne Wickramarathne
Modified: 2018-12-06 17:23 UTC (History)
2 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-26 03:38:22 UTC
Type: Bug


Attachments (Terms of Use)

Description Tyronne Wickramarathne 2014-07-18 10:46:46 UTC
Description of problem:
The connection-ttl attribute set on in-vm connection factories does not have any impact

Version-Release number of selected component (if applicable):
JBoss-EAP-6.2_CP4 aka JBoss-EAP-6.2.4
HornetQ-2.3.14.Final (2.3.14.1 (Branch 2.3.eap6_2), 123)

How reproducible:


Steps to Reproduce:
1. Configure both in-vm based connection factories with connection-ttl at any value apart from 60000 

                    <connection-factory name="InVmConnectionFactory">
                        <connectors>
                            <connector-ref connector-name="in-vm"/>
                        </connectors>
                        <entries>
                            <entry name="java:/ConnectionFactory"/>
                        </entries>
                        <connection-ttl>30000000</connection-ttl>
                        <reconnect-attempts>-1</reconnect-attempts>
                    </connection-factory>
                    <pooled-connection-factory name="hornetq-ra">
                        <transaction mode="xa"/>
                        <connectors>
                            <connector-ref connector-name="in-vm"/>
                        </connectors>
                        <entries>
                            <entry name="java:/JmsXA"/>
                        </entries>
                        <connection-ttl>30000000</connection-ttl>
                        <reconnect-attempts>-1</reconnect-attempts>
                    </pooled-connection-factory>



2. Enable TRACE level logging on HornetQ and Netty(optional) :

    <logger category="org.hornetq">
        <level name="TRACE"/>
    </logger>
    <logger category="org.jboss.netty">
        <level name="TRACE"/>
    </logger>

3. Start the server and verify via JBoss-CLI that the above values been properly set :
./subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:read-attribute(name=connection-ttl)
./subsystem=messaging/hornetq-server=default/pooled-connection-factory=hornetq-ra:read-attribute(include-defaults=true,name=connection-ttl)

4. Please check the server.log file. You would see the following :

2014-07-15 22:27:02,691 TRACE [org.hornetq.core.server] (Thread-169 (HornetQ-client-global-threads-1905768823)) InVMConnection [serverID=0, id=997df100-0c67-11e4-aa31-e5670480a144]::Sending inVM packet
2014-07-15 22:27:02,691 TRACE [org.hornetq.core.client] (Thread-169 (HornetQ-client-global-threads-1905768823)) handling packet PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=60000]
2014-07-15 22:27:02,692 TRACE [org.hornetq.core.server] (Thread-169 (HornetQ-client-global-threads-1905768823)) InVMConnection [serverID=0, id=997df100-0c67-11e4-aa31-e5670480a144]::packet sent done

Actual results:
The connection-ttl at the default settings can be seen

Expected results:
The configured connection-ttl value

Additional info:


Note You need to log in before you can comment on or make changes to this bug.