Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-4193

Unable to load custom properties from credentials.properties file located in conf folder of ActiveMQ installation directory

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Not A Problem
    • 5.5.1
    • None
    • Connector, Pool
    • None
    • I have ActiveMQ Version 5.5.1 installed on my linux[RHEL] box.

    Description

      Hi Developers,

      I basically wanted to read some custom properties from a credentials.property file located in conf folder of AMQ installation directory [/opt/apache/installed/activemq55-5.5.1/conf]

      Steps :
      1. I put my custom entries in credentials.properties file , with the details of,say a given Datasource.
      2. Given PropertyPlaceholderConfigurer bean configurations in my activemq-jdbc. xml.
      3. I have imported "activemq-jdbc. xml" in my activemq.xml file[/opt/apache/installed/activemq55-5.5.1/conf]
      4.When I startup activeMQ , it fails to startup. Also, I am not able to see the JDBC related tables being created, because it failed to startup.
      5.If I give values directly instead of reading from "credentials.properties", AMQ starts up successfuuly and I am able to see the Tables namely "ACTIVEMQ_MSGS,ACTIVEMQ_LOCK,ACTIVEMQ_ACKS" being created in my datasource.

      Please find attached the files. This looks like a bug to me. If not,kindly let me know the workaround for the same.

      Regards
      Jessy

      Attachments

        1. activemq.log
          0.4 kB
          Jessy
        2. activemq.xml
          5 kB
          Jessy
        3. activemq-jdbc.xml
          4 kB
          Jessy
        4. credentials.properties
          1 kB
          Jessy
        5. log4j.properties
          3 kB
          Jessy

        Activity

          People

            Unassigned Unassigned
            jessy_2012 Jessy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: