[jboss-jira] [JBoss JIRA] (WFLY-3404) Major performance degradation from JBoss 7.1 to Wildfly 8.0.0-Final.

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971951#comment-12971951 ] 

jaikiran pai commented on WFLY-3404:
------------------------------------

I think this was fixed in a later release as noted in https://community.jboss.org/message/862500#862500. Try the later releases from here http://wildfly.org/downloads/

> Major performance degradation from JBoss 7.1 to Wildfly 8.0.0-Final.
> --------------------------------------------------------------------
>
>                 Key: WFLY-3404
>                 URL: https://issues.jboss.org/browse/WFLY-3404
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.0.0.Final
>            Reporter: Timothy Heider
>            Assignee: Jason Greene
>
> I have deployed my application to Wildfly 8.0.0 Final and it is almost unusable now.  We have rolled back to JBoss 7.1 (same application WARs) and it works fine.  
> Specifically what seems to be slow is our SOAP web services are taking up to 8 to 10 seconds to respond.  We have user concurrency of probably 10-30 users at once hitting these services every 10 seconds or so.
> On JBoss 7.1 these services all respond sub-second.  The database is totally unburdened and the server is 90% idle all the time.
> We have one service endpoint that is a Comet queue wait call.  Probably 10 users are waiting on that.  Did something change between JBoss 7 and Wildfly 8 that might cause that to not work now? (e.g. too small a thread pool that blocks until the 10 second comet call breaks on a timeout?)
> We will try 8.1.0CR2 but I wanted to report we're investigating this and see if you can help us.  Thanks!



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)