I think it could be related to http://bugs.caucho.com/view.php?id=2941
as I see this error in the logs:
[2008-10-30 09:35:39.569] java.lang.UnsatisfiedLinkError:
com.caucho.vfs.JniFilePathImpl.nativeTruncate([BI)I
[2008-10-30 09:35:39.569] at
Hi,
I'm doing some experiments with Quercus and one of the things I wanted
to do is accessing an already existing web service written in Java. I
also tried implementing the experiments using Zend Framework, even
though that failed, first with a problem I solved by upgrading to 3.1.7
and then
Hello Daniel,
I had success running my project that uses ZF 1.5.2 on top of Quercus,
as it is using PDO, and the Quercus support at that time (dunno know,
I'm not watching its progress) didn't implement some necessary things,
I did implement and so it worked fine.
Which version of ZF were you
I've got a similar experience, but not enough evidence to name a root
cause.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
We are also on REsin 3.1.6. We restart the server each deploy because of
behavior exactly described below.
Possibly unrelated but also strange issue we see is abnormally long re-start
times, on a 2 server cluster where the process is:
kill server 1
deploy war 1
restart server 1... wait long
On Oct 30, 2008, at 6:39 AM, Mattias Jiderhamn wrote:
Although embarrassed to admit it, we have had long standing problems
with PermGen memory leaks. We have gotten used to restarting the
server
every time we redeploy, to avoid OutOfMemoryError. Since we would like
to make use of - or at
+1
On Oct 30, 2008, at 10:36 AM, Jean-Francois Lamy wrote:
I still don't see why old config files stop working. I can still
configure
Log4j using log4j.properties even though there are newer/better
config file
formats. Config files for production sites are tricky, and testing
them
Thanks for the update. A snapshot to vet the changes would be great.
Thanks,
Matt
Scott Ferguson wrote:
On Oct 24, 2008, at 11:40 AM, Matt Pangaro wrote:
Hi,
I was just wondering if we could get a status update on 3.0.27, since
there are a number of fixes in it, plus the newly discovered
