Please document that jetty > 7.6.2 probably doesn't work with Priam

[netflix]

Please document that jetty > 7.6.2 probably doesn't work with Priam

[pcn]

It seems that using jetty-7.6.2 only gets you so far. Trying to run a backup via jetty results in a stracktrace like so:

INFO: Binding com.netflix.priam.resources.CassandraConfig to GuiceInstantiatedComponentProvider
 INFO 21:45:30,112 Starting snapshot 201206272145
 INFO 21:45:31,283 Uploading to backup/us-east-1//102084710076281539039012382231339039035/201206272145/META/meta.json with chunk size 10485760
Jun 27, 2012 9:45:31 PM com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException
SEVERE: The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container
java.lang.UnsatisfiedLinkError: org.xerial.snappy.SnappyNative.maxCompressedLength(I)I
        at org.xerial.snappy.SnappyNative.maxCompressedLength(Native Method)
        at org.xerial.snappy.Snappy.maxCompressedLength(Snappy.java:220)
        at org.xerial.snappy.SnappyOutputStream.<init>(SnappyOutputStream.java:72)
        at org.xerial.snappy.SnappyOutputStream.<init>(SnappyOutputStream.java:65)
        at com.netflix.priam.compress.ChunkedStream.<init>(ChunkedStream.java:27)
        at com.netflix.priam.compress.SnappyCompression.compress(SnappyCompression.java:24)
        at com.netflix.priam.aws.S3FileSystem.upload(S3FileSystem.java:132)
        at com.netflix.priam.backup.MetaData$2.retriableCall(MetaData.java:107)
        at com.netflix.priam.backup.MetaData$2.retriableCall(MetaData.java:103)
        at com.netflix.priam.utils.RetryableCallable.call(RetryableCallable.java:42)
        at com.netflix.priam.backup.MetaData.upload(MetaData.java:102)
        at com.netflix.priam.backup.MetaData.set(MetaData.java:61)
        at com.netflix.priam.backup.SnapshotBackup.execute(SnapshotBackup.java:66)
        at com.netflix.priam.resources.BackupServlet.backup(BackupServlet.java:81)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
        at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
        at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
        at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)

and more.

Simply put, jetty appears to not work for Priam. Running the same command with the same war on the same host using tomcat-6 results in no backtrace.

[jhohertz]

Just wanted to mention that this is still a relevant issue, has to do with how Jetty's classloader works, and how Snappy is making use of a JNI interface.

Moving the snappy jar file from WEB-INF/lib to jetty's lib/ext folder works around the issue successfully.