Tapestry's throughput is severely effected by
HIVEMIND-162. If that bug is not going to be addressed soon, then the Tapestry hivemodule.xml files need to have their classes fully specified for threaded services as a workaround for the underlying problem. If a HiveMind fix is going to be released that takes care of this before T4 goes final, then this bug can be closed.
|Workflow||Default workflow, editable Closed status [ 12567592 ]||jira [ 12590731 ]|
|Workflow||jira [ 12344902 ]||Default workflow, editable Closed status [ 12567592 ]|
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||4.0.3 [ 12310994 ]|