[teiid-issues] [JBoss JIRA] Commented: (TEIID-1511) VDB deployment leaves with too many open files
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Wed Mar 16 23:32:45 EDT 2011
[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588505#comment-12588505 ]
Steven Hawkins commented on TEIID-1511:
---------------------------------------
Using JBAS-6665 and editing the deploy/remoting-jboss-beans.xml to reduce the pool size (the default remoting socket pool holds 300 serversockets, which will hold 2 threads per socket this seems far too high as the issue suggests):
<entry><key>maxPoolSize</key> <value>30</value></entry>
<!-- Number of seconds after which an idle worker thread will be -->
<!-- purged (socket transport). By default purging is not enabled. -->
<entry><key>idleTimeout</key> <value>60</value></entry>
However this still had no effect, either in timeout or number of sockets created. From the debugger it looks like there is an issue with InvokerRegistry$ClientInvokerHolder, which has a counter that will never reach 0 and release the socket. There is always 1 holder that is registered as part of AS startup outside of Teiid. A naive attempt to fix the counter still didn't work though. I think we'll have to log an issue against the usage of the local profile service.
> VDB deployment leaves with too many open files
> ----------------------------------------------
>
> Key: TEIID-1511
> URL: https://issues.jboss.org/browse/TEIID-1511
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.1, 7.2, 7.3
> Reporter: Ramesh Reddy
> Fix For: 7.4
>
>
> After deploying a VDB using Admn API or AdminShell a temporary file handle is open and does not seem to be closed. After deploying the VDB run
> lsof
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list