Hi all, I've just started to write a small utility to debug
messages withing a KahaDB. Main use case is to offline understand what is
filled in the store
and why logs are not cleaned.
I've started the implementation, but I want to write this utility catching
*all the knowledged that is out ther
In
> other words. they dont apply retrospectively.
>
>
> On 6 December 2012 13:44, RJtokenlanring <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=4660276&i=0>>wrote:
>
>
> > HI, thank you.
> > No, this not worked. File is completely corrupted (
But any plan to fix it? I haven't seen any opened ticket for this issue...
Could anyone answer to this question?
Downgrade is not an option, since there are very critical problems on 5.4.2
with kahadb .log file cleaning.
So should be mandatory to have a fix for this.
--
View this message in con
Tim, there is a plan on how to fix this issue? (AMQ-2935)
Any help is needed in testing?
Regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Fatal-Error-Unable-to-successfully-start-ActiveMQ-5-4-1-Broker-tp2719671p2761810.html
Sent from the ActiveMQ - User mailing li
Issue created:
https://issues.apache.org/activemq/browse/AMQ-2831
Thank you very much
Gary Tully wrote:
>
> you will need to create an account in the issue tracker:
> https://issues.apache.org/activemq/browse/AMQ, there is no restriction
> on account creation.
>
--
View this message in cont
hould be creating a
>> faultolerant connectionInfo, because http is an async transport it has
>> no way of seeing the connection disconnect in this case.
>>
>> On 16 July 2010 10:56, RJtokenlanring
>> wrote:
>>>
>>> //CODE
>>> pub
//CODE
public class TestVaseClientID {
public static void main(String[] args) {
try {
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("user", "default", "http://192.168.100.88:61617";);
Connection
est/java/org/apache/activemq/ReconnectWithSameClientIDTest.java?view=markup
>
>
> On 16 July 2010 09:22, RJtokenlanring wrote:
>>
>> Any update?
>>
>>
>> RJtokenlanring wrote:
>>>
>>> And also.
>>> If I kill all the clients an I
Any update?
RJtokenlanring wrote:
>
> And also.
> If I kill all the clients an I leave active only the broker,
> If I try to reconnect using http (or tcp) I get the same error.
> So client is not de-registered.
> This appens also if I use failover protocol. After client ki
(javax.jms.InvalidClientIDException - with the clientID
of the killed client).
I have to restart broker in order to register again the client.
RJtokenlanring wrote:
>
> Thank you very much. I'll try failover mecanism.
> After some tests I see that the code that I have written works correctly
> with tcp:/
e reconnect will be transparent
> and the broker will be aware of the possibility of a duplicate and
> suppress that exception.
> Otherwise you will need to backoff the reconnect till the broker has a
> chance to recognise and deal with the disconnect
>
> On 15 July 2010 14:25, RJ
Hi all,
I have a client that do a durable subscriptio to a topic.
It register with a static client id.
After a connectivity loss (an so a new re-connection), this exception is
thrown and connection cannot be
re-established:
2010-07-15 13:49:04,700 ERROR - javax.jms.InvalidClientIDException: B
Thank you. writeUTF8 is limited, wryteBytes no.
Thank you very much.
Gary Tully wrote:
>
> there is no hard limit on the transport, but utf is limited to what
> can fit in a short. can u use writeBytes?
>
> On 7 July 2010 16:13, RJtokenlanring wrote:
>>
>> My
it seems this bug:
http://issues.apache.org/activemq/browse/AMQ-1308
BUT I'm using tcp connection
(tcp://192.168.100.88:61616?jms.useCompression=true&keepAlive=true)
with ActiveMQ 5.3.2
It is releated?
Thank you.
RJtokenlanring wrote:
>
> Hi,
> I canno find any information
Hi,
I canno find any information about ByteMessage max size (supported during
transport).
Anyone knows this value?
Thank you
--
View this message in context:
http://old.nabble.com/ByteMessage-MAX-size-tp29097071p29097071.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ancements. I would check that you don't have a durable
> subscriber in your system that was active at some point - but is no loner
> - you can use JMX to do this
>
>
>
> On 2 Jul 2010, at 09:51, RJtokenlanring wrote:
>
>>
>> Hi all,
>> I have a q
hank you very much. I have updated to version 5.3.2. Now I'll monitor the
situation.
I'll also check via JMX the subscriber list. But the only subscriber are the
MDBs and all the MDBs are defined as follow:
@ActivationConfigProperty(propertyName = "destinationType", propertyValue =
"javax.jms.Top
Hi all,
I have a question on kahadb and .log files.
It seems that in case of Topic destination, .log files into kahaDB folder
are not
cleaned up correctly.
Here is the content of the directory
drwxrwxr-x 3 user1 user1 4.0K Dec 11 2009 ..
-rw-rw-r-- 1 user1 user1 33M Dec 15 2009 db-1.log
-rw
Hi, I'm using AMQ 5.3.0 and I see that there are a lot of .log files into
kahadb data directory.
Every message has a TTL with 1 hour of expire time and a DLQ is present and
consumed.
What's wrong? These log can be safely deleted?
Best regards
--
View this message in context:
http://old.nabble
Call tags are placed into jetty.xml configuration file.
This file is imported from the broker-config.xml file and used for activemq
configuration.
Thank you for the response
--
View this message in context:
http://old.nabble.com/HTTPS-configuration---HELP%21-tp26628876p26845928.html
Sent from
Hi, I have switched to apacheMQ 5.3.
This new error ir raised (that wasn't present before)
[org.apache.activemq.ra.ServerSessionImpl:42] Endpoint failed to process
message. Reason: null
ActiveMq 5.3 + JBoss 4.2.3
This is raised from a MDB:
@MessageDriven(activationConfig ={
@ActivationConfigP
Default apache-mq 5.3.0 comes with a non properly confgured https support.
If a user enables https transport into activemq.xml configuration file,
https://0.0.0.0:61617"/>
process enter in an infinite loop (as described into jetty docs).
Could you provide a working https configuration?
Thank
Hi all, I've followed all the threads and configurations guide for
configuring HTTPS support
(activeMQ 5.3.0 + JBOSS)
I have activated jetty.xml file into broker-config.xml
and configured jetty.xml as follow:
..
Resolved: correct parametres is ...propertyName = "userName"
--
View this message in context:
http://old.nabble.com/EJB3-authentication-issue-tp26611052p26611656.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi all,
I have some problems with authentication.
I've configured the authentication with AMQ 5.3 + JBOSS. How can I
authenticate my MDBs??
I've tested with the standard annotations:
@ActivationConfigProperty(propertyName = "user", propertyValue =
"admin"),
@ActivationConfigPr
Thank you for the response. I've already checked, but the returned factory is
null:
I've used:
url: jnp://127.0.0.1:1099
factory: org.jnp.interfaces.NamingContextFactory
context.factory: activemq/TopicConnectionFactory
TopicConnectionFactory factory = (TopicConnectionFactory)
context.lookup("act
Hi, after integrating activeMQ into JBOSS, I've tried the JNDI lookup. I
followed the istructions from:
http://activemq.apache.org/jndi-support.html
but I have some problems. Here is the error:
ERROR [main] - javax.naming.NameNotFoundException: topic/RawDataTopic
when i try: Topic topic = (Topic
Hi, I have integrated activeMQ 5.3 into Jboss 4.2.3. It works fine with tcp
and vm tranport.
But I now I have to configure HTTP and HTTP tansport. I've seen that http
transport is done via Jetty server: there is no way to use the provided
JBoss tomcat?
Could you provide me a broker-config.xml th
28 matches
Mail list logo