Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1493#issuecomment-218656836
@kiwiflyer along with this patch, have you also applied the optimization
patch #1534 (make sure to apply the patch on both mgmt server and KVM agent) ?
We can debug your issue to see if it's caused by NioConnection by changing
log4j settings to `TRACE`. Edit `/etc/cloudstack/agent/log4j-cloud.xml`, and
add a category with name="com.cloud.utils.nio" and priority value="TRACE" and
watch out for issues in the logs. Alternatively, you have enable DEBUG/TRACE on
com.cloud and org.apache.cloudstack categories to see what's happening.
Finally, if you've an IDE or jdb you can attach a debugger to the agent with
JAVA_OPTS settings `-Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n` and connect on
remote port 8787 (or any other custom port). Let me know if that helps, or you
need more help in finding out the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
