Your JVM is definitely not 64-bit.
Your OS may be : http://opensolaris.org/jive/thread.jspa?threadID=119527
Run this : isainfo -kv
Didn't anyone tell you Opensolaris was dead? :)
http://insidehpc.com/2010/08/16/opensolaris-dead-at-age-19/
File size should be independent of CPU
Scott, any insight?
Comment from our engineer below. This is resin 3.0 if it makes a difference.
For the persistent session, the timeout is based on access time. So each
new request resets the timer for the default 30min.
Is he referring to the actual session object on the server or
Where is the standard for persistent-cookie lifetimes? Do they expire based on
the time of first creation or does the cookie expiration time update to a new
value on each page request? Thanks,
___
resin-interest mailing list
Comment from our engineer below. This is resin 3.0 if it makes a difference.
For the persistent session, the timeout is based on access time. So each new
request resets the timer for the default 30min.
Is he referring to the actual session object on the server or the session
cookie in the
We've just released Resin 4.0.0 for download at
http://caucho.com/download
The resin-4.0-admin.pdf link on that page is broken.
-T
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Looks like Solaris has an epoll() alternative via port_create().
http://developers.sun.com/solaris/articles/event_completion.html
T
___
resin-interest mailing list
resin-interest@caucho.com
Resin 3.0.23 uses the select() API. This limits the server to only 1024
file descriptors. Is there a version of Resin converted to use poll()?
Thanks,
T
___
resin-interest mailing list
resin-interest@caucho.com
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
Does 3.2.x pre-compile xsl style sheets?
Thanks,
Tom
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Updating from 3.0.23 to 3.2.0 causes the following exception. Any
pointers appreciated.
Error in OutputDom : com.caucho.xsl.TransformerExceptionWrapper:
com.caucho.vfs.IOExceptionWrapper: java.lang.ClassCastException:
org.apache.xerces.dom.AttrImpl cannot be cast to
com.caucho.xml.QAbstractNode
477 of those threads had this stack:
0xff2c5870 _read + 0x8
0xe91db008 sock_read + 0x24
0xe91d8edc BIO_read + 0xcc
0xeaa49154 ssl3_read_n + 0x154
0xeaa492d0 ssl3_get_record + 0xe0
0xeaa49e78 ssl3_read_bytes + 0x1fc
0xeaa48dcc ssl3_read_internal + 0x44
0xeacb22a4
I'll send a jstack separately directly to caucho. The memory max
is set to 1M as you note.
T
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Out of curiosity, is it safe to set the thread stack size to 1k on the
load balance resin?
T
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
I've seen small TCP/IP MTU sizes cause similar behavior. We had VPN
software that set the MTU to less than the IP default, which I think should
have been 1500(?). Result was packet fragmentation that caused huge delays
in the Microsoft TCP implementation. I think the MTU setting, in this case,
Is there a status update on the next release of 3.0? I assume it includes
fix 0001927 OpenSSL handshake failure when cipher is not given.
_
Tom Hintz
Direct | 952-707-5412
Fax | 770-242-8270
Google IM | [EMAIL PROTECTED]
http
15 matches
Mail list logo