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
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
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
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
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
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
Chris-
Try adding s to the connectionProtocol value, so it'd read
connectionProtocol=s. I think that's for simple, as in clear text
password to auth against LDAP.
Matt
On 2/1/12 12:22 PM, Chris Robison wrote:
I'm trying to use the LDAP login module to tie into Active Directory.
Here's
My bad.. the default is s in the ActiveMQ src. This is where you
would specify ssl or not. I think the problem is that you have it
empty, so its parsing as NULL, and you are getting the error. Try not
setting it, and see if the default works for you.
On 2/1/12 12:22 PM, Chris Robison
No good. I should note that I'm combining LDAP authenticate with simple
authorization. Is that possible?
Chris
On Wed, Feb 1, 2012 at 12:42 PM, Matt Pavlovich mattr...@gmail.com wrote:
My bad.. the default is s in the ActiveMQ src. This is where you would
specify ssl or not. I think the
Are you getting the exact same exception? Your original exception cause
shows a null value for a key in that config:
Caused by: java.io.IOException: Configuration Error:
Line 6: expected [option key], found [null]
at com.sun.security.auth.login.**ConfigFile.match(ConfigFile.**java:577)
at
Yeah, it's the exact same exception.
On Wed, Feb 1, 2012 at 12:55 PM, Matt Pavlovich mattr...@gmail.com wrote:
Are you getting the exact same exception? Your original exception cause
shows a null value for a key in that config:
Caused by: java.io.IOException: Configuration Error:
Line 6:
How comfortable are you with Java? The next step to try would be to
write up a quick Java unit test that has the ConfigFile class try to
intialize against your login.config file.
See:
com.sun.security.auth.login.ConfigFile
On 2/1/12 1:59 PM, Chris Robison wrote:
Yeah, it's the exact same
I can do that. I'll let you know.
On Wed, Feb 1, 2012 at 1:19 PM, Matt Pavlovich mattr...@gmail.com wrote:
How comfortable are you with Java? The next step to try would be to write
up a quick Java unit test that has the ConfigFile class try to intialize
against your login.config file.
See:
Chris-
I whipped up a quick unit test, and this passed. I set the
connectionProtocol=s, w/o quotes.
ldap-login {
org.apache.activemq.jaas.LDAPLoginModule required
debug=true
initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory
connectionURL=ldap://dc101.cdr.corp;
When I run it, I still get the error.
On Wed, Feb 1, 2012 at 1:32 PM, Matt Pavlovich mattr...@gmail.com wrote:
Chris-
I whipped up a quick unit test, and this passed. I set the
connectionProtocol=s, w/o quotes.
ldap-login {
org.apache.activemq.jaas.**LDAPLoginModule required
The error says line 6 which in my login.config is connectionUsername.
Chris
On Wed, Feb 1, 2012 at 1:42 PM, Chris Robison chrisdrobi...@gmail.comwrote:
When I run it, I still get the error.
On Wed, Feb 1, 2012 at 1:32 PM, Matt Pavlovich mattr...@gmail.com wrote:
Chris-
I whipped up a
Ah, start w/ line 0.. that puts it at connectionPassword. Try adding
around Password!. The exclamation point may be throwing it off.
On 2/1/12 2:47 PM, Chris Robison wrote:
The error says line 6 which in my login.config is connectionUsername.
Chris
On Wed, Feb 1, 2012 at 1:42 PM, Chris
the broker creates the queue and it uses broker credentials, these
bypass authorization, so they are like super user.
On 1 February 2012 14:21, Zagan erbsen.fr...@gmail.com wrote:
Hello,
I have an Active MQ broker secured with Username/Password through the use of
simpleAuthenticationPlugin and
Sweet! Now I'm getting an LDAP error, which is progress.
On Wed, Feb 1, 2012 at 1:56 PM, Matt Pavlovich mattr...@gmail.com wrote:
Ah, start w/ line 0.. that puts it at connectionPassword. Try adding
around Password!. The exclamation point may be throwing it off.
On 2/1/12 2:47 PM, Chris
Glad to hear :-)
On 2/1/12 3:00 PM, Chris Robison wrote:
Sweet! Now I'm getting an LDAP error, which is progress.
On Wed, Feb 1, 2012 at 1:56 PM, Matt Pavlovichmattr...@gmail.com wrote:
Ah, start w/ line 0.. that puts it at connectionPassword. Try adding
around Password!. The
Would it be simpler to use different table names for each pair. So
just set the tablePrefix on the statements element in xml
configuration.
On 31 January 2012 18:34, mikmela mikm...@yahoo.com wrote:
As it was mentioned in
+1 Cut out a where clause will speed it up
On 2/1/12 3:10 PM, Gary Tully wrote:
Would it be simpler to use different table names for each pair. So
just set the tablePrefix on the statements element in xml
configuration.
On 31 January 2012 18:34, mikmelamikm...@yahoo.com wrote:
As it was
Hello,
I have set up a static NC between two brokers of Version 5.5.1, and we have
now seen twice within our preproduction test that the connection was lost
and not reestablished automatically. We could not establish it through JMX
using the NC's start operation but had to restart one or both
Nevermind, I found my answer in the FAQs.
On Wed, Feb 1, 2012 at 6:38 PM, Chris Robison chrisdrobi...@gmail.comwrote:
In my journey to integrate with an LDAP system, I've noticed there are a
few extra features on the current Fuse broker release when compared to the
current Apache release. I
24 matches
Mail list logo
