Page 1 of 1

Jetty Issue

PostPosted: Fri Oct 14, 2011 2:59 pm
by freaksonic
Hi -

Thanks for the great software. I've been running subsonic for about a year now with no problems. Recently though, I upgraded to 4.5 which seems to have broken jetty in some fantastic way.

The platform: FreeBSD-CURRENT with diablo-jre-1.6.0.07.02_15

The Subsonic Package: standalone-version (all platforms)

The problem: Subsonic execs cleanly using subsonic.sh or through direct command-line execution. When I connect to the configured port, I get a directory listing from a jetty sub-directory ($SUBSONIC_HOME/jetty/####/). I doubt it matters in this instance, but I have confirmed that other software, such as ffmpeg and friends are functioning. One final thing to note is that the web service does not create a log file.

Log Analysis: Here are the last 10 lines from subsonic_sh.log

Code: Select all
[GC 4388K->4078K(5056K), 0.0028530 secs]
[GC 4974K->4638K(5568K), 0.0029550 secs]
[Full GC 4638K->3421K(5568K), 0.0676050 secs]
[GC 4312K->3941K(6664K), 0.0017370 secs]
[GC 4825K->4468K(6664K), 0.0016140 secs]
76852 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Could not detect RMI registry - creating new one
76908 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Binding service 'SubsonicDeployerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[66.148.74.122:9412](local),objID:[0:0:0, 0]]]]
[GC 5358K->4660K(6664K), 0.0023950 secs]
[GC 5556K->4888K(6664K), 0.0039520 secs]


If I roll back to the 4.4 codebase, everything works as expected.

I've read the other posts related to Jetty content errors (404 and the like), but haven't read any applicable solutions.

Re: Jetty Issue

PostPosted: Fri Oct 14, 2011 3:00 pm
by freaksonic
Replying to my own post. After some more debugging, it turns out that rm -Rf of everything in the jetty directory solved the issue. Subsonic built a new directory with updated content and everything works well. I made no changes other than deleting the contents of the $SUBSONIC_HOME/jetty/.

Hopefully this helps others experiencing Jetty errors when accessing Subsonic.

Thanks again for the great software.