Some additional information: I tried installing 4.0.5 on my better server
(Resin-4.0.0, Nexenta/Open Solaris, recent, lots of RAM, faster CPUs), and got
similar behavior. I got it up and running, noticed some oddness at first (java
link errors running my app, slow page loads the first few times)
I only have one JDK installed.
On Mar 18, 2010, at 21:32:14, Tyson Weihs wrote:
> Are you pointing ./configure to the right JDK installation via
> "--with-java-home=DIR"?
>
> On Thu, Mar 18, 2010 at 11:28 PM, Rick Mann wrote:
> Hmm, configure still reports
>
>checking if Java is 64-bi
Are you pointing ./configure to the right JDK installation via
"--with-java-home=DIR"?
On Thu, Mar 18, 2010 at 11:28 PM, Rick Mann wrote:
> Hmm, configure still reports
>
>checking if Java is 64-bit... no
>
>
> On Mar 18, 2010, at 20:40:38, Tyson Weihs wrote:
>
> > Add "--enable-64bit" w
Hmm, configure still reports
checking if Java is 64-bit... no
On Mar 18, 2010, at 20:40:38, Tyson Weihs wrote:
> Add "--enable-64bit" when calling ./configure.
>
> -tyson
>
> On Thu, Mar 18, 2010 at 10:33 PM, Rick Mann wrote:
> Hi. I'm pretty sure I have a 64-bit java running on my N
Ah! Thank you!
On Mar 18, 2010, at 20:40:38, Tyson Weihs wrote:
> Add "--enable-64bit" when calling ./configure.
>
> -tyson
>
> On Thu, Mar 18, 2010 at 10:33 PM, Rick Mann wrote:
> Hi. I'm pretty sure I have a 64-bit java running on my Nxenta/Open Solaris
> box.
>
>SunOS -- 5.11 Nexe
Add "--enable-64bit" when calling ./configure.
-tyson
On Thu, Mar 18, 2010 at 10:33 PM, Rick Mann wrote:
> Hi. I'm pretty sure I have a 64-bit java running on my Nxenta/Open Solaris
> box.
>
>SunOS -- 5.11 NexentaOS_20081207 i86pc i386 i86pc Solaris
>
> However, when preparing to insta
Hi. I'm pretty sure I have a 64-bit java running on my Nxenta/Open Solaris box.
SunOS -- 5.11 NexentaOS_20081207 i86pc i386 i86pc Solaris
However, when preparing to install resin 4.0.5 on it, I notice the configure
script didn't find 64-bit java. However:
$ java -version
java version "
I have a server that Resin keeps restarting every 15-20 minutes. Where should
we start to look to see what is going on. I just enabled full debug logging so
starting to gather that information. I'd like to know any pointers we should
start looking at once some data is captured.
--
Peter Amiri
F
On Mar 18, 2010, at 16:30:02, Scott Ferguson wrote:
> And it may be better to set the for your older OS to
> something smaller, like 10 or 15, because that OS may not be as good
> with lots of threads.
10
seems to have no effect on the overall stability.
--
Rick
On Mar 18, 2010, at 16:30:02, Scott Ferguson wrote:
> That trace looks normal, assuming the *.216 and *.217 are your two HTTP
> ports. I assume that's the connection-refused state? Each one has
> several threads in the nativeAccept() state. The situation that would be
> a problem is if there
On Mar 18, 2010, at 16:30:02, Scott Ferguson wrote:
> Rick Mann wrote:
>> Hmm, I can't seem to post longer email to the list. Here's a link to my last
>> post:
>>
>> http://pastie.org/private/2c4lrjuj4oybdtzmj4gbzw
>>
> Thanks. There is a size limit for the list.
>
> That trace looks normal,
Rick Mann wrote:
> Hmm, I can't seem to post longer email to the list. Here's a link to my last
> post:
>
> http://pastie.org/private/2c4lrjuj4oybdtzmj4gbzw
>
Thanks. There is a size limit for the list.
That trace looks normal, assuming the *.216 and *.217 are your two HTTP
ports. I assume th
Hmm, I can't seem to post longer email to the list. Here's a link to my last
post:
http://pastie.org/private/2c4lrjuj4oybdtzmj4gbzw
On Mar 18, 2010, at 15:33:08, Rick Mann wrote:
> I replied with the thread dump, but don't see it appearing in the list. Seems
> like the list server is flaky.
>
I replied with the thread dump, but don't see it appearing in the list. Seems
like the list server is flaky.
On Mar 18, 2010, at 14:37:25, Scott Ferguson wrote:
> Rick Mann wrote:
>> Slower is subjective. Unfortunately, I can't currently run the old server to
>> actually measure times, but it's
Rick Mann wrote:
> Slower is subjective. Unfortunately, I can't currently run the old server to
> actually measure times, but it's just slow. I can see individual requests
> (images, CSS, etc) taking a long time to be fulfilled, whereas before, the
> pages would just come up fully rendered.
By the way, the server-dying thing seems to happen within just a couple of
hours after launch. I launched it before lunch, and checked it just now, and it
was dead again.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.cauc
Thanks for getting back to me, Scott! Responses below
On Mar 18, 2010, at 12:37:21, Scott Ferguson wrote:
> Rick Mann wrote:
>> My 4.0.5 install is really very slow. It just won't stay running (although
>> ps shows many resin threads), and it's much, much slower than 3.0.23 was.
>> I'm actually
Rick Mann wrote:
> My 4.0.5 install is really very slow. It just won't stay running (although ps
> shows many resin threads), and it's much, much slower than 3.0.23 was. I'm
> actually running fewer webapps currently, and my server is always idle.
>
How are you measuring the "slower"? (ab? lat
My 4.0.5 install is really very slow. It just won't stay running (although ps
shows many resin threads), and it's much, much slower than 3.0.23 was. I'm
actually running fewer webapps currently, and my server is always idle.
Configuration is slightly different than it used to be, a necessity of
Hi. My new insatll of 4.0.5 is running very badly. My server is basically
unloaded, except for the requests I make, but connections are constantly
dropped. I was running 3.0.23 without any real problems before this. Also, I
don't see anything in any of the logs when this happens.
Any suggestion
20 matches
Mail list logo
