activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-527) 4.0 M4 Persistent Issue with network brokers
Date Tue, 12 Jun 2007 14:51:33 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Strachan resolved AMQ-527.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0

Its been over a year since we asked for more feedback; so am gonna assume this is now resolved.
Let us know if its not and we can reopen

> 4.0 M4 Persistent Issue with network brokers
> --------------------------------------------
>
>                 Key: AMQ-527
>                 URL: https://issues.apache.org/activemq/browse/AMQ-527
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 4.0 M4
>         Environment: RadHat Linux Enterprise Server 3, Tomcat 5.5.15, MySQL 5.0.18 for
Linux
>            Reporter: Leon Hu
>            Assignee: Rob Davies
>             Fix For: 5.0.0
>
>
> Setup: 
> 3 networked brokers, B1, B2, and B3, on 3 servers, connected using multicast discovery.
activemq.xml: 
>  <broker useJmx="false" brokerName="B1"> 
>  
>  <persistenceAdapter>
>         <journaledJDBC journalLogFiles="5" dataDirectory="foo" dataSource="#mysql-ds"/>
>  </persistenceAdapter>
>  
>  <transportConnectors> 
>  <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>

>  </transportConnectors> 
>  
>  <networkConnectors> 
>  <networkConnector uri="multicast://default"/> 
>  </networkConnectors> 
>  
>  </broker> 
>  
>  <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
>            <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
>            <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
>                  <property name="username" value="activemqUser"/>
>                  <property name="password" value="activemqPwd"/>
>                  <property name="poolPreparedStatements" value="true"/>
>  </bean>
> Similar for B2 and B3. 
> Two queues: Q1 and Q2. 
> Two producers, one for each queue, both producers connected to B1. 
> One Q1 cosumer connected to B1, another Q1 consumer on B2. 
> One Q2 consumer connected to B2, another Q2 consumer connected to B3. 
> The problems:
> Problem 1: 
> Q1 messages are all consumed on B1, never delivered to B2, although there is a Q1 consumer
on B2. I understand this is probably the expected behavior, although this definitely looks
like a load balancing issue. 
> Problem 2: 
> All Q2 messages remain persistented in the MySQL DB on B1, even after being successfully
forwarded to B2 and B3 and consumed there. 
> Problem 3: 
> When all the JMS entities are stoped and restarted, Q1 works fine after a while, but
all Q2 messages are no longer forwarded to B2 and B3. This means that all Q2 messages are
not consumed but persisted instead, further increase the size of the persistent store. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message