Hi again,
I tested Quercus 3.1.6 on Resin 3.1.5, and the memory leak is still there.
As I'm not using PHP in production, just as a showcase, and it seems
nobody else is affected or cares about the leak, I won't probably be
doing further tests. I just wanted to do these last set of tests in case
Hi list,
I'm using resin-pro-3.0.25 in a three-server cluster with session
persistence configured using a MySQL database:
persistent-store type=jdbc
init
data-sourcejdbc/session/data-source
always-load /
always-save /
/init
PS;
It seems that PHP does not support SoapClient neither!
We have to use third party PHP packages such as nusoap?
Regards.
--
View this message in context:
http://www.nabble.com/SOAP-in-Resin-tp17659264p17894048.html
Sent from the Resin mailing list archive at Nabble.com.
Date: Tue, Jun 17, 2008 at 10:20:12AM +0200
Subject: [Resin-interest] Quercus + Scripting API memory issue [still present
in Quercus 3.1.6]
Hi again,
I tested Quercus 3.1.6 on Resin 3.1.5, and the memory leak is still there.
As I'm not using PHP in production, just as a showcase, and it
I'm using resin-pro-3.0.25 in a three-server cluster with session
persistence configured using a MySQL database:
persistent-store type=jdbc
init
data-sourcejdbc/session/data-source
always-load /
always-save /
/init
/persistent-store
Thanks Sam. I'll give it a go.
Richard Grantham
Development
---
[EMAIL PROTECTED]
Limehouse Software Ltd
DDI: (020) 7566 3336
Main: (020) 7566 3320
Fax: (020) 7566 3321
Limehouse Software Ltd
4th Floor
1 London Bridge
London
SE1 9BG
Manchester Office:
3rd Floor,
Hi
I have a test-server that runs a mix of Resin 2.1.17 and 3.0.23 Pro (havn't had
a reason to upgrade yet) using 2 different Apache 2.2 instances as frontends
for several vhosts on RHEL3u9 (2.4.21-50) with JDK1.6.0_03.
This setup is just fine, and performs as expected for all my
On Jun 17, 2008, at 9:47 AM, Jens Dueholm Christensen wrote:
So far so good, however this also appears in resin-stderr.log at the
same time:
[2008-06-17 16:28:01.507]Exception in thread resin-select-manager
java.io.IOException: failed to add EPOLL for pipe=47 (errno=-1)
[2008-06-17
Hi Scott
That seems to have done the trick!
A bit more digging told me, that epoll(4) was introduced around 2.5.44, so that
was spot on - thanks for the hint!
Apart from the increased usage of sockets (or so I understand it from
Hi,
As we are discussing some other issues, we found a potential serious problem
with jsp:useBean. Basically, if useBean only has the type parameter but not
the class/bean parameters, the resin server will fail because it does not
know what to instantiate, contrary to the spec.
!-- should set
On Jun 17, 2008, at 11:51 AM, Hacking Bear wrote:
Hi,
As we are discussing some other issues, we found a potential serious
problem with jsp:useBean. Basically, if useBean only has the type
parameter but not the class/bean parameters, the resin server will
fail because it does not know
HI List,
I have began to notice some strangeness when deploying my war files to my
production environment.
This is my scenario:
I have a 2 server clustered setup. Resin 3.1.3 pro. Previously, my
deployments for new versions was simply push out the new war file and wait
for the
watchdog to
Hmm... You are correct that this is the behavior described by the real spec.
Even though the JSP reference card on Sun's website clearly state a
different behavior.
http://java.sun.com/products/jsp/syntax/2.0/syntaxref2027.html#8865
I guest we can only blame the reference card. :-)
On Tue,
13 matches
Mail list logo
