Apache2 Tomcat6 mod_jk

[Codemonkey]

Dear Subsonic Users & Developers,

im using the newest subsonic version on tomcat 6. the tomcat is via mod_jk connected with my apache2 server. => apache is setup to forward all requests comming at <domain>/subsonic to the tomcat (tomcat is running on port 8080).
everything works fine. i can browse my music folders without having the <:8080> port stuff in my url.

but now, when i want to play a file, no matter what player i use (winamp, vlc, yahoo player (...)) , the player fails to connect.

does anyone know why that happens?

Thanks in advance for your help

Regards,
Codemonkey

[Codemonkey]

Hey everybody,

i found the solution by myself. It was just a misconfiguration issue. Now everything works fine.

Thanks,
Codemonkey

[supra92]

Codemonkey....

What was the solution you found, ie the configuration issue? I'd been running Subsonic on the default port 8080 for years, but have recently wanted to shut off port 8080 from the outside world, and thus implemented mod_jk as an interface between Apache2 and Tomcat5.5 so that both of them can exist on port 80, with Apache handling all the requests and passing info to Tomcat as needed.

I thought I had it working, and I believe it does work when I'm at the house, but here at the office I now have the same problem you did --- SS comes up just fine (on port 80), and all the cover art is there, etc. etc... but when I try to play a song, nothing happens. It does claim I'm playing the song over on the right pane's "Now Playing" area (and oddly, keeps adding additional instances of me for each song i play, rather than replacing the prev one).

What did you wind up doing to resolve this?

Cheers!
Supra92

[supra92]

Just to confirm --- everything DOES work fine when I'm playing Subsonic at home inside the network. It's only when I'm outside the network that this happens.

I'm all-too-familiar with the usual firewall protocols (I run iptables on linux, as well as the usual garden-variety router configurations), but to my mind 8080 shouldn't be needed anymore, should it? The theory is that Tomcat runs on 8080 by it's lonesome --- Apache runs on 80 and handles all requests, whilst communicating with Tomcat over that specific port (8009, is it?) via the mod_jk connector.

I may try re-opening up port 8080 to the outside, but I really can't believe that's the issue. Anyone have any ideas on this?

Cheers!
Supra92

[supra92]

Another odd update: on a whim, I re-opened up port 8080 to the outside world, and one of my users is now saying things are playing just fine again with the built-in flash player. Have not verified this myself, but it sounds like it's functional again.

This confuses me however --- I thought the whole idea of mod_jk was so that Tomcat could run on port 8080 only on the server itself, while Apache on port 80 passed all data back and forth to the outside world. If that's the case, why is port 8080 still needed for the outside world?

To recap -- everything re: Subsonic works when only port 80 is open (artist list on left, album art in main screen, etc.) EXCEPT the actual music streaming. Opening port 8080 again seems to allow music streaming to work again.

Have I configured mod_jk incorrectly? Or is there some additional setting I need to do to force the actual music stream to go over 80 and not 8080?

Any help is greatly appreciated...
Supra92

[nullchar]

It must be a configuration issue. I and many others have a local tomcat proxied behind a public apache server with mod_jk. Android and web streaming work great, especially with apache over https.