[ https://issues.jboss.org/browse/JBDS-1698?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1698: ---------------------------------- Dan, as you asked me on IRC today if I am still facing performance problems I found out some following observations: If I try to publish Teiid Designer Parts Example Project I get following [1],[2] errors. And the running soa server throws some exceptions [3]. All of these errors occur before the "Publish to Modeshape" dialog appears. Maybe we should consider renaming this jira if the performance problems are caused by these errors? [1] attached screen1.png [2] attached screen1_stacktrace.txt [2] attached soa-server.log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1698?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on JBDS-1698: ------------------------------------- I'm not sure why the dialog doesn't appear for 2 minutes - that would be something that needs to be investigated in the plugin (my guess is that the request to the server has to timeout, or that the problematic query was taking a long time to run). Another possible reason for the delay might be this: if this was the first request made to the server, then (prior to ModeShape 2.6.0.Beta1) the delay might be due to ModeShape starting (see MODE-1115). Starting with 2.6.0.Beta1, ModeShape starts immediately when the server is started (MODE-1180), so the first client requests should be significantly faster. Note that this reason can be tested/verified by simply trying the publishing step again (without shutting down the server), and if the response is significantly(!) faster, this was likely the cause for the delay. As for the NPE exception in "soa-server.log", this was already fixed via MODE-1131 and was included in ModeShape's 2.5.0.Beta2 release (and later releases). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1698?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1698: -------------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1698?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1698: ---------------------------------- Hi Dan, I tried it today with JBDS 5.0.0.M3 and SOA 5.2.ER5. I do not have performance problems anymore. Also I do not see the exception anymore. Feel free to close the jira ;-). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1698?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-1698. ---------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira