[S2] concurrency issues

[meeboo <de...@gmail.com>]

Hey all

We just launched a webapp using Hibernate/Spring/S2. The architecture is
pretty standard with a DAO, Service and a Web layer. Our problem is that we
are receiving massive traffic which pretty much kills the application after
just a couple of seconds. I am guessing this is since our S2 architecture is
a bit fragile (we're all S2 newbies). What we have done is that we have a
superclass called "StrutsSupport" which implements SessionAware,
ParameterAware and ValidationAware. We then have all of our Struts action
classes subclass StrutsSupport. StrutsSupport is also declared in Spring as 

<bean id="strutsSupport" class="com.myapp.web.struts.StrutsSupport"
scope="prototype">
		<property name="adminService" ref="adminService" />
		<property name="liveContentService" ref="liveContentService" />
		<property name="movieService" ref="movieService" />
		<property name="searchQueryService" ref="searchQueryService" />
		<property name="userService" ref="userService" />
</bean>

As you can see it contains all our service class references. Our service
classes in turn look like this:

<bean id="userService" class="com.myapp.service.impl.UserServiceImpl">
        <property name="newsletterSubscriberDao"
ref="newsletterSubscriberDao" />
        <property name="userDao" ref="userDao" />
        <property name="userMessageDao" ref="userMessageDao" />
        <property name="zipCodeDao" ref="zipCodeDao" />
</bean>


Can it be the StrutsSupport superclass which is causing all the problems?
Should it be configured another way?

Thanks!!
-- 
View this message in context: http://www.nabble.com/-S2--concurrency-issues-tf3703183.html#a10355708
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: [S2] concurrency issues

[meeboo <de...@gmail.com>]

We have about 100000 visits a day so it takes a small mistake to break the
app completely (it's happened before, maybe I should have a talk with our
server people). I found the mistake though, some methods were using
handrolled SQL and creating the session directly from a DaoSupport class
instead of the hibernateDaoTemplate. Thanks for the quick reply though Dave,
you're a stand up S2 guy :)


Dave Newton-4 wrote:
> 
> --- meeboo <de...@gmail.com> wrote:
>> We just launched a webapp using Hibernate/Spring/S2.
>> The architecture is pretty standard with a DAO, 
>> Service and a Web layer. Our problem is that we
>> are receiving massive traffic which pretty much
>> kills the application after just a couple of
> seconds.
> 
> A couple of *seconds*? I find it difficult to believe
> that you are receiving enough traffic in a couple of
> seconds to break your application.
> 
> Define "kills the application"; what is actually
> happening?
> 
> d.
> 
> 
> 
>  
> ____________________________________________________________________________________
> Expecting? Get great news right away with email Auto-Check. 
> Try the Yahoo! Mail Beta.
> http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-S2--concurrency-issues-tf3703183.html#a10356581
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: [S2] concurrency issues

[Dave Newton <ne...@yahoo.com>]

--- meeboo <de...@gmail.com> wrote:
> We just launched a webapp using Hibernate/Spring/S2.
> The architecture is pretty standard with a DAO, 
> Service and a Web layer. Our problem is that we
> are receiving massive traffic which pretty much
> kills the application after just a couple of
seconds.

A couple of *seconds*? I find it difficult to believe
that you are receiving enough traffic in a couple of
seconds to break your application.

Define "kills the application"; what is actually
happening?

d.



 
____________________________________________________________________________________
Expecting? Get great news right away with email Auto-Check. 
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org