You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (Created) (JIRA)" <ji...@apache.org> on 2012/02/02 08:43:53 UTC
[jira] [Created] (APLO-148) Errors starting Apollo 1.1 snapshot
Errors starting Apollo 1.1 snapshot
-----------------------------------
Key: APLO-148
URL: https://issues.apache.org/jira/browse/APLO-148
Project: ActiveMQ Apollo
Issue Type: Bug
Environment: apollo-1.1-0.20120202.033306.10
Reporter: Lionel Cons
When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
(1) apollo.log contained:
2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
(2) apollo was reporting itself as STARTING instead of STARTED
(3) it could not be (gently) stopped:
# service apollo stop
Gracefully Stopping apollo
Could not stop process 29202
Destroying the data directory fixed the problem.
I had a similar problem in past when using data with a previous version (store-version.txt).
In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-148:
-------------------------------
Fix Version/s: (was: 1.1)
1.2
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
> Fix For: 1.2
>
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-148:
-------------------------------
Fix Version/s: 1.1
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
> Fix For: 1.1
>
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino closed APLO-148.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 1.5)
I've not been able reproduce this issue. Please re-open if you figure a way of how to reproduce.
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-148:
-------------------------------
Fix Version/s: (was: 1.4)
1.5
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
> Fix For: 1.5
>
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-148:
-------------------------------
Fix Version/s: (was: 1.2)
1.3
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
> Fix For: 1.3
>
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-148) Errors starting Apollo 1.1 snapshot
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-148:
-------------------------------
Fix Version/s: (was: 1.3)
1.4
> Errors starting Apollo 1.1 snapshot
> -----------------------------------
>
> Key: APLO-148
> URL: https://issues.apache.org/jira/browse/APLO-148
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-0.20120202.033306.10
> Reporter: Lionel Cons
> Fix For: 1.4
>
>
> When starting the latest Apollo 1.1 snapshot with existing data from a previous 1.1 snapshot, Apollo got hung:
> (1) apollo.log contained:
> 2012-02-02 08:31:02,660 | INFO | Opening the log file took: 577.89 ms | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,904 | WARN | DB operation failed. (entering recovery mode): java.lang.NoClassDefFoundError: org/codehaus/jackson/annotate/JsonClass | org.apache.activemq.apollo.broker.store.leveldb.LevelDBClient | leveldb store io write
> 2012-02-02 08:31:02,959 | INFO | virtual host startup is waiting on store startup | console | hawtdispatch-DEFAULT-1
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: http://0.0.0.0:6100/ | console | Apollo Task
> 2012-02-02 08:31:03,514 | INFO | Administration interface available at: https://0.0.0.0:6101/ | console | Apollo Task
> 2012-02-02 08:31:06,938 | INFO | broker startup is waiting on start virtual-host: apollo | console | hawtdispatch-DEFAULT-1
> (2) apollo was reporting itself as STARTING instead of STARTED
> (3) it could not be (gently) stopped:
> # service apollo stop
> Gracefully Stopping apollo
> Could not stop process 29202
> Destroying the data directory fixed the problem.
> I had a similar problem in past when using data with a previous version (store-version.txt).
> In case of fatal(?) error with the data store, apollo should die loudly instead of hanging.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira