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

Jessy updated AMQ-4194:
-----------------------

    Attachment: AMQ WebConsole_With JDBC persistance setup..jpg
    
> With JDBC persistence feature for AMQ, webconsole does not show up any queues 
> ,but just a blank table.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4194
>                 URL: https://issues.apache.org/jira/browse/AMQ-4194
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool, Documentation
>    Affects Versions: 5.5.1
>         Environment: I have ActiveMQ Version 5.5.1 installed on my 
> linux[RHEL] box.
>            Reporter: Jessy
>            Priority: Critical
>         Attachments: activemq.xml, AMQ WebConsole_With JDBC persistance 
> setup..jpg
>
>
> Hi Developers,
> I am basically trying to set up JBDC persistance feature on ActiveMQ.
> Below are the steps:
> 1.Made appropriate entries required in the "activemq-jdbc. xml"[conf folder 
> of AMQ installation directory]
> 2.I have imported "activemq-jdbc. xml" in my activemq.xml 
> file[/opt/apache/installed/activemq55-5.5.1/conf]
> 3.AMQ starts up successfuuly and I am able to see the Tables namely 
> "ACTIVEMQ_MSGS,ACTIVEMQ_LOCK,ACTIVEMQ_ACKS" being created in my datasource. 
> When i post the messages to the queues, database table ACTIVEMQ_MSGS stores 
> the message.
> But,when I check my webconsole, I just see an empty table, no queue related 
> information is shown up. 
> Without JDBC setup, I would be able to see the list of queues on my AMQ 
> webconsole. Would want this to be the same with JDBC feature too.
> Looks like a bug to me. If not,kindly let me know if there are added 
> configurations need to be done to set this right. Kindly throw more light on 
> this issue. 
> Kindly let me know if you need more information to debug this issue.
> PFA
> Regards
> Jessy

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to