Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

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~~.

Show
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 .
Forum Reference:
http://community.jboss.org/thread/163742
Workaround:

Workaround Exists
Workaround Description:

Hide

Use an alternative deployment mechanism, such as a local file drop into the deploy directory, or through RHQ.

Show
Use an alternative deployment mechanism, such as a local file drop into the deploy directory, or through RHQ.

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

is blocked by

JBPAPP-6396 ServerInvoker does not close StreamHandler in the case of "addstreamcallback"