On RHEL4, you need to use the -L option of ps to see threads:
ps -AL
BillOn 9/29/06, Swaminathan Subramanian [EMAIL PROTECTED] wrote:
Hello!I am running Resin 3.0 on Linux (RHE 4). My resin.conffor threads is as follows:thread-pool!-- Maximum number of threads.--thread-max500/thread-max
!--
I ended up writing my own authenticator extending Caucho's
AbstractAuthenticator
because I need to use ldaps and need some custom functionality.
Things should work if the default PROVIDER_URL is good for you (ie
ldap://localhost:389).
Bill
On 5/3/07, Riccardo Cohen [EMAIL PROTECTED] wrote:
Hi
find this ?
Bill Au wrote:
I ended up writing my own authenticator extending Caucho's
AbstractAuthenticator
because I need to use ldaps and need some custom functionality.
Things should work if the default PROVIDER_URL is good for you (ie
ldap://localhost:389).
Bill
On 5/3/07, *Riccardo
In 3.0.x, the server mbean has a clearCache() and a clearCacheByPattern(host,
url) method in com.caucho.server.resin.mbean.ServletServerMBean. The name
of the mbean should be resin:type=Server,name=default
Bill
On 5/31/07, Bernard Bernstein [EMAIL PROTECTED] wrote:
We are using the Resin
With the SSL port set up in Resin, relative redirect on a https request
should go to the SSL port. Is that not the case?
Bill
On 6/1/07, Michael Fortin [EMAIL PROTECTED] wrote:
Hello,
We have our servers setup behind a load balancer and the load balancer
does all the encryption for ssl.
.
Thanks again,
Michael
Bill Au wrote:
With the SSL port set up in Resin, relative redirect on a https
request should go to the SSL port. Is that not the case?
Bill
On 6/1/07, *Michael Fortin * [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hello,
We have our servers setup
for the sites themselves.
Bill Au wrote:
watchdog-port
http://www.caucho.com/resin/doc/resin-watchdog.xtp
I also want to run multiple independent instances on the same machine.
Scott and company, I think it will be useful to include an example of that
in the resin 3.1 documentation
Resin does support the trimDirectiveWhitespaces configuration parameter
which is defined in the JSP 2.1 specifications.
http://java.sun.com/developer/technicalArticles/J2EE/jsp_21/
Bill
On Wed, Jun 4, 2008 at 6:05 AM, bisoa [EMAIL PROTECTED] wrote:
It seems like I have to code without white
Take some thread dumps when your CPU utilization is high too see whats'
going on inside that JVM during that time.
Bill
On Thu, Jul 10, 2008 at 4:57 PM, Adam Allgaier [EMAIL PROTECTED] wrote:
We're having stability issues with our app running on Resin, characterized
by climbing memory usage,
With the pro license, you get better performance from both resin and
quercus.
Bill
On Thu, Sep 4, 2008 at 12:52 PM, Rob Lockstone [EMAIL PROTECTED] wrote:
We have a 100 Server Pro license and are very happy with it.
Back in the day, there was no Pro version (as I recall). But as
Resin has
I trick that I use to trouble shoot perm gen memory leak involves using
jconsole and , jmap, and jhat. I would attach to resin with jconsole, then
reload the webapp a few times to trigger the perm gen leak. That I will
stop the webapp completely, and then go to the memory tab to trigger some
I just noticed that the status for JSR313 is now listed as Withdrawn.
What implication does that have on a stable release of 4.0?
Bill
On Thu, May 7, 2009 at 12:02 PM, Scott Ferguson f...@caucho.com wrote:
We've just released Resin 4.0.0 for download at http://caucho.com/download
.
Resin
The command line arguments for starting Resin 4.0.x only applied to the
watchdog and NOT the actual resin process itself. JVM command line
arguments are specified in resin.xml. For example, in the command above,
$JAVA_MX and $JAVA_MS applies to the watchdog only. I wouldn't increase the
default
It is part of resin 4.x. Make sure you have the following in your
resin.xml:
web-app id=/resin-admin root-directory=${resin.root}/doc/admin
prologue
resin:set var=resin_admin_external value=false/
resin:set var=resin_admin_insecure value=true/
/prologue
In addition to admin and resin-doc, I noticed that there is also a config
webapp under doc. Anyone knows what that is for?
Bill
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
PM, Emil Ong e...@caucho.com wrote:
Hi Bill,
I don't see that app. What's in it? Do you see a directory or an MBean
or something else that refers to it?
Thanks,
Emil
On Fri, Apr 16, 2010 at 11:26:28AM -0400, Bill Au wrote:
In addition to admin and resin-doc, I noticed that there is also
I just noticed that the tar balls for resin 4.0.11 is available in Caucho's
download area but the download page still show 4.0.10 as the latest. Is
that just a case of the download page being outdated? Are the 4.0.11 tar
balls official releases?
Bill
Soctt,
Assuming this fix will be in 4.0.16, how soon will that be released?
We are looking to upgrade to Resin 4. I would not want to have to do the
upgrade in 2 steps (first to 4.0.15, and then to 4.0.16 with this fix). How
long is the startup delay anyway?
Bill
On Wed, Mar 2, 2011 at
Just saw that 4.0.16 is now available in the download area. I took a quick
look at Resin Pro 4.0.16. It looks like the old doc directory is now
installed at resin-doc. From Makefile:
mkdir -p $(resin_root)/resin-doc; \
cp -r $(CP_U_FLAG) doc/*
How soon can we expect 4.0.22? I am wondering if I should want for that or
go with 4.0.21 for the time being. We just got hit by bug 4701 again. I
want to pick for the fix for that which is in 4.0.21 but I don't want the
solution to be worse than the problem itself. How wide-reaching is bug
Scott,
What would trigger the JVM bug having to do with the IP addresses? I want
to make sure that I am not affected before I upgrade.
What version of JVM does that affect?
Bill
On Mon, Feb 6, 2012 at 11:34 AM, Scott Ferguson f...@caucho.com wrote:
**
Can you try the snapshot
Out of PermGen space is almost always caused by a classloader leak which
occurs when a webapp is reloaded. It could be caused by either your own
code, third-party code, or in some case Java core classes.
You need to take heap dumps before and after webapp reload and use a heap
analyzer to see
If it is not a leak (classes are being cleaned up upon webapp reload but a
large number is being created), simply increase max perm size.
Bill
On Wed, Apr 25, 2012 at 11:47 PM, Matt White mwh...@leporidae.net wrote:
On 4/24/2012 5:13 PM, Bill Au wrote:
Wow, something I'm actually qualified
This has been fixed in 4.0.31:
http://bugs.caucho.com/view.php?id=5193
As a temporary work-around, you can remove
expand-preserve-fileset=WEB-INF/work/** from your resin.xml. But that
will remove all compiled JSP causing them to be recompiled even if they
have not changed in the new war.
Bill
24 matches
Mail list logo
