[Helma-user] Mysterious crash deploying on Dreamhost

[Phil Hagelberg]

<maksim_lin at ngv.vic.gov.au> writes:

> It might be worth checking what version of java they provide (try on
> the console: java -version) - I seem to remember something simliar
> happenign a while back when I tried running helma with gcj (the
> default java implementation on many linux distributions)

I get this:

$ java -version
java version "1.5.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
Java HotSpot(TM) Server VM (build 1.5.0_02-b09, mixed mode)

That should be fine, right?

> Also while the java jvm is quite memory heavy, helma is actually one
> of the most memory efficient java apps that I have ever used -
> espeically a server-side one and it runs very well on the VPS
> (virtual private server) hosting service that I use. So if it is a
> memory constraint problem on your hosting service I very much doubt
> you will get an java based app that will use less memory then helma.

Yeah, that was pretty much just a wild guess. Since it says "Killed"
it seems it's not a crash within Helma but an outside process that is
stopping it. As far as I know, that generally is caused by abusing
quotas of some kind.

Is using jetty via start.sh the best way to get Helma deployed on a
shared server that doesn't support tomcat?

Thanks for your input. I'll see if I can get any help from the hosting
company.

-Phil Hagelberg
http://technomancy.us