Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.0.0.M2
-
Fix Version/s: 5.0.0.M4
-
Component/s: modeshape
-
Labels:None
-
Release Notes Docs Status:Not Required
Description
1) Import Parts Model Project Set Example (Help -> Project Examples... -> Teiid Designer -> ..)
2) Right click on PartsProject and select ModeShape -> Publish
The ModeShape publish dialog appears on the screen after more then 2 minutes. On the first look it seems like frozen, but after cca 2 minutes starts everything to work.
Gliffy Diagrams
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
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).
Randall Hauch
added a comment - 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). Pavol, I checked in the ModeShape client jar from SOA 5.2.0 ER3 which adds patches to the ModeShape 2.5.Final. Hopefully this will fix the performance and exception issue. Let me know. Thanks, Dan
Dan Florian
added a comment - Pavol, I checked in the ModeShape client jar from SOA 5.2.0 ER3 which adds patches to the ModeShape 2.5.Final. Hopefully this will fix the performance and exception issue. Let me know. Thanks, Dan Pavol, the ModeShape client jar from EDS 5.2.0 ER5 has been checked-in to trunk. Try the query more than once to compare performance. Let me know if you are still seeing the performance and exception issue. Thanks.
Dan Florian
added a comment - Pavol, the ModeShape client jar from EDS 5.2.0 ER5 has been checked-in to trunk. Try the query more than once to compare performance. Let me know if you are still seeing the performance and exception issue. Thanks. 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 
.
The performance issue and exception have been fixed per testing by Pavol using JBDS 5.0.0.M3 and SOA 5.2.ER5.
Dan Florian
added a comment - The performance issue and exception have been fixed per testing by Pavol using JBDS 5.0.0.M3 and SOA 5.2.ER5. Verified on jbdevstudio-product-linux-gtk-5.0.0.v201110242253R-H40-M4.
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