Latest official release
Hi, may I know whether the latest official activemq release is 4.0.2? May I know when is the released date of it as well? Thanks -- View this message in context: http://www.nabble.com/Latest-official-release-tf2717760.html#a7577432 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Latest official release
On 11/28/06, nabble615 [EMAIL PROTECTED] wrote: Hi, may I know whether the latest official activemq release is 4.0.2? Currently yes. The 4.1 release is still in voting; its looking good so hopefully should pass in the next day or so May I know when is the released date of it as well? Thanks It was released a few weeks ago http://www.nabble.com/-ANN--Apache-ActiveMQ-4.0.2-released%21-tf2627759.html -- James --- http://radio.weblogs.com/0112098/
[jira] Commented: (AMQCPP-14) CMSExpiration not handled properly in ActiveMQProducer
[ https://issues.apache.org/activemq/browse/AMQCPP-14?page=comments#action_37573 ] Nathan Mittler commented on AMQCPP-14: -- Another issue was found in that the MessageConsumer's receive() method does not seem to take message expiration into account before returning it. After a quick inspection, it appears the .NET client may have the same issue. An example of what should be done is shown in ActiveMQMessageConsumer's dequeue method: https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQMessageConsumer.java CMSExpiration not handled properly in ActiveMQProducer -- Key: AMQCPP-14 URL: https://issues.apache.org/activemq/browse/AMQCPP-14 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 1.0 Environment: All Reporter: Nathan Mittler Assigned To: Nathan Mittler Priority: Minor Fix For: 1.1 Original Estimate: 1 day Remaining Estimate: 1 day ActiveMQProducer.send method is overwriting the CMSExpiration in the message with its default timeToLive value. This is incorrect - it should set the expiry to (expiry + timeToLive). An example of this is in ActiveMQ's ActiveMQSession: https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQSession.java A work-around is to specify the timeToLive value in the producer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37576 ] james strachan commented on AMQ-1054: - Just to make absolutely sure, I've added the test case into the 4.0 branch too https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.0/activemq-test-atomikos/ and the test case works fine. I wonder if these tests fail on a specific platform only? I wonder could someone try running these test cases on Windows (am an OS X / unix person myself) BTW I tried Java 1.4.2 with the 4.0 branch (which is basically 4.0.2) XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1074) support JDBC master slave on MySQL
support JDBC master slave on MySQL -- Key: AMQ-1074 URL: https://issues.apache.org/activemq/browse/AMQ-1074 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 We need to make a few changes to support MySQL's SQL dialect for JDBC Master Slave... http://incubator.apache.org/activemq/jdbc-master-slave.html For details see this thread... http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37578 ] Guy Pardon commented on AMQ-1054: - James, FYI: I am seeing this exactly on OSX/Unix myself. What I can do is upload the whole thing as a ZIP (if you say whereto). Guy XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37579 ] Shoaib Akhtar commented on AMQ-1054: Hi James, It is quite amazing that you cannot reproduce the problem Guy mentioned. Anyhow i am using Sun JDK 1.5.0.9 (most latest update from Sun) on Windows XP (service pack 2) with ActiveMq version 4.0.2 (the latest released version). And the problem comes i do not use linux/unix so not sure about them but on windows it is giving the classcast exception and as i said before there seems bug with activemq code when there is NO Transaction to recover and i am sure though i did not tested that in case ther is any transaction to rceover it well might work. Regards, Shoaib XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37580 ] james strachan commented on AMQ-1054: - Hi Guy Just to be sure - are you saying the bug doesn't happen for you on OSX/Unix? i.e. its a windows only bug? XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37581 ] james strachan commented on AMQ-1054: - Shoaib - I wonder could you try using ActiveMQ trunk (or tomorrows nightly snapshot build of 4.2-SNAPSHOT) to see if I've fixed the bug for you on your environment? I think I've nailed the ClassCastException you're seeing - am just not yet sure of the magic incantations to reproduce it so I can know for sure its fixed XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: (AMQ 992) DefaultDatabaseLocker and mysql
On 11/21/06, slotito [EMAIL PROTECTED] wrote:
Hi,
I am trying to get MySQL to work in the Master/Slave JDBC configuration -
the default sql does not lock the table properly.
I added a MysqlJDBCAdapter that extends
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter so I could
override the lockCreateStatement.
I then edited the resources so that the mysql-ab_jdbc_driver would use the
MysqlJDBCAdapter instead of the DefaultJDBCAdapter.
The new locking statement is: LOCK TABLE ACTIVEMQ_LOCK WRITE (which works
in MySQL 5.x at least)
Unfortunately, once I run it with the new code, it gets stuck in the
following block (from org.apache.activemq.store.jdbc.DefaultDatabaseLocker)
PreparedStatement statement =
connection.prepareStatement(statements.getLockCreateStatement());
while (true) {
try {
log.info(Attempting to acquire the exclusive lock to become
the Master broker);
boolean answer = statement.execute();
if (answer) {
break;
}
}
catch (Exception e) {
if (stopping) {
throw new Exception(Cannot start broker as being asked
to shut down. Interupted attempt to acquire lock: + e, e);
}
log.error(Failed to acquire lock: + e, e);
}
log.debug(Sleeping for + sleepTime + milli(s) before trying
again to get the lock...);
Thread.sleep(sleepTime);
}
Unlike the original SQL (SELECT* FROM ACTIVEMQ_LOCK FOR UPDATE), the lock
table command for Mysql doesn't return a ResultSet. This means that
answer above will always be false, even though the table is successfully
locked, and it basically goes into an infinite loop Attempting to
acquire
(see
http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#execute(java.lang.String))
I see three ways to get this working, but I might be missing something.
I've never contributed anything to this project so I'd like to get some
advice from you guys.
1) I'm pretty sure it is possible to allow multiple queries in a statement
through the use of a connection string parameter (?allowMultiQueries=true)
in the mysql driver - i.e. it would allow LOCK TABLE ACTIVEMQ_LOCK WRITE;
SELECT * FROM ACTIVEMQ_LOCK which would return a ResultSet and set answer
to true. This would just be a documentation effort, basically making sure
anyone using the Master/Slave JDBC configuration with MySQL knows to set
that connection parameter.
2) I could create a MysqlDatabaseLocker and the necessary resource/config
changes, then override that method and remove the answer part. This seems
like overkill since none of the other databases seem to require their own at
this point.
3) I could remove the boolean answer from the DefaultDatabaseLocker. Is it
currently necessary? If there's anything kind of database access error, it
will just throw a SQLException anyway. Other connections will wait for the
lock to become available before they return from the statement.execute(),
right?
Any thoughts on this?
Thanks for this great contribution Steve!
Firstly - I've raised a JIRA to track this issue...
http://issues.apache.org/activemq/browse/AMQ-1074
I agree with 3), I think we should ignore the check for a result set
on the SQL statement. I've made this change in trunk now which should
help. I've also committed your patch to trunk - providing a
MySqlJDBCAdapter which uses the SQL you so kindly submitted for the
exclusive lock. I tried it on my machine with MySQL Connector/J 5.0.4
and it seemed to work great.
I wonder could you see if it works for you? If so we can close the issue.
--
James
---
http://radio.weblogs.com/0112098/
[jira] Commented: (AMQ-1074) support JDBC master slave on MySQL
[ https://issues.apache.org/activemq/browse/AMQ-1074?page=comments#action_37583 ] james strachan commented on AMQ-1074: - Patch applied to trunk - which seems to work for me with MySQL Connector/J 5.0.4. support JDBC master slave on MySQL -- Key: AMQ-1074 URL: https://issues.apache.org/activemq/browse/AMQ-1074 Project: ActiveMQ Issue Type: Improvement Reporter: james strachan Fix For: 4.2.0 We need to make a few changes to support MySQL's SQL dialect for JDBC Master Slave... http://incubator.apache.org/activemq/jdbc-master-slave.html For details see this thread... http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1075) support for FileMessage interface to support in-band and out-of-band file transfer
support for FileMessage interface to support in-band and out-of-band file
transfer
--
Key: AMQ-1075
URL: https://issues.apache.org/activemq/browse/AMQ-1075
Project: ActiveMQ
Issue Type: New Feature
Components: Broker
Reporter: james strachan
Fix For: 4.2.0
Some new API like this...
public class ActiveMQSession {
// send a local file or stream over JMS
public FileMessage createLocalFileMessage(InputStream inputStream) {...}
public FileMessage createLocalFileMessage(File file) {..,}
public FileMessage createLocalFileMessage(URL url) {..,}
// send a remote URL over JMS
public FileMessage createRemoteFileMessage(URL url) {...}
}
with FileMessage like this...
public interface FileMessage extends Message {
// access the remote resource
// or for local resources, force creation of temporary file
// so this resource can be parsed multiple times etc
URL getURL();
InputStream getInputStream();
}
For further discussion see
http://www.nabble.com/support-for-FileMessage--tf2641673.html#a7373916
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37586 ] Shoaib Akhtar commented on AMQ-1054: Hi James, Sorry i could not see your post before i posted my comment. If it is fixed may i ask whats the timeline for it releasing as it seems to be quite a major bug. Best Regards and Thanks, Shoaib XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ] james strachan resolved AMQ-1054. - Fix Version/s: 4.2.0 Resolution: Fixed Aha! So the reason the test case was working that I checked into trunk and 4.0 branch was due to the fact that the test was using the VM transport - which tends to avoid mashalling to and from a socket, so not causing the bug. Have patched the test case both in trunk and in the 4.0 branch. The one in the 4.0 branch now does indeed fail with the ClassCastException. The one in trunk passes with flying colours. So this issue is now resolved and will go out as part of the 4.2 release. If we cut a 4.1.x bug fix release this fix can be back ported for that too XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37589 ] james strachan commented on AMQ-1054: - Have backported the test case and fix to 4.1 branch too if we release a new bug fix release of 4.1 before 4.2 XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Heap overflow after consumer closes
This is with the Kaha store and the store durable pending cursor. Messages size is 10 kilobytes. Heap size set to 512MB. activemq.xml configured for 100 MB. 1. Start a consumer for a durable topic and stop it immediately. 2. Wait until 5 messages have been enqueued. 3. Start the producer for the durable topic (leave it running for remainder of test). 4. Restart the consumer from Step #1, have it consume 8000 messages. 5. Once the consumer has ended, heap usage will rise until out of heap (forcing GC does not affect). UsageManager only indicates approx 1% memory usage, so this leak is outside of what UsageManager monitors. Memory usage was about 80 MB at the time the consumer closed, and rose to 500 MB within one minute of the consumer closing. -- View this message in context: http://www.nabble.com/Heap-overflow-after-consumer-closes-tf2722488.html#a7592496 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1
[ https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37597 ] Shoaib Akhtar commented on AMQ-1054: Hi James, Thanks for the fixed bug and thanks to Guy Pardon as well for reporting this issue. Last nigh i saw the patch you applied and i think though still not able to check that it should be working but the patch code seems to be a little hack i think it can be improved and that too not in TransactionContext anyhow it is still great that this bug is fixed. Great work ActiveMq team, its is a great and extremely cool messaging system. Cheers ! Regards, Shoaib Akhtar XA recover fails for 4.0.1 -- Key: AMQ-1054 URL: https://issues.apache.org/activemq/browse/AMQ-1054 Project: ActiveMQ Issue Type: Bug Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials for the JTA/XA part Reporter: Guy Pardon Fix For: 4.2.0 Attachments: pom.xml XAResource.recover seems to fail for 4.x of ActiveMQ: ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 [Lorg.apache.activemq.command.DataStructure; [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I borrowed this stack trace from). We have seen similar things in other applications that tried to use ActiveMQ. I think this is a class cast error in ActiveMQ... With 3.1 there is no problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1070) Deadlock in Queue.java
[ https://issues.apache.org/activemq/browse/AMQ-1070?page=all ] Rob Davies resolved AMQ-1070. - Fix Version/s: 4.2.0 Resolution: Fixed Locking behaviour has changed for 4.2 - can now longer reproduce this Deadlock in Queue.java -- Key: AMQ-1070 URL: https://issues.apache.org/activemq/browse/AMQ-1070 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2 Reporter: Tom Kaitchuck Assigned To: Rob Davies Fix For: 4.2.0 It is possible to have a deadlock as follows: ActiveMQ Transport: tcp:///127.0.0.1:53335: at org.apache.activemq.broker.region.PrefetchSubscription.add(PrefetchSubscription.java:66) - waiting to lock 0x90786240 (a org.apache.activemq.broker.region.QueueSubscription) at org.apache.activemq.broker.region.Queue.addSubscription(Queue.java:192) - locked 0x908fa480 (a java.util.LinkedList) at org.apache.activemq.broker.region.AbstractRegion.addDestination(AbstractRegion.java:93) - locked 0x903b9b40 (a java.lang.Object) at org.apache.activemq.broker.region.RegionBroker.addDestination(RegionBroker.java:221) at org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:130) at org.apache.activemq.advisory.AdvisoryBroker.addDestination(AdvisoryBroker.java:142) at org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:130) at org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBrokerFilter.java:143) at org.apache.activemq.broker.region.AbstractRegion.addConsumer(AbstractRegion.java:182) - locked 0x908e6cb8 (a java.lang.Object) at org.apache.activemq.broker.region.RegionBroker.addConsumer(RegionBroker.java:297) at org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:74) at org.apache.activemq.advisory.AdvisoryBroker.addConsumer(AdvisoryBroker.java:78) at org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:74) at org.apache.activemq.broker.MutableBrokerFilter.addConsumer(MutableBrokerFilter.java:87) at org.apache.activemq.broker.AbstractConnection.processAddConsumer(AbstractConnection.java:538) at org.apache.activemq.command.ConsumerInfo.visit(ConsumerInfo.java:296) at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:237) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:63) at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:67) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:124) at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:123) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:88) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:138) at java.lang.Thread.run(Thread.java:595) ActiveMQ Transport: tcp:///127.0.0.1:53315: at org.apache.activemq.broker.region.Queue.dropEvent(Queue.java:321) - waiting to lock 0x908fa480 (a java.util.LinkedList) at org.apache.activemq.broker.region.Queue.dropEvent(Queue.java:315) at org.apache.activemq.broker.region.QueueSubscription.acknowledge(QueueSubscription.java:54) at org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:125) - locked 0x90786240 (a org.apache.activemq.broker.region.QueueSubscription) at org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:265) at org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:366) at org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:177) at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:66) at org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:66) at org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:79) at org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:445) at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179) at org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:237) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:63) at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:92) at
