Bug 990494 - Netty worker threads consume all cpu time after deployment and undeployment of service with udp binding
Summary: Netty worker threads consume all cpu time after deployment and undeployment o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER7
: 6.0.0
Assignee: Douglas Palmer
QA Contact: Jiri Sedlacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-31 09:57 UTC by Jiri Sedlacek
Modified: 2015-08-02 23:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
reproducer (6.87 KB, application/x-compressed-tar)
2013-07-31 09:57 UTC, Jiri Sedlacek 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-1633 0 Major Closed Netty goes bonkers when undeploying UDP bindings 2014-06-16 23:49:08 UTC

Description Jiri Sedlacek 2013-07-31 09:57:51 UTC 
Created attachment 781034 [details]
reproducer

Description of problem:

After deployment and undeployment of archive with switchyard service, netty worker threads consume all cpu power. 

Example project is attached.
Comment 1 Keith Babo 2013-07-31 13:29:02 UTC 
I can confirm this behavior locally and I also see netty threads consuming the CPU.  We need to dig into this deeper, but I would vote against this being a blocker as deployment still works and the server is still able to shutdown cleanly if the user gets into a situation where undeploy pegs the CPU.  Undeploying the app and bouncing the server results in a clean undeployment.  Obviously not ideal, but at least the server is left in a consistent state.

BTW, I do not see this behavior with Netty TCP bindings, so the impact here is limited to UDP bindings only.
Comment 2 Jiri Sedlacek 2013-08-01 11:15:56 UTC 
Keith, I've seen this behaviour with TCP bindings too, but just once and cannot reproduce it now. So there may be issues with Netty regardless of TCP/UDP choice.
Comment 7 JBoss JIRA Server 2013-10-21 13:15:02 UTC 
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1633

pushed
Comment 8 Jiri Sedlacek 2013-12-18 13:51:59 UTC 
tried several times, seems to be fixed, marking as verified in ER7-2
Comment 9 JBoss JIRA Server 2014-06-16 23:49:09 UTC 
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1633 to Closed
Note You need to log in before you can comment on or make changes to this bug.