Re: [Resin-interest] 4.0.6 Can't handle files 2GB?

2010-10-18 Thread Tom Hintz
 
 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 architecture on Solaris.


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Cookie lifetime

2010-08-19 Thread Tom Hintz
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 the session 
 cookie in the browser?  Yes, each new request does reset the timer on the 
 session object on the server, but we are not seeing the expiry date on the 
 cookie being updated. I have tested this on a server using IE8, Firefox 3.6, 
 and the latest Chrome build with Resin running solo and with Apache running 
 as the front end, and the results are the same in all browsers. 

 When setting cookie-max-age in the session-config for the web app, the expiry 
 date/time for the session's persistent cookie does not change on subsequent 
 requests. I also verified that this behavior is exhibited.



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Cookie lifetime

2010-08-17 Thread Tom Hintz
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
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Cookie lifetime

2010-08-17 Thread Tom Hintz
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 browser?  Yes, each new request does reset the timer on the 
session object on the server, but we are not seeing the expiry date on the 
cookie being updated. I have tested this on a server using IE8, Firefox 3.6, 
and the latest Chrome build with Resin running solo and with Apache running as 
the front end, and the results are the same in all browsers.

When setting cookie-max-age in the session-config for the web app, the expiry 
date/time for the session's persistent cookie does not change on subsequent 
requests. I also verified that this behavior is exhibited.

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] FW: resin-interest Digest, Vol 35, Issue 9

2009-05-07 Thread Tom Hintz

 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


[Resin-interest] select() vs poll()

2009-03-19 Thread Tom Hintz
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
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] 3.0.23 select()

2009-03-17 Thread Tom Hintz
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
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Memory leak - in Resin?

2008-10-30 Thread Tom Hintz
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


[Resin-interest] Pre-compiled XSLT

2008-10-07 Thread Tom Hintz
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


[Resin-interest] Convert 3.0.23 to 3.2.0 Xsl transform

2008-10-07 Thread Tom Hintz
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

Code goes something like this.

private static DocumentBuilder s_DocumentBuilder = null;
private static com.caucho.xsl.Xsl s_TransformerFactory = null;
...
public void OutputDom(Document doc, String outFile)
{
org.apache.xml.serialize.OutputFormat MyOutputFormat;
XMLSerializer MySerializer;
FileOutputStream OutputXML;

try
{
//  Save Output XML Document by creating an
output stream, an
//  XMLSerializer, assigning the output stream
to the serializer, and
//  setting the serializer to be a DOM
serializer
OutputXML = new FileOutputStream(outFile);
MySerializer = new XMLSerializer();
MySerializer.setOutputByteStream(OutputXML);
MySerializer.asDOMSerializer();
//  Create the Output Format for the Serializer
for
//XML, UTF-8, and indentation true
MyOutputFormat = new
org.apache.xml.serialize.OutputFormat(XML, UTF-8, true);
MySerializer.setOutputFormat(MyOutputFormat);
//  Write out the document, and close the output
stream
MySerializer.serialize(doc);
OutputXML.flush();
OutputXML.close();
}

catch (Exception e)
{
System.err.println(Error in OutputDom :  +
e.toString());
}
}

Tom


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


Re: [Resin-interest] Leak with 3.0.23 load balancing

2008-10-03 Thread Tom Hintz
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  ssl_read + 0xa8
0xeb1e25d8  Java_com_caucho_vfs_JniStream_readNative + 0x54

Tom

-Original Message-
Subject: RE: Leak with 3.0.23 load balancing

Thread count climbed steadily from a beginning of 70 to 300+ to finally
500+ when heap was exhausted.

Tom


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Fwd: Resin 3.0 thread leak

2008-10-02 Thread Tom Hintz


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


Re: [Resin-interest] Resin 3.0 thread leak

2008-10-02 Thread Tom Hintz
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


Re: [Resin-interest] Slooow file reads (really weird!)

2007-10-05 Thread Tom Hintz
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,
was in the VPN software.

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] 3.0.24 Status w/OpenSSL handshake fix?

2007-08-07 Thread Tom Hintz
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://www.comsquared.com/ www.comsquared.com

 

IMPORTANT NOTICE: This communication is privileged and contains confidential
information for the sole use of the intended recipient(s). Any unauthorized
disclosure, copying or use of this communication is strictly prohibited. If
you have received this message in error, please contact the sender and
delete this message without printing it or otherwise retaining a copy.

 

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest