[jira] Commented: (AMQ-2826) Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra
[ https://issues.apache.org/activemq/browse/AMQ-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60808#action_60808 ] Scott Clasen commented on AMQ-2826: --- Ok, so I was able to get the adapter to build and test under JDK 1.5 with a bunch of wrestling. Not sure this is the way to go anyhow, since this would rely on an external cassandra instance to do testing, and would also be generally more of a maintenence burden. Here are the steps I needed to take. Generate cassandra thrift java sources from the thrift idl, pull into project (could be an external dependency, but need to compile with jdk1.5) Fix some blood where generated code was attempting to assign an int instead of an Enum Type. Pull BloomFilter and a few dependent sources from cassandra into project, remove serialization code that ties it to cassandra too strongly. (Could use another bloomFilter impl or another duplicate detection strategy) remove two usages of String.getBytes(Charset) and new String(bytes, Charset) which were added in 1.6 from Cascal (scala cassandra library used in the adapter), build cascal with jdk 1.5 (skipping tests, since the rely on an embedded cassandra instance) install cassandra (actually worked with 0.6.3 even though the thrift api was 0.6.1), configure broker keyspace, remove adapter test code that relied on embedded cassandra instance, build and test under jdk 1.5 Sooo, while it is possible to get it working under 1.5, it dosen't feel very good from a future maintainability and development perspective. Thoughts? > Look at the possibility of incorporating a cassandra persistence adapter from > http://github.com/ticktock/qsandra > - > > Key: AMQ-2826 > URL: https://issues.apache.org/activemq/browse/AMQ-2826 > Project: ActiveMQ > Issue Type: New Feature > Components: Message Store >Affects Versions: 5.3.2 >Reporter: Scott Clasen > > I am the author of http://github.com/ticktock/qsandra, which is a cassandra > persistence adapter for activemq. I am willing to donate it if it is > something that is of interest to ActiveMQ.. > Only current trouble with that is it needs JDK 1.6, so it would probably need > to wait until (if and when) ActiveMQ 5.x is built with JDK 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2826) Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra
[ https://issues.apache.org/activemq/browse/AMQ-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60700#action_60700 ] Scott Clasen commented on AMQ-2826: --- Could take that jdk 1.6 profile a step further, and have a seperate profile where the whole module is included only in the 1.6 profile Sort of like ...normal modules... org.apache.maven.plugins maven-compiler-plugin 1.5 1.5 1.5 jdk1.6 1.6 .all normal modles... activemq-cassandra-store org.apache.maven.plugins maven-compiler-plugin 1.6 1.6 1.6 OR just have the module sit off to the side in svn, like activemq-blaze or activemq-protobuf In the meantime I'll create a branch and pull in the cassandra thrift sources and try and build against 1.5 and run the tests against an external cassandra instance > Look at the possibility of incorporating a cassandra persistence adapter from > http://github.com/ticktock/qsandra > - > > Key: AMQ-2826 > URL: https://issues.apache.org/activemq/browse/AMQ-2826 > Project: ActiveMQ > Issue Type: New Feature > Components: Message Store >Affects Versions: 5.3.2 >Reporter: Scott Clasen > > I am the author of http://github.com/ticktock/qsandra, which is a cassandra > persistence adapter for activemq. I am willing to donate it if it is > something that is of interest to ActiveMQ.. > Only current trouble with that is it needs JDK 1.6, so it would probably need > to wait until (if and when) ActiveMQ 5.x is built with JDK 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2826) Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra
[ https://issues.apache.org/activemq/browse/AMQ-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60684#action_60684 ] Scott Clasen commented on AMQ-2826: --- So any suggestions on how to proceed? The maven profile for now could simply prevent the tests from being run... Not sure what type of infrastructure is available in the CI environment, as far as having the ability to stand up a single node cassandra and zookeeper instance to run the tests agains at some point... How is the JDBC Store tested against all the different vendors that are supported? > Look at the possibility of incorporating a cassandra persistence adapter from > http://github.com/ticktock/qsandra > - > > Key: AMQ-2826 > URL: https://issues.apache.org/activemq/browse/AMQ-2826 > Project: ActiveMQ > Issue Type: New Feature > Components: Message Store >Affects Versions: 5.3.2 >Reporter: Scott Clasen > > I am the author of http://github.com/ticktock/qsandra, which is a cassandra > persistence adapter for activemq. I am willing to donate it if it is > something that is of interest to ActiveMQ.. > Only current trouble with that is it needs JDK 1.6, so it would probably need > to wait until (if and when) ActiveMQ 5.x is built with JDK 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2826) Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra
[ https://issues.apache.org/activemq/browse/AMQ-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60678#action_60678 ] Scott Clasen commented on AMQ-2826: --- Gary- The 1.6 dependency is more of a dependency for testing. Cassandra itself requires 1.6, and the unit tests use an embedded cassandra server as the backend. They could be easily made to run against an external instance, but that complicates the build, maybe they could be constrained to run only against a certain maven profile? Other than that the persistence adapter uses only the cassandra thrift interface, and also a BloomFilter from Cassandra. Both the thrift interface and the bloom filter could be extracted and compiled under 1.5...I think Thoughts? > Look at the possibility of incorporating a cassandra persistence adapter from > http://github.com/ticktock/qsandra > - > > Key: AMQ-2826 > URL: https://issues.apache.org/activemq/browse/AMQ-2826 > Project: ActiveMQ > Issue Type: New Feature > Components: Message Store >Affects Versions: 5.3.2 >Reporter: Scott Clasen > > I am the author of http://github.com/ticktock/qsandra, which is a cassandra > persistence adapter for activemq. I am willing to donate it if it is > something that is of interest to ActiveMQ.. > Only current trouble with that is it needs JDK 1.6, so it would probably need > to wait until (if and when) ActiveMQ 5.x is built with JDK 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQ-2826) Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra
Look at the possibility of incorporating a cassandra persistence adapter from http://github.com/ticktock/qsandra - Key: AMQ-2826 URL: https://issues.apache.org/activemq/browse/AMQ-2826 Project: ActiveMQ Issue Type: New Feature Components: Message Store Affects Versions: 5.3.2 Reporter: Scott Clasen I am the author of http://github.com/ticktock/qsandra, which is a cassandra persistence adapter for activemq. I am willing to donate it if it is something that is of interest to ActiveMQ.. Only current trouble with that is it needs JDK 1.6, so it would probably need to wait until (if and when) ActiveMQ 5.x is built with JDK 6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2245) Allow restart of embedded broker
[
https://issues.apache.org/activemq/browse/AMQ-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59594#action_59594
]
Scott Clasen commented on AMQ-2245:
---
I see the same stack trace today in 5.3.1 after trying to force start a
BrokerService that was stopped. Is there a way to replace the ErrorBroker?
> Allow restart of embedded broker
>
>
> Key: AMQ-2245
> URL: https://issues.apache.org/activemq/browse/AMQ-2245
> Project: ActiveMQ
> Issue Type: Improvement
>Affects Versions: 5.2.0
>Reporter: Dejan Bosanac
>Assignee: Dejan Bosanac
> Fix For: 5.3.0
>
> Attachments: ActiveMQThreadBrokerFactory.java
>
>
> Currently we don't allow restarting the stopped broker and instead developers
> need to create another instance of the broker and start it. Usually this is a
> desired behavior and should remain a default one. But we should provide an
> option to people wanting to start stopped brokers. The proposed enhancement
> will introduce
> {code}
> public void start(boolean force);
> {code}
> method, which will force the broker to start.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2306) Unable to monitor or manage slave brokers in shared filesystem master slave configuration
[ https://issues.apache.org/activemq/browse/AMQ-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Clasen updated AMQ-2306: -- Description: It appears that when running in shared master slave configuration one cant connect to the jmx console or use activemq-admin to stop the slave. Start a slave with a master running ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 Loading message broker from: xbean://itdept//messagebroker/activemq-config/broker3.xml INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) WARN AMQPersistenceAdapter - Waiting to Lock the Store /datafiles/itdept/activemq-journal Notice that no connections including jmx have been started...attempts to stop the broker with activemq-admin fail with..Caused by: java.net.ConnectException: Connection refused Kill the master and get INFO AMQPersistenceAdapter - Aquired lock for AMQ Store/datafiles/itdept/activemq-journal INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker (messagebroker3) is starting INFO BrokerService - For help or more information please see: http://activemq.apache.org/ INFO KahaStore - Kaha Store using data directory /datafiles/itdept/activemq-journal/kr-store/data INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi INFO TransportServerThreadSupport - Listening for connections at: tcp://0.0.0.0:3 INFO TransportConnector - Connector tcp Started INFO BrokerService - ActiveMQ JMS Message Broker (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started INFO log- Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog INFO log- jetty-6.1.9 INFO log- web...@1288520654 at http://0.0.0.0:55573/admin INFO log- Started selectchannelconnec...@0.0.0.0:55573 Now you can connect via JMX and concole brokers are very simply configured... broker3 broker 4 was: It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 Loading message broker from: xbean://itdept//messagebroker/activemq-config/broker3.xml INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) WARN AMQPersistenceAdapter - Waiting to Lock the Store /datafiles/itdept/activemq-journal Notice that no connections including jmx have been started...attempts to stop the broker with activemq-admin fail with..Caused by: java.net.ConnectException: Connection refused Kill the master and get INFO AMQPersistenceAdapter - Aquired lock for AMQ Store/datafiles/itdept/activemq-journal INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker (messagebroker3) is starting INFO BrokerService - For help or more information please see: http://activemq.apache.org/ INFO KahaStore - Kaha Store using data directory /datafiles/itdept/activemq-journal/kr-store/data INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi INFO TransportServerThreadSupport - Listening for connections at: tcp://0.0.0.0:3 INFO TransportConnector - Connector tcp Started INFO BrokerService - ActiveMQ JMS Message Broker (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started INFO log- Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog INFO log- jetty-6.1.9 INFO log- web...@1288520654 at http://0.0.0.0:55573/admin INFO log- Started selectchannelconnec...@0.0.0.0:55573 Now you can connect via JMX and concole brokers are very simply configured... broker3 broker 4 > Unable to monitor or manage slave brokers in shared filesystem master slave > configuration > - > >
[jira] Updated: (AMQ-2306) Unable to monitor or manage slave brokers in shared filesystem master slave configuration
[ https://issues.apache.org/activemq/browse/AMQ-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Clasen updated AMQ-2306: -- Description: It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 Loading message broker from: xbean://itdept//messagebroker/activemq-config/broker3.xml INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) WARN AMQPersistenceAdapter - Waiting to Lock the Store /datafiles/itdept/activemq-journal Notice that no connections including jmx have been started...attempts to stop the broker with activemq-admin fail with..Caused by: java.net.ConnectException: Connection refused Kill the master and get INFO AMQPersistenceAdapter - Aquired lock for AMQ Store/datafiles/itdept/activemq-journal INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker (messagebroker3) is starting INFO BrokerService - For help or more information please see: http://activemq.apache.org/ INFO KahaStore - Kaha Store using data directory /datafiles/itdept/activemq-journal/kr-store/data INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi INFO TransportServerThreadSupport - Listening for connections at: tcp://0.0.0.0:3 INFO TransportConnector - Connector tcp Started INFO BrokerService - ActiveMQ JMS Message Broker (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started INFO log- Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog INFO log- jetty-6.1.9 INFO log- web...@1288520654 at http://0.0.0.0:55573/admin INFO log- Started selectchannelconnec...@0.0.0.0:55573 Now you can connect via JMX and concole brokers are very simply configured... broker3 broker 4 was: It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running > Unable to monitor or manage slave brokers in shared filesystem master slave > configuration > - > > Key: AMQ-2306 > URL: https://issues.apache.org/activemq/browse/AMQ-2306 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMX >Affects Versions: 5.2.0 >Reporter: Scott Clasen > > It appears that when running in shared master slave configuration one cant > connect to the jmx console or user activemq-admin to stop the slave. > Start a slave with a master running > ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 > ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 > Loading message broker from: > xbean://itdept//messagebroker/activemq-config/broker3.xml > INFO BrokerService - Using Persistence Adapter: > AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) > WARN AMQPersistenceAdapter - Waiting to Lock the Store > /datafiles/itdept/activemq-journal > Notice that no connections including jmx have been started...attempts to stop > the broker with activemq-admin fail with..Caused by: > java.net.ConnectException: Connection refused > Kill the master and get > INFO AMQPersistenceAdapter - Aquired lock for AMQ > Store/datafiles/itdept/activemq-journal > INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker > (messagebroker3) is starting > INFO BrokerService - For help or more information please > see: http://activemq.apache.org/ > INFO KahaStore - Kaha Store using data directory > /datafiles/itdept/activemq-journal/kr-store/data > INFO ManagementContext - JMX consoles can connect to > service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi > INFO TransportServerThreadSupport - Listening for connections at: > tcp://0.0.0.0:3 > INFO TransportConnector - Connector tcp Started > INFO BrokerService - ActiveMQ JMS Message Broker > (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started > INFO log- Logging to > org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog > INFO log
[jira] Created: (AMQ-2306) Unable to monitor or manage slave brokers in shared filesystem master slave configuration
Unable to monitor or manage slave brokers in shared filesystem master slave configuration - Key: AMQ-2306 URL: https://issues.apache.org/activemq/browse/AMQ-2306 Project: ActiveMQ Issue Type: Bug Components: Broker, JMX Affects Versions: 5.2.0 Reporter: Scott Clasen It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1871) activemq wrapper shell script missing from bin/linux-x86-64 and bin/linux-x86-32 of the 5.1.0 distro. (tar.gz version)
[ https://issues.apache.org/activemq/browse/AMQ-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44595#action_44595 ] Scott Clasen commented on AMQ-1871: --- also, the wrapper.java.library.path.1= in the wrapper.conf in each of the 2 linux subdirectories points to a nonexistent directory. > activemq wrapper shell script missing from bin/linux-x86-64 and > bin/linux-x86-32 of the 5.1.0 distro. (tar.gz version) > -- > > Key: AMQ-1871 > URL: https://issues.apache.org/activemq/browse/AMQ-1871 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.1.0 >Reporter: Scott Clasen > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQ-1871) activemq wrapper shell script missing from bin/linux-x86-64 and bin/linux-x86-32 of the 5.1.0 distro. (tar.gz version)
activemq wrapper shell script missing from bin/linux-x86-64 and bin/linux-x86-32 of the 5.1.0 distro. (tar.gz version) -- Key: AMQ-1871 URL: https://issues.apache.org/activemq/browse/AMQ-1871 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.1.0 Reporter: Scott Clasen -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
