[jboss-user] [JBoss Messaging] - Hot deploy of an ear containing a QueueBrowser showing Class
JBM rocks by the way. This is the first big issue we have encountered in
months of usage.
We have an application with a QueueBrowser that consumes from a JBM queue that
at this point contains only ObjectMessages. The ObjectMessage contains a basic
custom class that is part of the ear. The first time the application is
deployed, messages are browsed correctly from the queue. After a hot deploy,
we can no longer browse the queue.
I am not very familiar with the internals of JBM, but here is what I found
while debugging. We are using JBoss 4.2 with JBM 1.4.0-SP3-CP01.
This is the code:
| //various setup code for the session all within a try/finally that
ultimately closes the QueueBrowser, QueueSession, and QueueConnection
| final Enumeration enumerator = browser.getEnumeration();
| while (enumerator.hasMoreElements())
| {
| final ObjectMessage message = (ObjectMessage)
enumerator.nextElement();
|
| final Object messageObject = message.getObject();
|
| if (messageObject instanceof CustomObject)
| {
| // code path on a fresh server
| }
| else
| {
| // code path after a redeploy
| }
|}
|
1. After a redeploy the messageObject is a CustomObject, but its from a dead
ClassLoader (likely the undeployed ear). I think it's dead because when I
print it out, it says [EMAIL PROTECTED] url=null ,addedOrder=41}. The
classloader of CustomObject prints out as [EMAIL PROTECTED]
url=file:/C:/jboss/jboss-4.2/server/default/tmp/deploy/tmp31717application.ear
,addedOrder=43}. This explains why the else state executes.
2. On a fresh start of the server, if I debug into the message.getObject()
call, it eventually lands in MessageSupport.getPayload(), which because the
payload is null and the payloadAsByteArray is not, goes into
StreamUtils.readObject. Eventually the object is deserialized and returned to
the client.
3. On a redeploy, when I debug into the message.getObject() method, it lands
in MessageSupport.getPayload() but now the payload is not null and the
payloadAsByteArray is null. It returns the payload that is associated to the
dead classloader immediately.
It seems like a cached Message is being returned, one that was previously
deserialized with the original deployed ear's ClassLoader. And since it is a
different ClassLoader, we end up with the invalid codepath being following.
I could probably code up a workaround that uses reflection to process the
Message's object.
Any thoughts as to what is happening?
Is there a way to override the cached payload behavior?
Is there additional work that can be down to shutdown the
QueueBrowser/QueueSession such that the Queue is reset to the original state?
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157041#4157041
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157041
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Mule and JMS in JBoss
try the mule user forum http://www.nabble.com/Mule---User-f2727.html or read the docs at http://mule.mulesource.org/display/MULE2USER/JMS or look at the examples at https://svn.codehaus.org/mule/branches/mule-2.0.x/examples/ or look at the unit tests for mule jms transport at https://svn.codehaus.org/mule/branches/mule-2.0.x/transports/jms/src/test/ View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157059#4157059 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157059 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: rich:tree onkeyup functionality?
Please post this question to the Richfaces forum. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4085478#4085478 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4085478 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Problems using ajax validation in seam-gen
I'm a bit late to this party, but we have been experiencing this for months. We originally tried the same technique Pete suggested using - a4j eventqueues with requestDelays - but it didn't go far enough. What we wanted was if a user was typing or clicking, to send one request to the queue requestDelay milliseconds after the final generated event on that queue. This would allow a user to click a button repeatedly, but only the very last button click would be processed. Or if a user went trigger happy on the keyboard in an input field with a keypress event, it would only react on the last keypress event. Or we could send an input field onchange and a button click through the queue to send only the last event. There is a chance for lost javascript events, but since 99.9% of our pages simply submit the form and kick off an action, ignoring the original events didn't really hurt anything. In order to do this we implemented a special JavaScript event queue widget that enforced this behavior. It worked pretty well. However, we still get the Conversation ended, timed out or was processing another request message so often that our users consistently bring it up as a problem. We would still love to see JBSEAM-1832 implemented since it helps to address the double click problem as well as the The conversation ended, timed out or was processing another request problem. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081464#4081464 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081464 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: howto display the an enum object internationalized
What we did was to create an EnumConverter that uses the resource bundle for
internationalization. We just defined a convention
packagename.classname.enumvalue=Some text.
If we find something in the resource bundle, use it, otherwise just use the
toString value of the enum.
Something like this code.
|
| @Override
| public String getAsString(final FacesContext context, final UIComponent
component, final Object object) throws ConverterException
| {
| String retVal = null;
| if (object instanceof Enum)
| {
| Enum instance = (Enum)object;
| final String resourceKey = instance.getClass().getName() + .
+ instance.name();
| try
| {
| retVal = ResourceBundle.instance().getString(resourceKey);
| }
| catch (MissingResourceException e)
| {
| //Ignore
| }
| if (StringUtils.isEmpty(retVal))
| {
| retVal = instance.name();
| }
| }
| return retVal;
| }
|
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4071203#4071203
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4071203
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Validation of non-ui fields
That is the approach we have taken. It works.fine is the appropriate word. Another idea would be to bind the values to a h:inputHidden. Using Hibernate Validator's @AssertTrue and @AssertFalse you could do some incredibly complicated validations without needing to RYO validators. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4070172#4070172 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4070172 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - remoting with security
I am attempting to secure our @WebRemote methods and I'm having a bit of trouble. I have a SB with two @WebRemote methods. I then put a @Restrict on the SB implementation class. When a call is made to one of the methods from the javascript, it does correctly validate that the restrictions are met. However, the response from the server is a 200 status with an empty responseText. Thus, I cannot automatically redirect the user to a login page (like Ajax4jsf does). Note that the server prints out the NotLoggedInException (and AuthorizationException) in the logs. Is there a way to hook up the ExceptionFilter to the Seam Remoting requests? Thanks! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042150#4042150 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042150 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: two transactions, one entityManager
Thanks petemuir and vladimir. The approach that we decide to take was to connect the modal dialog to a @WebRemote. This isolates the alert transaction to a separate conversation. It is probably better this way since I don't have to worry about JSF restoring the view each time we ask for more alerts from the server. Thus, as expected, performance is considerably faster. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042154#4042154 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042154 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: remoting with security
Maybe the solution is to change the Remoting class so that it throws rather than swallows all Exceptions. In theory, wouldn't the exception bubble up through the ServletRequest all the way to the ExceptionFilter? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042169#4042169 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042169 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Changeing Validation Messages
For the hibernate validator, message keys should not be demarcated with #{}.
Simply drop the #.
@NotNull(message={messages.notnullerror})
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042237#4042237
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042237
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - two transactions, one entityManager
We have an application where every 5 minutes an a4j:poll queries to see if there are any user alerts to display. If there is an alert, the user is presented with a modal dialog. They then click an OK button on the dialog which causes the Alert to save to the database with the acknowledgment time. This alert dialog can be displayed on any screen in the application, but the alert acknowledgment action should not participate in those screen's transactions. It works great in every scenario except for the following: The user is on an edit screen and is making changes. A new alert modal dialog is displayed and the user clicks OK. The alert acknowledgment time is saved, but so are the user's changes on the edit screen. This is not good. The alert action is a Stateful EJB. I have tried numerous ways to get this to occur how I want using @TransactionAttribute.NOT_SUPPORTED, REQUIRES_NEW, but I just cannot get it to work. When the form posts and the acknowledge alert action is called, is it possible that the form values for the edit screen are also being applied to this new nested transaction or is the transaction demarcation not really occurring like I think it is? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4041932#4041932 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041932 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: two transactions, one entityManager
I also failed to mention that I have tried MANUAL and AUTO flush mode with no change in behavior. I have also tried manually creating a nested conversation in the action and then popping it at the end. No change in behavior. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4041952#4041952 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041952 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - EntityConverted and EmbeddedId
Now that the EntityConverter has been rewritten to convert ID objects to Integers can the @EmbeddedId annotation now be supported? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4034822#4034822 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034822 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Injection of a stateless session bean (SLSB) into anothe
Did you try | @In(create=true) | SimpleBean simpleBean; | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4034825#4034825 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034825 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Injected SLSB not getting interceptors sometimes
Instead of using the Logger annotation, you could try looking up the Log using one of the Logging static methods. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4034826#4034826 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034826 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Switching SEAM 1.2 to JSF 1.2 RI problem
The only thing we had to do was just to make sure we had this listener in the web.xml | listener | listener-classcom.sun.faces.config.ConfigureListener/listener-class | /listener | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4030244#4030244 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4030244 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Why does ModelValidator use SEVERITY_WARN
In almost all UIComponents I've seen, validation errors create SEVERITY_ERROR FacesMessages. However, the ModelValidator creates SEVERITY_WARN FacesMessages. | 1. Why does it use SEVERITY_WARN instead of SEVERITY_ERROR? | 2. Other than writing my own ModelValidator, how can I change this behavior? | | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4027582#4027582 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027582 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Remoting in CVS is currently broken
Seam Remoting is currently throwing an UnsupportedOperationException | java.lang.UnsupportedOperationException: Cannot post to the resource servlet | at org.jboss.seam.servlet.ResourceServlet.doPost(ResourceServlet.java:107) | Seam XMLHttpRequests are POSTs so either the doPost should work, or the remoting requests need to go to something that doesn't satisfy the /seam/resource/* url-pattern. This doPost change was made pretty recently because I have been updating my CVS tree on a daily basis and I'm just now seeing this problem. Based on the documentation and current examples I have the following configuration. | filter | filter-nameSeam Filter/filter-name | filter-classorg.jboss.seam.web.SeamFilter/filter-class | /filter | | filter-mapping | filter-nameSeam Filter/filter-name | url-pattern/*/url-pattern | /filter-mapping | | servlet | servlet-nameSeam Resource Servlet/servlet-name | servlet-classorg.jboss.seam.servlet.ResourceServlet/servlet-class | /servlet | | servlet-mapping | servlet-nameSeam Resource Servlet/servlet-name | url-pattern/seam/resource/*/url-pattern | /servlet-mapping | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4026450#4026450 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4026450 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: jndi name of ejb in ear
Thanks. We settled on hardcoding the ear name in the @JndiName for each service along with placing it in the components.xml. This way, if the ear name changes, the services are still bound to the same namespace. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3991424#3991424 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3991424 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - jndi name of ejb in ear
EJBs deployed from an EAR are put under the EAR's jndi namespace. For instance
if the ear file is my-ear.ear, and there is a Local Session Bean with the
name of MySessionBean, it will be bound to my-ear/MySessionBean. In order
for Seam to lookup this EJB, it requires a change to the components.xml so that
instead of using #{ejbName}/local it uses my-ear/#{ejbName}/local. While
this works great, the ear name is now hardcoded in the ejb jar module inside of
the ear. This isn't such a big problem until someone renames the ear file. At
this point,the components.xml has to be updated since Seam can no longer find
my-ear/MySessionBean/local. This is a big problem, especially when trying to
run multiple versions of the same application on a single server.
One possibility to fix the problem is to override the jndi name using either
the @LocalBinding or @JndiName annotations. However, the jndi bindings of
different EARS can collide since they both name is now hardcoded in the Java
class.
Would it be possible for the Seam jndiPattern to automatically look in the
EAR's jndi namespace?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3991091#3991091
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3991091
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: conversational bean not always redirecting to ifNotBegun
LOL. Sounds like a good way to keep QA on their toes. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3971602#3971602 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971602 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: One to one doubt
What about the server's log file? If a conversion error is occuring, I would expect something like a NullPointerException or a ClassCastException. It sounds more like a JSF issue than a Seam issue. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3971363#3971363 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971363 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: conversational bean not always redirecting to ifNotBegun
What nightly build would be a good place to start? Is the current code base in CVS production worthy for an internal application with 70 users? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3971364#3971364 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971364 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - conversational bean not always redirecting to ifNotBegunOutc
This is probably my misunderstanding of the phases and conversations, but here it goes We have a seam app with a lot of @Conversational beans. Many of these beans support wizards. If a user is on the nth page of one of the wizards, and the server was just bounced, I would expect the Next button to automatically redirect them to the ifNotBegunOutcome of the class associated with the Next buttons action method. However, in most scenarios, it lets the Next go through and the user is shown a nonsense wizard page filled with blanks. It appears that the problem has to do with the sequence of the the Conversational check and the instantiation of the components associated with the form post. Conversational checks only occur in the INVOKE_APPLICATION phase. If the Conversational bean does not exist in the conversation scope, it will redirect to the ifNotBegunOutcome. However, during the APPLY_REQUEST_VALUES phase, the Conversational beans have already bean instantiated by the SeamVariableResolver. For instance, in the log below, we are demonstrating what happens when we click the Next button on an action that uses the worksheetBean. I had just restarted the server (and thus the conversation was gone). Because the worksheetBean is instantiated by the SeamVariableResolver, the intended Conversational check never occurs. What can we do about this? | 2006-09-12 14:40:21,162 DEBUG [com.app.web.listener.LogPhaseListener] BEFORE: APPLY_REQUEST_VALUES(2) | 2006-09-12 14:40:21,240 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, [EMAIL PROTECTED], [EMAIL PROTECTED] url=null ,addedOrder=0} | 2006-09-12 14:40:21,240 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, [EMAIL PROTECTED], [EMAIL PROTECTED] url=null ,addedOrder=0} | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: userPrincipal | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.contexts.Contexts] found in application context: userPrincipal | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolved name to seam component | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: userPrincipal | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.contexts.Contexts] found in application context: userPrincipal | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolved name to seam component | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: applicationMessages | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.Component] instantiating Seam component: applicationMessages | 2006-09-12 14:40:21,271 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolved name to seam component | 2006-09-12 14:40:21,287 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, [EMAIL PROTECTED], [EMAIL PROTECTED] url=null ,addedOrder=0} | 2006-09-12 14:40:21,287 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: worksheetBean | 2006-09-12 14:40:21,287 DEBUG [org.jboss.seam.Component] instantiating Seam component: worksheetBean | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3971106#3971106 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971106 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Long Running Conversation Timeouts are never occuring
Thanks for the clarifications on this. If I were developing a new application that allowed users to hold onto tickets for five minutes, I would have originally thought that I could simply use the Conversation timeout. But since this is not the case, it would be important that I understand that I need to design the the ticket timeout behavior into my code. In order to avoid further confusion on this issue, the documentation in 11.4 and 11.8 should probably be clarified. E.g in 11.8 anonymous wrote : | Internal component for Seam page and conversation context management. Always installed. | * org.jboss.seam.core.manager.conversationTimeout ? the conversation context timeout in milliseconds. | Could be changed to something like anonymous wrote : | Internal component for Seam page and conversation context management. Always installed. | * org.jboss.seam.core.manager.conversationTimeout ? the non foreground conversation context timeout in milliseconds. A non foreground conversation is a conversation not associated with the current request. | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970747#3970747 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970747 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Long Running Conversation Timeouts are never occuring
We are having issues with conversations being timed out in 1.0.1GA. This may
be fixed in the CVS version.
We have set the org.jboss.seam.core.Manager.conversationTimeout to 15 seconds
through use of a components.xml.
After pausing on a conversational page for 30 seconds, we attempt to see if the
conversation did timeout. When we click the Save link on our page, it allows
the request to go through without redirecting to the No Conversation page.
In order to debug the issue, we set some breakpoints in
Manager.setLongRunningConversation, Manager.storeConversation, and
Manager.conversationTimeout to
see how things are playing out.
When we click the Save link, the first thing that happens is the conversation
is restored.
At this point, the longRunningConversation is set to true.
Stack trace
| Thread [http-0.0.0.0-8080-2] (Suspended (entry into method
setLongRunningConversation in Manager))
| Manager.setLongRunningConversation(boolean) line: 294
| Manager.restoreConversation(String) line: 587
| Manager.restoreConversation(Map) line: 521
| AbstractSeamPhaseListener.restoreAnyConversationContext(FacesContext)
line: 41
| SeamPhaseListener.afterPhase(PhaseEvent) line: 63
| PhaseListenerManager.informPhaseListenersAfter(PhaseId) line: 89
| LifecycleImpl.restoreView(FacesContext, PhaseListenerManager) line: 181
| LifecycleImpl.execute(FacesContext) line: 66
| FacesServlet.service(ServletRequest, ServletResponse) line: 137
| ApplicationFilterChain.internalDoFilter(ServletRequest,
ServletResponse) line: 252
| ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
173
| ExtensionsFilter.doFilter(ServletRequest, ServletResponse, FilterChain)
line: 144
| ApplicationFilterChain.internalDoFilter(ServletRequest,
ServletResponse) line: 202
| ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
173
| SeamRedirectFilter.doFilter(ServletRequest, ServletResponse,
FilterChain) line: 30
| ApplicationFilterChain.internalDoFilter(ServletRequest,
ServletResponse) line: 202
| ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
173
| ReplyHeaderFilter.doFilter(ServletRequest, ServletResponse,
FilterChain) line: 96
| ApplicationFilterChain.internalDoFilter(ServletRequest,
ServletResponse) line: 202
| ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
173
| StandardWrapperValve.invoke(Request, Response) line: 213
| StandardContextValve.invoke(Request, Response) line: 178
| SecurityAssociationValve.invoke(Request, Response) line: 175
| BasicAuthenticator(AuthenticatorBase).invoke(Request, Response) line:
524
| JaccContextValve.invoke(Request, Response) line: 74
| StandardHostValve.invoke(Request, Response) line: 126
| ErrorReportValve.invoke(Request, Response) line: 105
| StandardEngineValve.invoke(Request, Response) line: 107
| CoyoteAdapter.service(Request, Response) line: 148
| Http11Processor.process(InputStream, OutputStream) line: 869
|
Http11Protocol$JmxHttp11ConnectionHandler(Http11BaseProtocol$Http11ConnectionHandler).processConnection(TcpConnection,
Object[]) line: 664
| PoolTcpEndpoint.processSocket(Socket, TcpConnection, Object[]) line: 527
| MasterSlaveWorkerThread.run() line: 112
| ThreadWithAttributes(Thread).run() line: 595
|
Because the longRunningConversation is true, the conversation is touched.
When the conversation is touched, the ConversationEntry.lastRequestTime is
updated to the current time.
|public void storeConversation(ContextAdaptor session, Object response)
|
| if ( isLongRunningConversation() )
| {
| touchConversationStack();
| if ( !Seam.isSessionInvalid() )
| {
| forceMutableComponentReplication();
| storeLongRunningConversation(response);
| }
| }
| else
| {
| discardTemporaryConversation(session, response);
| }
|
|
Stack trace
| Thread [http-0.0.0.0-8080-1] (Suspended (entry into method
touchConversationStack in Manager))
| Manager.touchConversationStack() line: 164
| Manager.storeConversation(ContextAdaptor, Object) line: 368
| AbstractSeamPhaseListener.storeAnyConversationContext(FacesContext)
line: 69
| SeamStateManager.saveSerializedView(FacesContext) line: 45
| FaceletViewHandler.renderView(FacesContext, UIViewRoot) line: 578
| LifecycleImpl.render(FacesContext) line: 384
| FacesServlet.service(ServletRequest, ServletResponse) line: 138
| ApplicationFilterChain.internalDoFilter(ServletRequest,
ServletResponse) line: 252
| ApplicationFilterChain.doFilter(ServletRequest, ServletResponse) line:
173
| ExtensionsFilter.doFilter(ServletRequest, ServletResponse,
[jboss-user] [JBoss Seam] - Re: Long Running Conversation Timeouts are never occuring
In order to get the correct behavior, I will assume that we need to make our conversationTimeout to be equal to the session timeout. This is good to know since it is the single biggest issue reported by the users of our Seam based application. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970412#3970412 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970412 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Long Running Conversation Timeouts are never occuring
Also, just to clarify, what is the foreground conversation? Is it the conversation associated with the current request? So the only conversations that would ever get cleaned up are those not part of the current request. Scenario: I have two browser instances open and I leave my desk for 20 minutes. When I come back to my desk, I click on a link in one of the browser windows. If I clicked a link in Browser A, it will only expire the conversation for Browser B. However, If I clicked a link in Browser B, it will expire the conversation for Browser A. This seems unintuitive. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3970421#3970421 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970421 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Joining an existing conversation
http://docs.jboss.com/seam/1.0.1.GA/reference/en/html/remoting.html#d0e4175
For instance,
| function callMyRemoteMethod(conversationId, otherArg)
| {
| Seam.Remoting.getContext().setConversationId(conversationId);
| var callback = function() { alert('remote method done!'); };
|
| var myComponent = Seam.Component.getInstance('MyComponent');
| myComponent.myRemoteMethod(otherArg, callback);
| }
|
And then in your page, make sure to call the javascript method with the
conversationId.
For instance,
| h:commandButton
onclick=javascript:callMyRemoteMethod(#{conversation.id}, 'FOO'); return
false; value=Click Me!/
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3958946#3958946
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3958946
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
