headers
Jason Dillon | 1 Feb 04:19
Gravatar

Re: Confusing docs about disabling flow control

So is the community abandoning its documentation in favor of the fuse documentation?  I've seen similar
replies a few times to go look at fuse docs vs. what is on the activemq.apache.org site before.

Would be nice to have a single concise location to find the most current/accurate/comprehensive
documentation for the project.

--jason

On Jan 30, 2012, at 1:41 AM, Torsten Mielke wrote:

> Hello Jason,
> 
> Yes, you can simply set producerFlowControl=false on an out-of-the-box broker configuration without
having to change the underlying cursor. 
> When disabling flow control, make sure to set upper limits for storeUsage tempUsage and memoryUsage to
prevent the broker from running out of disk space or heap memory.
> 
> 
> There is perhaps better documentation provided by FuseSource on this topic
> http://fusesource.com/products/enterprise-activemq/#documentation
> 
> Also see the persistence guide which has a full chapter on message cursors
> http://fusesource.com/docs/broker/5.5/persistence/index.html
> 
> 
> Hope this helps,
> 
> 
> 
> Torsten Mielke
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hiram Chirino | 1 Feb 05:47
Gravatar

Re: Apollo and websockets

Since it's been requested so much I started working on it today and made
good progress.  The next snapshot build of apollo 1.1-SNAPSHOT should have
WebSocket support.  Just add connectors for the 'ws://' or 'wss://'
protocols to the apollo.xml file.  For example:

  <connector id="ws"  bind="ws://0.0.0.0:61623"  connection_limit="2000"/>
  <connector id="wss" bind="wss://0.0.0.0:61624" connection_limit="2000"/>

Stomp frames get sent as binary to the JS client which it did not
originally expect, so I've patched up the following JS client lib to handle
that case:
https://github.com/chirino/stomp-websocket

On Tue, Jan 31, 2012 at 1:28 PM, chirino <hiram@...> wrote:

> Apollo does not yet support WebSockets.  :(
> Issue https://issues.apache.org/jira/browse/APLO-145
> has already been raised.  And I totally agree with it.  We should suport
> it.
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Apollo-and-websockets-tp4200336p4345411.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

--

-- 

**
(Continue reading)

Permalink | Reply | 0 comments |
headers
tomerb | 1 Feb 14:19
Favicon

Re: Reply:network of broker - update and rebalance not working

figured out the problem (at list on my env)
when a broker updates another broker that it is up, it identifies itself by
the server name.
once the server name of all brokers was added to /etc/hosts on the client
side, all was well
:)
I guess this is bad practice, and the broker should identify itself by ip
and not by hostname

I was running activeMQ 5.5.1 on ubuntu 10.4

--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-update-and-rebalance-not-working-tp4343907p4347806.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Permalink | Reply | 1 comment |
headers
Zagan | 1 Feb 15:21
Picon

Who creates ActiveMQ.DLQ and DLQ.<QueueName> Queues

Hello, 
I have an Active MQ broker secured with Username/Password through the use of 
<simpleAuthenticationPlugin> and <authorizationPlugin>. 

I now want to configure a Deadletter queue for each created queue:
<policyEntry queue=">" producerFlowControl="true"
						memoryLimit="1mb">
						
						<deadLetterStrategy>
							<individualDeadLetterStrategy
								queuePrefix="DLQ." useQueueForQueueMessages="true"
								processExpired="true" processNonPersistent="false" />
						</deadLetterStrategy>

The client queues are automatically generated at startup via
 <destinations>
      <queue physicalName="TEST" />
    </destinations>

When I start the Active MQ broker and connect with a client (who has only
the right to read + write to the TEST queue) something went wrong. So he
wants to put the messag to DLQ.TEST. Who creates the queue - the client who
doesn't have the permissions or is this queue created serverside with
"admin" privileges? 

Thanks for any help

--
View this message in context: http://activemq.2283324.n4.nabble.com/Who-creates-ActiveMQ-DLQ-and-DLQ-QueueName-Queues-tp4348011p4348011.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
(Continue reading)

Permalink | Reply | 1 comment |
headers
reids | 1 Feb 15:37
Picon

Re: JMS Bridge with ssl + authentication issue


Feng Xue wrote
> 
> Hi All,
> 
> I have been trying to configure 2 brokers with JMS bridge, ssl and
> authentication.
> 
> The goal is to set up a broker "localServer" with JMS bridge that connects
> to 
> another broker "remoteServer1". The JMS bridge configuration works fine if
> local Broker
> has no ssl and authentication.  But if I add ssl and/or authentication
> into the 
> localbroker, it always starts with error as shown at the end of the
> message.
> 
> <snip>
> 
> ERROR JmsQueueConnector              - Failed to initialize the
> JMSConnector
> javax.jms.JMSException: User name or password is invalid.
>         at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:46)
>         at
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1177)
> 

I know this is an old thread but I found it searching for a solution to the
same issue so perhaps someone else might benefit in the future.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oscar Pernas | 1 Feb 16:24
Picon
Gravatar

disable a specific advisory message

Hi,

I've disabled the deadletters queue like this:

<deadLetterStrategy>
                        <sharedDeadLetterStrategy processExpired="false" />
</deadLetterStrategy>

because I dont want to post process expired messages. Now Im seeing that
when the broker discards this expired messages, it drops messages from the
client. I was thinking that could be because a lot of messages are send to
the expired advisory topic. How I can disable this specific advisory
messages? Could be the reason of the dropped packets? I can disable all
advisory messages, but I want only this expired/DLQ advisory messages.

Thanks in advance

--

-- 
Óscar Pernas Plaza.
Permalink | Reply | 0 comments |
headers
Matt Pavlovich | 1 Feb 17:05
Picon

Re: Confusing docs about disabling flow control

Hi Jason-

The community has definitely not abandoned the community documentation.  
As with many open source projects, there are only a few people dedicated 
to it full-time vs hundreds of users.

I don't think Fuse is trying to corner the documentation on the product 
or anything.  Their docs are free.  I look at it akin to a blogger 
posting something useful on his blog, instead of the community site.

I agree that single doc location is ideal, but volunteer resources are 
limited and mostly dedicated to solving code issues.  If you know anyone 
that would like to help organize the community docs, I'm sure it 
wouldn't be hard to get them tied in.

Thanks,
Matt Pavlovich

Media|Driver

On 1/31/12 9:19 PM, Jason Dillon wrote:
> So is the community abandoning its documentation in favor of the fuse documentation?  I've seen similar
replies a few times to go look at fuse docs vs. what is on the activemq.apache.org site before.
>
> Would be nice to have a single concise location to find the most current/accurate/comprehensive
documentation for the project.
>
> --jason
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matt Pavlovich | 1 Feb 17:11
Picon

Re: Reply:network of broker - update and rebalance not working

Hi-

Glad to here the issue has cleared up for you.  Using host names is 
probably a safer setup in most cases, since there are situations where 
using the IP address may cause problems for other folks.

Thanks,
Matt Pavlovich

On 2/1/12 7:19 AM, tomerb wrote:
> figured out the problem (at list on my env)
> when a broker updates another broker that it is up, it identifies itself by
> the server name.
> once the server name of all brokers was added to /etc/hosts on the client
> side, all was well
> :)
> I guess this is bad practice, and the broker should identify itself by ip
> and not by hostname
>
> I was running activeMQ 5.5.1 on ubuntu 10.4
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-update-and-rebalance-not-working-tp4343907p4347806.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
Christian Hilgers | 1 Feb 17:57
Picon
Favicon

Re: ActiveMQ Master/slave with MySQLCluster backend

Am 31.01.2012 14:13, schrieb Gary Tully:
> This need some work.
> On 5.6, a single broker can deal with a failover of the jdbc store.
> The difficulty is locking in the master/slave case, or peer cluster case.
>
> The current lock impl (who's job it is to get an exclusive lock on the
> store) treats failure of a lock as a fatal event and stops the broker.
>
> What would be great if you could describe how you think it should
> work, or how you would like it to work.
>
> I think this is something we can/should support.

I agree, this should be supported as this is the only way to build continental
clusters.

The current implementation does single
Locking Query is SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE
to determine who is Master.

As this lock is restricted to one specific node, I now understand why AMQ
does the restart.

My suggestion to get out here is:
selected Master does perodically (eg. each second)
SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE
UPDATE UPDATE ACTIVEMQ_LOCK SET TIME=$NOW,BROKER_NAME=$NAME WHERE ID = 1
COMMIT

analog to the idea from
(Continue reading)

Permalink | Reply | 2 comments |
headers
Chris Robison | 1 Feb 19:22
Picon

Using LDAP login module

I'm trying to use the LDAP login module to tie into Active Directory.
Here's what my AMQ conf looks like:

<plugins>
<jaasAuthenticationPlugin configuration="ldap-login" />
<authorizationPlugin>
<map>
<authorizationMap>
<authorizationEntries>
<authorizationEntry queue=">" read="MQCoreAdmin" write="MQCoreAdmin"
admin="MQCoreAdmin" />
<authorizationEntry topic=">" read="MQCoreAdmin" write="MQCoreAdmin"
admin="MQCoreAdmin" />
</authorizationEntries>
</authorizationMap>
</map>
</authorizationPlugin>
</plugins>

Here is what the login.config looks like:

ldap-login {
  org.apache.activemq.jaas.LDAPLoginModule required
    debug=true
    initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory
    connectionURL="ldap://dc101.cdr.corp"
    connectionUsername="CN=AMQ Service User,CN=Users,DC=cdr,DC=corp"
    connectionPassword=Password!
    connectionProtocol=""
    authentication=simple
(Continue reading)

Permalink | Reply | 14 comments |

Gmane