[
https://issues.jboss.org/browse/TEIID-1511?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1511:
----------------------------------
Assignee: Steven Hawkins
Workaround Description: Use an alternative deployment mechanism, such as a local file
drop into the deploy directory, or through RHQ.
Workaround: [Workaround Exists]
Priority: Critical (was: Major)
Steps to Reproduce:
Use the admin api to deploy/undeploy a large number of times, for example in adminshell
for (i = 0; i < 200; i++) {
deployVDB("foo.vdb");
undeployVDB("foo", 1);
}
There will be well over 300 new open sockets at the end of the run. Prior to the previous
commit on this issue in 7.4, at most 64 of them can be buffer files that will get auto
cleaned up, but the rest of them will be remoting serversockets that do not seem to be
limited by the suggestion in JBAS-6665.
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
Assignee: Steven Hawkins
Priority: Critical
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