Re: [Resin-interest] Websphere?

[Brian Parkinson]

I also found this hilarious.
 
Again, just personal opinion, but I'd far far far far far far rather
work with Resin than Web*.
 
parki...
 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron Freeman
Sent: Friday, June 27, 2008 3:01 PM
To: 'General Discussion for the Resin application server'
Subject: Re: [Resin-interest] Websphere?


Hahaha, I am still laughing at that.
 
By the same logic, his company should swap out all servers and personal
computers to OS/2 as well.
 
Seriously though Haluk, give us some specific points other than database
connectivity that would lead you to consider switching so we have
something to consider.  There must be a reason (or several reasons)
other than database connectivity that prompts you to ask for
comparisons?
 
Aaron




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Kreiser
Sent: Friday, June 27, 2008 12:33 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Websphere?


even IF that were true (which I doubt) there is more to choosing
app server.  

do you really want to go with the company that designed java's
date handling API's



Haluk AKIN wrote: 

Thank you for your reply Eric.
 
 
We were told that websphere has a better performance
compared to Resin. I'm trying to find out if that is true.
We have also switched to DB2 recently. So maybe it is
possible IBM software could work better with IBM database?
 
 
 
Thanks,
Haluk



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Kreiser
Sent: Friday, June 27, 2008 11:48 AM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Websphere?


Why are you looking to switch off of Resin?


Personal thoughts... I have been using resin for
years... I have had very few issues with it... it performs well... it is
easy to setup and manage... it does everything I need from an app
server...




Haluk AKIN wrote: 

Hi,
 
We are evaluating to switch our website from
Resin to Websphere.
 
I would appreciate if you could guide me to some
comparisons between these two.
 
Personal thoughts are welcome as well.
 
 
Thanks,
Haluk Akin
 
 


-- 



Eric S. Kreiser
Senior Software Architect


Mzinga
5095 Ritter Road * Mechanicsburg, PA  17055
---
Email me: [EMAIL PROTECTED]
 
Learn more: http://mzinga.com/v/ekreiser/
 
Toll Free: 800.869.5763 




-- 



Eric S. Kreiser
Senior Software Architect


Mzinga
5095 Ritter Road * Mechanicsburg, PA  17055
---
Call my office: 717.458.9804
Fax me: 717.790.0401
Email me: [EMAIL PROTECTED]  
Learn more: http://mzinga.com/v/ekreiser/
 
Toll Free: 800.869.5763 



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

[Resin-interest] Help with port of app from tomcat to resin

[Brian Parkinson]

Hello - 

I've used Resin in the past, and am back again. :) Wondering if someone
might have some suggestions...

We've written a pretty complicated web app using DWR 2.0.3 and JSF (Sun
1.2.7) as well as Spring (2.5.1). It's working great on Tomcat (6.0.16).
In the past on another project, we found that Resin was way faster than
Tomcat, and my understanding is that is still the same (?).

So I grabbed Resin, and fired it up, and it the ALMOST works (woot!) - I
was expecting that nothing would work properly, but my login page comes
up - the issue is when the login is successful and the main page
attempts to load.

One thing I noticed - a couple of my JSF-managed backing beans implement
HttpSessionBindingListener, and for some reason, Resin is repeatedly
calling this (see output below). Never seen this using Tomcat - any
ideas?

When the HttpSessionBindingListener.valueUnbound method is called, my
backing bean clears out some data structures (as it's going out of
session scope) and so I think the fact that this method is being called
by Resin is causing problems - have I set something up wrong?

Any ideas are really appreciated - it seems that I'm really close to
being able to move to Resin, which would be a Happy Day.

As well, are there clear advantages to using Resin's implementation of
JSF?

Thanks.

Brian Parkinson
Software Architect
Avaning Inc.

--- x8 snip


[15:30:13.218] {main} Host[] active
[15:30:13.218] {main} hmux listening to localhost:6800
[15:30:13.234] {main} http listening to *:8080
[15:30:13.234] {main} Server[id=,cluster=app-tier] active
[15:30:13.234] {main} Resin started in 6438ms
[15:31:21.234] {http--8080-1} Loading XML bean definitions from file
[C:\cygwin\home\parki\tools\java\resin-3.1.6\webapp
s\demo2\WEB-INF\spring.xml]
[15:31:21.531] {http--8080-1} Refreshing
[EMAIL PROTECTED]:
display
name
[EMAIL PROTECTED];
startup date [Thu Jun 12 15:31:21 EDT 2008
]; root of context hierarchy
[15:31:21.531] {http--8080-1} Bean factory for application context
[org.springframework.context.support.GenericApplicati
[EMAIL PROTECTED]:
[EMAIL PROTECTED]
804
[15:31:22.328] {http--8080-1} Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableB
[EMAIL PROTECTED]: defining beans
[customEditorConfigurer,lowAlertConfig,mediumAlertConfig,highAlertConfig
,ecobeeAuthent
icationProvider,authenticationManager,buildInfo,foundationBuildInfo,cach
eManager,acknowledgeCache,alertCache,dispatchCac
he,statusCache,thermostatCache,weatherCache,communicator,waiterManager,a
cknowledgeHandler,alertHandler,dispatchHandler,e
rrorHandler,statusHandler,thermostatHandler,handler,httpClient,clientUti
l,alertDao,fileDao,infoDao,logDao,statusDao,http
ThermostatDao,thermostatDao,userDao,weatherDao,workDao,dwrManager,mapCon
fig,dataSource,sqlMapClient,modelCopier,statusEq
uipment1,statusEquipment2,statusZone1,statusMessage,org.springframework.
scheduling.quartz.SchedulerFactoryBean#0,dbPingT
rigger,dbPingJob,dbPingTask,scheduledService,statusMessageGenerator,auxi
liaryConverter,calendarEventConverter,climateCon
verter,thermostatProcessor,preferences,user]; root of factory hierarchy
[15:31:22.609] {http--8080-1} Initializing EHCache CacheManager
[15:31:24.375] {http--8080-1} Job execution threads will use class
loader of thread: http--8080-1
[15:31:24.421] {http--8080-1} Quartz Scheduler v.1.6.0 created.
[15:31:24.437] {http--8080-1} RAMJobStore initialized.
[15:31:24.437] {http--8080-1} Quartz scheduler 'DefaultQuartzScheduler'
initialized from default resource file in Quartz
 package: 'quartz.properties'
[15:31:24.437] {http--8080-1} Quartz scheduler version: 1.6.0
[15:31:24.437] {http--8080-1} JobFactory set to:
[EMAIL PROTECTED]
[15:31:24.875] {http--8080-1} Starting Quartz Scheduler now
[15:31:24.875] {http--8080-1} Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED started.
[15:31:31.203] {http--8080-1} Connecting without SSL.
[15:31:32.390] {http--8080-1} Login accepted for user: [EMAIL PROTECTED]
[15:31:33.093] {http--8080-1} GET /thermostat/105 ecobeeId:
670092a011a7e419cc07ff80
[15:31:34.984] {http--8080-1} Value unbound from session.
[15:31:35.000] {http--8080-1} Value unbound from session.
[15:31:35.171] {http--8080-1} DWR Version 2.0.3 starting.
[15:31:35.171] {http--8080-1} - Servlet Engine: Resin/3.1.6
[15:31:35.171] {http--8080-1} - Java Version:   1.5.0_14
[15:31:35.171] {http--8080-1} - Java Vendor:Sun Microsystems Inc.
[15:31:35.812] {http--8080-1} Probably not an issue: org.jdom.Document
is not available so the jdom converter will not l
oad. This is only an problem if you wanted to use it.
[15:31:35.812] {http--8080-1} Probably not an issue: org.jdom.Element is
not available so the jdom converter will not lo
ad. This is only an problem if you wanted to use it.
[15:31:35.859] {http--8080-1} Value unbound from session.
[15:31:35.859] {http--8080-1} Value unbound from session.
[15:31:35.906] {http--8080-1} Value unbound