[
http://jira.amdatu.org/jira/browse/AMDATU-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10667#comment-10667
]
Ivo Ladage - van Doorn commented on AMDATU-266:
-----------------------------------------------
The problem is that Amdatu was using the Avro deamon while my stand-alone app
was using the Thrift daemon. As Avro is not fully supported yet, Thrift should
still be used. Refactored the cassandra daemon service to use the Thrift daemon
instead.
After fixing this issue it seems that
http://jira.amdatu.org/jira/browse/AMDATU-265 is also resolved
> Cassandra daemon started incorrectly
> ------------------------------------
>
> Key: AMDATU-266
> URL: http://jira.amdatu.org/jira/browse/AMDATU-266
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Cassandra
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> When I tested running Cassandra from a standalone java app I noticed that
> when the daemon is started using:
> new CassandraDaemon().activate();
> this method never returns, but keeps polling for 'stuff to do'. This is
> exactly how the daemon is started in CassandraDaemonServiceImpl.
> If this is really true I cannot image why cassandra would have ever worked,
> but at least this must be investigated.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
