Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: error (athena.apache.org: encountered temporary error during SPF
 processing of domain of karel.gardas@centrum.cz)
Message-ID: <52135DA3.6040800@centrum.cz>
Date: Tue, 20 Aug 2013 14:14:27 +0200
From: Karel Gardas <karel.gardas@centrum.cz>
User-Agent: Mozilla/5.0 (X11; SunOS i86pc;
 rv:10.0.4) Gecko/20120628 Thunderbird/10.0.4
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Re: AMQ 5.7.0 and interceptors configuration.
References: <1376980413473-4670502.post@n4.nabble.com>
 <52133DE2.5010304@centrum.cz>
 <CAH+vQmM4TinCiBGqOAJd4BDJ4ncwDfS4rAFh=ZTFug_1RH3QGg@mail.gmail.com>
In-Reply-To: 
 <CAH+vQmM4TinCiBGqOAJd4BDJ4ncwDfS4rAFh=ZTFug_1RH3QGg@mail.gmail.com>
Content-Type: multipart/mixed;
 boundary="------------070000050405010901020602"

--------------070000050405010901020602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


In 5.7.0 XML schema I don't see plugins element defined so I'm still 
curious how the interceptors.html page may be correct. Anyway, my xml 
config file is attached.

Thanks!
Karel

On 08/20/13 01:50 PM, Gary Tully wrote:
> post the xml config you are using and the parse exception. that doco
> is fine... pay attention to the detail in the error and the xml schema
> - http://activemq.apache.org/xml-reference.html
>
> On 20 August 2013 10:58, Karel Gardas<karel.gardas@centrum.cz>  wrote:
>>
>> Hello,
>>
>> I'm trying to configure our specific authorization interceptor into ActiveMQ
>> 5.7.0 and while following http://activemq.apache.org/interceptors.html page
>> I'm neither able to define plugin as an xbean and then reference it in the
>> broker tag/element nor define it in plugins element inside the broker. I
>> always get SAXParseException complaining that such format is not supported.
>> So neither of two offered ways work for me.
>>
>> My question is: is http://activemq.apache.org/interceptors.html already
>> out-dated and if so, what shall I do in order to integrate our interceptor
>> with 5.7.0 release?
>>
>> Thanks!
>> Karel
>
>
>


--------------070000050405010901020602
Content-Type: text/xml;
 name="activemq-openpmf-tls-auth.xml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="activemq-openpmf-tls-auth.xml"

<!--
    Licensed to the Apache Software Foundation (ASF) under one or more
    contributor license agreements.  See the NOTICE file distributed with
    this work for additional information regarding copyright ownership.
    The ASF licenses this file to You under the Apache License, Version 2.0
    (the "License"); you may not use this file except in compliance with
    the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
-->
<!-- START SNIPPET: example -->
<beans
  xmlns="http://www.springframework.org/schema/beans"
  xmlns:amq="http://activemq.apache.org/schema/core"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
  http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->
    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="locations">
            <value>file:${activemq.conf}/credentials.properties</value>
        </property>
    </bean>

    <!--
        The <broker> element is used to configure the ActiveMQ broker.
    -->
    <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">

        <!--
            For better performances use VM cursor and small memory limit.
            For more information, see:

            http://activemq.apache.org/message-cursors.html

            Also, if your producer is "hanging", it's probably due to producer flow control.
            For more information, see:
            http://activemq.apache.org/producer-flow-control.html
        -->

        <destinationPolicy>
            <policyMap>
              <policyEntries>
                <policyEntry topic=">" producerFlowControl="true">
                    <!-- The constantPendingMessageLimitStrategy is used to prevent
                         slow topic consumers to block producers and affect other consumers
                         by limiting the number of messages that are retained
                         For more information, see:

                         http://activemq.apache.org/slow-consumer-handling.html

                    -->
                  <pendingMessageLimitStrategy>
                    <!-- <constantPendingMessageLimitStrategy limit="1000"/> -->
                    <constantPendingMessageLimitStrategy limit="-1"/>
                  </pendingMessageLimitStrategy>
                  <dispatchPolicy>
                    <!--
                        Use total ordering, see:
                        http://activemq.apache.org/total-ordering.html
                    -->
                       <strictOrderDispatchPolicy/>
                  </dispatchPolicy>

                </policyEntry>
                <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
                  <!-- Use VM cursor for better latency
                       For more information, see:

                       http://activemq.apache.org/message-cursors.html

                  <pendingQueuePolicy>
                    <vmQueueCursor/>
                  </pendingQueuePolicy>
                  -->
                </policyEntry>
              </policyEntries>
            </policyMap>
        </destinationPolicy>


        <!--
            The managementContext is used to configure how ActiveMQ is exposed in
            JMX. By default, ActiveMQ uses the MBean server that is started by
            the JVM. For more information, see:

            http://activemq.apache.org/jmx.html
        -->
        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>

        <!--
            Configure message persistence for the broker. The default persistence
            mechanism is the KahaDB store (identified by the kahaDB tag).
            For more information, see:

            http://activemq.apache.org/persistence.html
                    
                    journalMaxFileLength="32mb"
                    concurrentStoreAndDispatchQueues="false"
                    concurrentStoreAndDispatchTopics="false"
                    enableJournalDiskSyncs="true"

        -->
        <persistenceAdapter>
            <kahaDB directory="${activemq.data}/kahadb"
                    journalMaxFileLength="32mb"
                    enableJournalDiskSyncs="true"
                    concurrentStoreAndDispatchTopics="false"
                    concurrentStoreAndDispatchQueues="false"
            />
        </persistenceAdapter>


        <plugins>
          <bean id="OpenPMF" class="com.objectsecurity.openpmf.activemq.PMFPlugin"/>
        </plugins>


          <!--
            The systemUsage controls the maximum amount of space the broker will
            use before slowing down producers. For more information, see:
            http://activemq.apache.org/producer-flow-control.html
            If using ActiveMQ embedded - the following limits could safely be used:

        <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage limit="20 mb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="1 gb"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="100 mb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>
        -->
          <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage limit="64 mb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="100 gb"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="50 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>

        <!--
            The transport connectors expose ActiveMQ over a given protocol to
            clients and other brokers. For more information, see:

            http://activemq.apache.org/configuring-transports.html
        -->
        <transportConnectors>
            <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
            <!-- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireformat.maxFrameSize=104857600"/> -->
            <transportConnector name="openwire" uri="ssl://0.0.0.0:61617?maximumConnections=1000&amp;wireformat.maxFrameSize=104857600?transport.needClientAuth=true"/>
        </transportConnectors>

        <!-- destroy the spring context on shutdown to stop jetty -->
        <shutdownHooks>
            <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
        </shutdownHooks>

    </broker>

    <!--
        Enable web consoles, REST and Ajax APIs and demos

        Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
    -->
    <import resource="jetty.xml"/>

</beans>
<!-- END SNIPPET: example -->

--------------070000050405010901020602--