Sudhik created LOGBACK-1426: ------------------------------- Summary: JMS Queue Appender Key: LOGBACK-1426 URL: https://jira.qos.ch/browse/LOGBACK-1426 Project: logback Issue Type: Bug Components: logback-access Affects Versions: 1.2.1 Environment: Container: Liberty Profile <feature>wasJmsClient-2.0</feature> <resourceAdapter id="mqJms" location="$\{server.config.dir}/jars/wmq/wmq.jmsra-9.0.4.0.rar"> <classloader apiTypeVisibility="spec, ibm-api, api, third-party"/> </resourceAdapter> <jmsQueueConnectionFactory id="jndi/MDBQ" jndiName="jndi/MDBQ"> <properties.mqJms channel="APPL_CONN_CHL" hostName="QMAPPPRD.azlifem.azl.pvt" port="1414" queueManager="QM.APP.PRD" transportType="CLIENT" /> </jmsQueueConnectionFactory> <jmsQueue id="jndi/queue" jndiName="jndi/queue"> <properties.mqJms baseQueueName="ELFSERVICE.APP" baseQueueManagerName="QM.APP.PRD" /> </jmsQueue> logback.xml <appender name="queue" class="ch.qos.logback.classic.net.JMSQueueAppender"> <QueueConnectionFactoryBindingName>jndi/MDBQ</QueueConnectionFactoryBindingName> <QueueBindingName>jndi/queue</QueueBindingName> </appender> Logs: 15:06:04,590 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.net.JMSQueueAppender] 15:06:04,591 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [queue] [9/25/18 15:06:05:026 CDT] 00000018 SystemOut O 2018-09-25 15:06:05,025 [Default Executor-thread-1] INFO JMS_LOGGER - Message sent to the configured appender. Reporter: Sudhik Assignee: Logback dev list I need to user JMS Queue Appender and implemented it using 1.2.1 version of logback-access. Logs say appender is added and messages are being sent to queue successfully but I don't actually see the messages in queue. When I write a small program to write the messages to queue using the code of logback-access, it successfully writes. So, no idea on where logback is failing. Do you plan to release any new version of Logback with JMS appender or can you look at why my code is not working ? -- This message was sent by Atlassian JIRA (v7.3.1#73012)