[JBoss Seam] - concurrent-request-timeout - how to set optimal size?
by enda
Seems that concurrent-request-timeout parameter in components.xml is important for Ajax
How can I determine optimal size?
-----------------------------------------------------------------------------------
<core:manager concurrent-request-timeout="1000"
conversation-timeout="120000"
conversation-id-parameter="cid"/>
-----------------------------------------------------------------------------------
Also to use conversation propagation seems important
-----------------------------------------------------------------------------------
<h:commandButton value="Save"
rendered="#{edit}"
action="#{personAccountManager.save}">
<s:conversationPropagation type="join"/>
</h:commandButton>
----------------------------------------------------------------------------------
Seam examples in documentation does not have this?
When concurrent-request-timeout is small then I have problem:
20:31:21,692 INFO [lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or was processing another request), detail=(The conversation ended, timed out or was processing another request)]
sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or was processing another request), detail=(The conversation ended, timed out or was processing another request)]
But can a bigger value cause memory problems on server?
Tomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106056#4106056
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106056
18 years, 8 months
[JBoss Seam] - simulating dependency bijection with SeamTest
by djfjboss
Following the examples in Yuan/Heute chapter 21 re the above, I cannot see how to inject a FacesMessage.
My original class has:
@In
| FacesMessages facesMessages;
followed by
facesMessages.add(...
as per usual
and my test class extends SeamTest.
However I seem to need to bind the facesMessages variable explicitly within a test method in order that this variable is bound in the testing context. I therefore tried:
setField(action, "facesMessages", FacesMessages.instance());
But this generates an IllegalStateException, stating that there is no active conversation context (as a result of FacesMessages.instance() checking for Contexts.isConversationContextActive(), in turn accessing the thread local variable, which appears therefore to be null.
Am I barking up the wrong tree? I had thought I would be able to get at this and other related variables via the SeamTest class but I don't see how.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106053#4106053
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106053
18 years, 8 months