[Resin-interest] the response time

2010-01-15 Thread long wang
Hi, there, I integrate resin with apache. My resin's version is 3.0.19 and apache is 2.0.59. I configured both of them to record the response time in microseconds(log format %D). But I found the time recorded by resin is much larger than apache. Sometimes it's hundreds of times larger. Does

[Resin-interest] Resin: configuration for a jms client]

2010-01-15 Thread Daniel López
Hi there, Nobody uses Resin's JMS from external applications? Do people use other JMS solutions inside Resin? I'll stick with OpenJMS for now, but as we already have Resin nodes installed, I thought it would have been intesting to use them and remove one service. The scarce documentation

Re: [Resin-interest] the response time

2010-01-15 Thread Scott Ferguson
long wang wrote: Hi, there, I integrate resin with apache. My resin's version is 3.0.19 and apache is 2.0.59. I configured both of them to record the response time in microseconds(log format %D). But I found the time recorded by resin is much larger than apache. Sometimes it's hundreds

Re: [Resin-interest] the response time

2010-01-15 Thread Jon Stevens
I don't understand why people still put their container behind apache. Unless you are using mod_rewrite or something like that, you don't need to do that. It isn't like apache somehow 'protects' resin from evil doers. If you need a load balancer, get a load balancer. jon On Fri, Jan 15, 2010 at

Re: [Resin-interest] Resin: configuration for a jms client]

2010-01-15 Thread Scott Ferguson
Daniel López wrote: Hi there, Nobody uses Resin's JMS from external applications? Do people use other JMS solutions inside Resin? I'll stick with OpenJMS for now, but as we already have Resin nodes installed, I thought it would have been intesting to use them and remove one service.

[Resin-interest] Messaging Config

2010-01-15 Thread Scott Hernandez
I was looking at the lastest 4.0.3 docs and it seems to indicate that I should do this for my configuration: web-app ... xmlns:queue=urn:my-package-path ... jms:JmsConnectionFactory / jms:FileQueue queue:DeliveryQueue/ Nameddelivery/Named /jms:FileQueue queue:DeliveryListener

Re: [Resin-interest] java unicode problem in cross-plateform situation

2010-01-15 Thread Knut Forkalsrud
You may want to double check if you really have UTF-8 in your environment in all circumstances. Here you also depend on the character set of the source file, which is unnecessary. And your code could be simpler. char[] urlset3a = {0xc0,\u00c1, // either numeric literals or unicode escapes