Thanks.
These postings hits the Mark Richard's article right on the bull's eye.
On Thu, Oct 25, 2012 at 6:01 AM, Christian Posta
wrote:
> Sean K,
> Looks like you already got a response from James :)
> But here's at least one discussion that took place a while ago a
http://www.wmrichards.com/amqp.pdf
On Wed, Oct 24, 2012 at 11:58 PM, Claus Ibsen wrote:
> Hi
>
> Do you have a link to the article?
>
>
> On Thu, Oct 25, 2012 at 12:37 AM, Sean K wrote:
>> Has anyone responded to this article written by Mark Richards about
>> A
Has anyone responded to this article written by Mark Richards about
AMQP and JMS (includes ActiveMQ)?
Specifically:
"This means that message clients using AMQP are completely agnostic as
to which AMQP clients API or
AMQP message broker you are using." -- I remember hearing something
like that
the credentials you're using in login.config are not
> matching your Ldap server.
>
>
> Regards
> --
> Dejan Bosanac
> --
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> dbosa...@redhat.com
> Twitter: @dejanb
> Blog: http://sensati
.LDAPLoginModule.open(LDAPLoginModule.java:437)^M
at
org.apache.activemq.jaas.LDAPLoginModule.authenticate(LDAPLoginModule.java:175)^M
... 26 more^M
On Thu, Oct 18, 2012 at 3:48 PM, Sean K wrote:
> And then on the broker side, here is the log that I snipped out --
>
> I turne
ory Manager" -- all of them results in the user not being
authenticated.
Any ideas?
On Thu, Oct 18, 2012 at 2:27 PM, Sean K wrote:
> I havent tried that yet.
>
> But I think I am getting closer.
>
> I took a vanilla activemq 5.6.0 bundle zip and expanded it on a
> win
http://camel.apache.org/schema/spring";>
On Wed, Oct 17, 2012 at 9:18 PM, Claus Ibsen wrote:
> Hi
>
> Have you tried with the ActiveMQ 5.7.0 release?
>
>
> On Wed, Oct 17, 2012 at 2:09 AM, Sean K wrote:
>> Hi,
>> I am working with the documentation
Hi,
I am working with the documentation on the activemq site for
configuring the LDAP.
http://activemq.apache.org/security.html -- almost everything is
copied verbatim except for hostnames and there were a few parameters
that were not writable by the current bean so I remove them -- for
example t
So if I set broker centos-test3 as a unidirectional bridge- it cannot
be a consumer, only a producer on a queue.
how does real world deployments handle data going in both directions?
I can think of two ways:
1.) put the broker in a less restricted DMZ zone in a company with
less ports blocked.
2
If it is duplex, it is not configurable to use a certain port or specific range?
For my case, I am not 100% certain at this time whether unidirectional
will work the the business case.
On Wed, Aug 22, 2012 at 5:07 PM, ceposta wrote:
> The network connector in broker 2 has duplex set to "true"
attached: activemq-centos-test1.xml for broker 1
attached: activemq-centos-test3.xml for broker 2.
On Wed, Aug 22, 2012 at 3:46 PM, ceposta wrote:
> From your logs:
>
> sk92129 wrote
>>
>> 2012-08-22 12:58:21,363 | INFO | Listening for connections at:
>> ssl://centos-test1.foo.com:61616?needC
e firewall so that an
outside broker can connect to my broker?
On Wed, Aug 22, 2012 at 12:12 PM, Sean K wrote:
> I have two centos machines up and running. When I disable or turn
> off iptables, the one broker can establish a transport bridge with the
> other broker on the other ce
I have two centos machines up and running. When I disable or turn
off iptables, the one broker can establish a transport bridge with the
other broker on the other centos machine.
I noticed that the port number being used changes -- 53033, 53067, etc..
How can I configure each broker in the stat
13 matches
Mail list logo
