[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3566) Conversation.isLongRunning() causes NPE

[Shane Bryzak (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Bryzak updated JBSEAM-3566:
---------------------------------

    Fix Version/s: 2.1.2.CR1
                       (was: 2.1.1.CR1)


I'm not able to reproduce this.  Could you please attach a runnable test case with instructions on how to reproduce?

> Conversation.isLongRunning() causes NPE
> ---------------------------------------
>
>                 Key: JBSEAM-3566
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3566
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.3.CR1
>         Environment: JBoss 4.2.2, Seam 2.0.3.CR1
>            Reporter: Nikolay Elenkov
>             Fix For: 2.1.2.CR1
>
>
> I have a couple of methods that log conversation start/end for debugging purposes in may app. 
> The code is pretty simple:
> @Observer(value = "org.jboss.seam.beginConversation")
> public void onConversationStart() {
>   log.debug("CONVERSATION Started");
>   Conversation c = Conversation.instance();
>   log.debug(String.format("id: %s; isLongRunning %s; viewId: %s", 
> 	c.getId(), c.isLongRunning(), c.getViewId()));
> }
> Most of the time that works OK, but I get an occasional NPE, seems to happen when 
> you access the app right after JBoss has started. Here is the trace:
> Caused by: java.lang.NullPointerException
> 	at org.jboss.seam.core.Manager.isReallyLongRunningConversation(Manager.java:230)
> 	at org.jboss.seam.core.Conversation.isLongRunning(Conversation.java:308)
> 	at myapp.LoggerBean.onConversationEnd(LoggerBean.java:145)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira