[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1511: --------------------------------------- The temp streams automatically clean up when their corresponding inputstream is garbage collected. The file store logic also maintains an open file pool, but limits the size to by default to 64 files. We could be more proactive at purging on the stream close for readers and inputstreams since they can only be read once (lob types can be read multiple times). If we're creating additional listening sockets, I'm not sure what those are. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1511: ------------------------------------- On second thought you are right, if this deploy is done from Admin Shell or remote Admin connection. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1511: --------------------------------------- This is well below us. DeploymentProgress.run() uses the remoting logic through a StreamingDeploymentTarget. Look at DeploymentManagerImpl - there is no other implementation of DeploymentTarget, so even a local ProfileService will use remoting for deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-1511 at 4/14/11 4:07 PM: -------------------------------------------------------------- This error was occurring due to stream handler was not being closed. See https://issues.jboss.org/browse/JBREM-1282 was (Author: rareddy): This error was occurring due to stream handler was not being closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1511: ------------------------------------- May be profile service being created in-correctly. It was not obvious to me on the first look, I will take peek again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1511: --------------------------------------- Is there anything that we can do on our side for this in the 7.4 release? Or should we add a KI to the release notes and await the associated fix? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin... ] Ramesh Reddy closed TEIID-1511. ------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira