Hi everyone,
We're having a problem with apparent disconnection of a shared drive
containing the JVM and the JAR files. From time-to-time our
application will report "ClassDefNotFound" exceptions for classes that
are truly there. As a result we'll get some missing JSP .class files
presumbaly becau
We use jsse versus openssl, but when we were playing with openssl in
the 3.0.x release, the certificate chain file needed to have all the
certificates in it - from the root, any intermediates, and your final
wildcard cert - all cat'd together. Just something to check.
+ jay
On 1/24/07, Barrie S
Riccardo,
We have been running 3.0.18Pro with openssl on windows successfully
for a while now.
We take our certificates - from the root cert, all the intermediate
certs, down to our wildcard cert - and bundle them into a pkcs12 file
(a .p12 file). You can review the openssl documentation to learn
I had some fun and frustration this morning configuring a new server
environment. I mistakenly tried to use variable names like "foo.bar"
and "foo-bar" in some statements. Those didn't work.
Instead, does work.
Was this a convention I should have known? It occurs to me now that
these statements
I am setting up a new resin installation and ran into a fork in the config.
We would like to have http://foo.bar.com and https://foo.bar.com to be
answered by the same resin, but with different webapps defined for
each.
http://foo.bar.com would answer with a welcome page while ...
https://foo.bar
again!
+ jay
On 3/30/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Mar 30, 2007, at 3:33 PM, Jay Ballinger wrote:
>
> > I am setting up a new resin installation and ran into a fork in the
> > config.
> >
> > We would like to have http://foo.bar.com a
y hoping to not have to set a host name at all. I would
like to simply have any request hitting port 8080 served from one set
of defined webapps, while all requests hitting port 8443 served from
another set of defined webapps regardless of which host name has
brought the user to this server. Is
to an explicit
host name nor lock myself into a long list of host-alias names.
Thanks, again, for the help, Scott. Hopefully I was a little clearer
this time in what I am trying to accomplish.
+ jay
On 4/2/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Mar 31, 2007, at 9:41 PM,
about this > < close to having this new server environment
configured. This is my last hiccup, so far.
+ jay
On 4/2/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Apr 2, 2007, at 10:27 AM, Jay Ballinger wrote:
>
>
s, and the
port forwarding (to not run as root), it requires that you wrestle the
OS and Resin into the format that will work. I'll have to document the
setup in a blog somewhere for others to review.
+ jay
On 4/3/07, Scott Ferguson <[EMAIL PROTECTED]> wrote:
>
> On Apr 2, 2007,
We're using SSL (via JSSE) on Resin 3.1 just fine.
+ jay
On 4/5/07, Jean-Francois Lamy <[EMAIL PROTECTED]> wrote:
>
>
>
>
> My understanding is that SSL support is only available for Resin Pro, and
> client won't shell out 1000$ for running on a dual-core PC.
>
>
>
> So plan B is to install Apac
We use JSSE successfully and haven't really noticed any performance
problems or slowdowns.
pkcs12
/some/path/to/file.p12
secret
We used OpenSSL to bundle the wildcard cert, the intermediate certs,
and the root cert into one .p12 file
Mike,
This sounds like a perfect use for a hardware load-balancer. A
hardware load-balancer can create the affinity for a particular server
much like you describe - except for the choosing of a server based on
your algorithm, that is.
Most hardware solutions implement some sort of persistence fea
Are you trying to use session objects that are from the past? If these
objects were serialized before your change, they will probably be
incompatible with your new change. You'll need to clean house of the
serialized artifacts first.
+ jay
On 9/3/07, Daniel López <[EMAIL PROTECTED]> wrote:
> Hi
I'm finding myself in the same boat as Tim, I need to restrict the list
of ciphers for resin using JSSE.
Tim, did you get this working?
+ jay
Kuntz, Tim wrote:
> All,
>
> I’m currently using JSSE vs. OpenSSL for my SSL configuration. I now
> need to restrict the ciphers so use of the weake
Mitch,
We're using a hardware load balancer in front of our Resin servers. To
try and find a way to uniquely identify each browser in an SSL and NAT
world, we're utilizing the session ID on the SSL handshake.
Since NAT routers will consolidate IP addys, and cookies may be hidden
behind the SSL
You're setting these in the resin config file and not on the
command-line call, right?
+ jay
Stargazer wrote:
> I have a RH server with 750mb ram. Its serving about 30 hosts, split
> between php (quercus) and jsp. As its not doing
> anything else, just the usual email etc, I want to allocate 5
Hi everyone,
We're running Resin 3.0.18 Pro on a Windows 32-bit system and we're
looking to understand/tune our memory settings a bit.
According to http://www.caucho.com/resin-3.0/performance/jvm-tuning.xtp
the stack size is set to 2048k unless set otherwise. Is this true? In
using JConsole we
if we use -Xss1024k, each thread is really using
between 0 and 1024k depending on what that thread really needs?
+ jay
Knut Forkalsrud wrote:
> On Thu, Jan 8, 2009 at 1:52 PM, Jay Ballinger wrote:
>> - When a thread is created, does it grab all of the stack memory, or can
>> the sta
rote:
>
>> On Jan 8, 2009, at 13:52, Jay Ballinger wrote:
>>
>>> Hi everyone,
>>>
>>> We're running Resin 3.0.18 Pro on a Windows 32-bit system and we're
>>> looking to understand/tune our memory settings a bit.
>>>
>>> A
Tuan,
Did you try ${object.price} ?
We also found Resin 3.1.x to be more specific than 3.0.x about the
conventions used with EL. We made a pass through our code looking for
these capitalization differences and that solved our problems.
+ jay
Tuan Tran wrote:
> Hi all!
>
>
>
> We are hav
Howdy,
Please refer to:
http://bugs.caucho.com/view.php?id=3431 (which is a reopen of)
http://bugs.caucho.com/view.php?id=2360
We're using Resin Pro 3.1.6 and trying to limit the cipher suites for
JSSE. I couldn't find the documentation, but through trial and error was
able to discover that h
start, we may implement 3.1.6x until
3.1.10 is available. ;)
Have you guys had a chance to take a quick look, yet?
+ jay
Scott Ferguson wrote:
> On May 1, 2009, at 4:33 PM, Jay Ballinger wrote:
>
>> Howdy,
>>
>> Please refer to:
>>
>> http://bugs.caucho.c
We use wildcard certs with 3.0.18Pro and 3.1.6Pro (JSSE and 32bit)
without problems.
If only we could correctly limit the cipher suites.
http://bugs.caucho.com/view.php?id=3431 (which is a reopen of)
http://bugs.caucho.com/view.php?id=2360
Scott or Emil, either of you had a chance to review my s
24 matches
Mail list logo
