-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The 1.0 branch doesn't work with cassandra-1.0.10 #44
Comments
Hmmm, I haven't seen this before. We are running the latest build(s) of the 1.0 branch internally here and haven't had problems like the one you are seeing. Also, we're starting to the trunk version for cassandra 1. (in test), as well. Is this the only exception that gets thrown, or are there others? Also, are you adding in any extra jars/config to the webapp? Also, maybe setting the tomcat debugging level really low may help print out some extra info we can use to help debug, |
It's been an active week, and my half-broken priam-1.1 magically recovered 2 nodes that died on Saturday - Hooray! I'm pretty ignorant of java, so I'm 100% sure that I just ran mvn with the recommended flags from the docs. Would the version of Tomcat I'm using matter? |
We're using Tomcat 6.x here, and that has been stable for a long time with Priam. A google search yielded this link :http://stackoverflow.com/questions/6564553/tomcat-6-log4j-1-2-16-java-lang-illegalstateexception-class-invariant-viol . How are you deploying the Priam webapp to Tomcat? Do you bounce tomcat each time, or just redeploy the war to a running Tomcat process? |
I've tried clearing the property referenced in stackoverflow - it gets rid of the invariant error message. In my case that message happens when the server has detected an error and has already unloaded it, so I'm still without priam in this case. My deployment, when testing, is to shut down tomcat6, delete all the state I find in /var/lib/tomcat6/webapp/Priam* and one or two other places I can't recall right now, then replace with a new war and start up tomcat again. When it's died once this seems to be minimum to get a working system. |
It turns out that updating dependencies in maven has fixed this. I assume the gradle script in the current master branch would do the same. Closing. |
What's the last known working version of cassandra, priam, and tomcat? Trying to use the current 1.0 checkout, e49e963, trying to load that into a tomcat6 server results in errors like this:
I'm muddling along with what's in master, but so much is broken that it's not particularly useful.
If there's a last known-good commit that I should be using, I can start from there.
Thanks
-Peter
The text was updated successfully, but these errors were encountered: