activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinks Gautam (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5651) huge message loss / miss found in amq-camel route exchanges
Date Tue, 10 Mar 2015 14:53:41 GMT

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

Pinks Gautam updated AMQ-5651:
------------------------------
    Attachment: camel-issueRprtd.xml
                activemq.xml
                log4j.properties

the configurations files in use during message loss

> huge message loss / miss found in amq-camel route exchanges 
> ------------------------------------------------------------
>
>                 Key: AMQ-5651
>                 URL: https://issues.apache.org/jira/browse/AMQ-5651
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-camel, Broker
>    Affects Versions: 5.10.1
>         Environment: apache-activemq-5.10.0 on RHEL6 / JDK-1.7
>            Reporter: Pinks Gautam
>         Attachments: activemq.xml, camel-issueRprtd.xml, log4j.properties
>
>
> We have various routes and exchanges configured using camel.xml for pushing SMPP messages
to SMSC.
> For a single route, our producer client application sends message to route-1 which enroutes
it further to SMPP exchange and then to log component for logging.
> We have noticed that around 10-50% of messages were not logged in our logging file after
passing through the route which leads to blunder mismatch in figures.
> Earlier we were using over apache-activemq-5.9.1 with same route configurations and is
working with 0% loss in log file. I am not able to understand what is the reason behind this
mismatch as only activemq version has been changed and rest all application specific configurations
are same.
> I am attaching my activemq.xml, camel.xml and log4j.properties file for reference.
> Seeking the earliest possible response as the system is in production, affecting our
clients and business.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message