Hi activemq devs!!
I'm having a problem with activemq and log4j ...
this is my log4j.properties :
log4j.appender.A1=org.apache.log4j.net.JMSAppender
log4j.appender.A1.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
log4j.appender.A1.ProviderURL=tcp://dllo-aborja
Hi activemq devs!!
I'm having a problem with activemq and log4j ...
this is my log4j.properties :
log4j.appender.A1=org.apache.log4j.net.JMSAppender
log4j.appender.A1.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
log4j.appender.A1.ProviderURL=tcp://dllo-aborja
We are using SSL to allow clients and servers to connect together
with Lingo doing the actual RPC mechanism on top of ActiveMQ (no
persistent store).
I have read http://activemq.apache.org/how-do-i-use-ssl.html and this
is fine is all the certificates are know before the JVM starts up,
bu
When creating a new connection, I am sometimes seeing a hang in
setClientID when it tries to send the info command to the broker. Has
anyone seen this? Any ideas? Thanks.
Id: 18, Name: ***, State: WAITING, Lock:
[EMAIL PROTECTED]
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Unknown
This may seem like a strange question, but what does the ActiveMQ
MemoryManager class actually do, or what is the usage that it tries to
manage?
We have a Lingo application which might get swamped with requests under
certain circumstances. This causes the request queue lengths to grow quite
larg
I ran into this at one time. For me, it was that my ClassLoader was
null for the current thread. But then, I was using JNI and hadnt set
things up properly for myself - which is probably not your problem.
I would imagine you could run into the same problem if your classpath
didn't include acti
Hi all,
Recently I was testing the Java interface to ActiveMQ. Im interested in the
static transport mechanism, specifically, I have a master/slave setup and I
want my code to connect to the master always and on failure, switch to using
the slave server.
I followed this http://activemq.apache
On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
I believe so but maybe it never worked correctly. Maybe I forgot to do
"jms.$PROPERTY" and just did "$PROPERTY" so it never complained about it.
Most likely is we used to just ignore the parameters so it silently
worked :) We should be able to
I believe so but maybe it never worked correctly. Maybe I forgot to do
"jms.$PROPERTY" and just did "$PROPERTY" so it never complained about it.
James.Strachan wrote:
>
> On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> it used to work in v3
>
> Of the C# client? Are you sure?
>
> Note
Hello ActiveMQ Users,
I am using durable topic subscriptions . The
session used is in auto acknowledge mode.
// code segment for session
HerbieSession = (ActiveMQSession) HConn.createSession(false,
Session.AUTO_ACKNOWLEDGE);
Fot the message publishing , the time to l
I have spring jar from amq 4.0.1 distribution (I think spring 1.2.8), but amq
jar is 4.1. Thanks.
--
View this message in context:
http://www.nabble.com/ClassCastException%2C-BrokerId-tf3216115s2354.html#a8950220
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
it used to work in v3
Of the C# client? Are you sure?
Note that the plumbing is in the C# code to deal with URI arguments;
but AFAIK we've not wired in all of the available properties yet. e.g.
DispatchAsync should be supported; though there's
it used to work in v3
James.Strachan wrote:
>
> The C# client doesn't support the various properties that the Java
> client supports
>
> On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> When using the MNS C# client and using the following URL:
>>
>> tcp://localhost:61616?jms.useAsyncSen
The C# client doesn't support the various properties that the Java
client supports
On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
When using the MNS C# client and using the following URL:
tcp://localhost:61616?jms.useAsyncSend=true&jms.dispatchAsync=true
I get an error message that says:
When using the MNS C# client and using the following URL:
tcp://localhost:61616?jms.useAsyncSend=true&jms.dispatchAsync=true
I get an error message that says:
"no such property useasyncsend on class: Connection"
Am I forming the URL correctly?
--
View this message in context:
http://www.nabb
Could be that you have client jars with different version than the
broker? I'm not really sure though...
Vadim Pesochinsky wrote:
Hi all!
Anyone have seen this exception in 4.1.0? I only use Java clients to
commincate with AMQ. Any ideas?
I get a lot of "org.apache.activemq.transport.Inactivi
This is still not enough information for us to go on. Please provide a
sample app that demonstrates the exact problem you are having.
> -Original Message-
> From: penny_hu [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 12, 2007 9:45 PM
> To: users@activemq.apache.org
> Subject: Re
Hi,
AFAIK, binding 2 brokers with same uri will result in a bind exception
because the address is already used. And by the way, using failover is an
assurance that you will be connected to the slave when the master goes down
so there is no point in making the slave and master have the same uri.
18 matches
Mail list logo