December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-9405) could not find stateful bean - error

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBAS-9405?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated JBAS-9405: --------------------------------------- Forum Reference: http://community.jboss.org/message/610094#610094, https://community.jboss.org/message/783547#783547 (was: http://community.jboss.org/message/610094#610094) > could not find stateful bean - error > ------------------------------------ > > Key: JBAS-9405 > URL: https://issues.jboss.org/browse/JBAS-9405 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Environment: Red hat Linux 5.5 > Reporter: Jboss fan99 > Assignee: Alexey Loubyansky > > If I leave my browser idle for some time (around 3 mins), I get "Could not find stateful bean:" error. > javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > > I grepped by bean id in logs and found below. Not sure but seems like bean is removed before it's attempted to read again. > Is there any configuration I can do to avoid this error. > > [root@localhost log]# grep 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da * > server.log:2011-06-10 18:56:25,652 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Attempting to passivate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:56:25,660 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Saving session state to: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser > server.log:2011-06-10 18:56:27,206 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Passivation complete; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:16,744 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:16,744 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Reading session state from: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser > server.log:2011-06-10 18:57:16,763 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Removing passivated state file: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser > server.log:2011-06-10 18:57:16,979 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:16,985 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:16,987 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:16,989 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:27,893 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:27,894 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-127.0.0.1-80-1) Error Rendering View[/index.xhtml]: javax.el.ELException: /sections/leftSideBar.xhtml @14,46 rendered="#{! loginbacking.loggedIn}": javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:Caused by: javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da > server.log:2011-06-10 18:57:27,998 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6186) Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/AS7-6186?page=com.atlassian.jira.plugin.s... ] Marek Schmidt updated AS7-6186: ------------------------------- Attachment: seam-booking.ear > Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations > ----------------------------------------------------- > > Key: AS7-6186 > URL: https://issues.jboss.org/browse/AS7-6186 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: 7.1.4.Final (EAP) > Environment: Current 7.1.4.Final-SNAPSHOT (2012-12-15), Mojarra 2.1.16, Seam2.3.0.Final > Reporter: Marek Schmidt > Assignee: Stan Silvert > Priority: Critical > Attachments: seam-booking.ear > > > Recent Mojarra upgrade seems to break Seam 2.3.0 conversations. > Not exactly sure yet what has changed and whether it is a Mojarra bug or Seam depending on something it shouldn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6186) Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/AS7-6186?page=com.atlassian.jira.plugin.s... ] Marek Schmidt updated AS7-6186: ------------------------------- Steps to Reproduce: 0. deploy Seam2.3.0 booking example application 1. open http://127.0.0.1:8080/seam-booking 2. login as gavin/foobar 3. choose a hotel 4. click on "bool hotel" 5. notice a "The conversation ended, timed out or was processing another request" messsage appears. was: 1. deploy Seam2.3.0 booking example application 2. login as gavin/foobar 3. choose a hotel 4. click on "bool hotel" 5. notice a "The conversation ended, timed out or was processing another request" messsage appears. > Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations > ----------------------------------------------------- > > Key: AS7-6186 > URL: https://issues.jboss.org/browse/AS7-6186 > Project: Application Server 7 > Issue Type: Bug > Components: JSF > Affects Versions: 7.1.4.Final (EAP) > Environment: Current 7.1.4.Final-SNAPSHOT (2012-12-15), Mojarra 2.1.16, Seam2.3.0.Final > Reporter: Marek Schmidt > Assignee: Stan Silvert > Priority: Critical > Attachments: seam-booking.ear > > > Recent Mojarra upgrade seems to break Seam 2.3.0 conversations. > Not exactly sure yet what has changed and whether it is a Mojarra bug or Seam depending on something it shouldn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6186) Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations

by Marek Schmidt (JIRA)

Marek Schmidt created AS7-6186: ---------------------------------- Summary: Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations Key: AS7-6186 URL: https://issues.jboss.org/browse/AS7-6186 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.4.Final (EAP) Environment: Current 7.1.4.Final-SNAPSHOT (2012-12-15), Mojarra 2.1.16, Seam2.3.0.Final Reporter: Marek Schmidt Assignee: Stan Silvert Priority: Critical Recent Mojarra upgrade seems to break Seam 2.3.0 conversations. Not exactly sure yet what has changed and whether it is a Mojarra bug or Seam depending on something it shouldn't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment

by Guy Kaisin (JIRA)

[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] Guy Kaisin commented on AS7-5584: --------------------------------- Hi all, I think that bug should be reopened... G. > Naming context read-only during SAR deployment > ---------------------------------------------- > > Key: AS7-5584 > URL: https://issues.jboss.org/browse/AS7-5584 > Project: Application Server 7 > Issue Type: Bug > Components: POJO > Affects Versions: 7.1.1.Final > Reporter: Philippe Marschall > Assignee: Philippe Marschall > Fix For: 7.2.0.Alpha1 > > > During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}} > http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-711) LdapExtAdLoginModule proposal for inclusion

by Péter Radics (JIRA)

[ https://issues.jboss.org/browse/SECURITY-711?page=com.atlassian.jira.plug... ] Péter Radics commented on SECURITY-711: --------------------------------------- I understand that introducing yet-another ldap login module is probably not the best idea, but I didn't want to break any existing functionality of the current LdapExtLoginModule when I created the version that works in our AD setup. The third patch though can be considered a fix for a performance issue in the current LdapExtLoginModule, and doesn't break any of its existing functionality. It's an improvement for all LDAP setups where the role attribute is a DN (Active Directory happens to use such a setup, but there're probably others, too). In any case, I just read the Tom Fonteyne is also working on the performance issue, and he'll commit his changes soon, so hopefully this issue can be closed. > LdapExtAdLoginModule proposal for inclusion > ------------------------------------------- > > Key: SECURITY-711 > URL: https://issues.jboss.org/browse/SECURITY-711 > Project: PicketBox > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: PicketBox, Security SPI > Affects Versions: PicketBox_4_0_14.Final > Environment: jboss7, active directory authentication > Reporter: Péter Radics > Assignee: Anil Saldhana > Priority: Minor > Labels: LdapExtLoginModule, active-directory, security > Attachments: picketbox-r359-LdapExtLoginModule.patch, picketbox-r362-LdapExtAdLoginModule.patch, picketbox-r363-LdapExtAdLoginModule-with-history.patch > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Please consider including the attached LdapExtAdLoginModule into the official release. This login module is based on r362 of LdapExtLoginModule, but it's better suited for deeply nested Active Directory domains: it only uses one search for the userDN then it's resolving the roles recursively by querying attributes on DNs only. (as a side-effect, it doesn't trigger AS7-5737) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6185) EJB2 CMP/CMR problem reading CMR in ejbStore() - IllegalStateException: ARJUNA016082: Synchronizations are not allowed!

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/AS7-6185?page=com.atlassian.jira.plugin.s... ] Brad Maxwell moved JBPAPP6-1730 to AS7-6185: -------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform 6) Key: AS7-6185 (was: JBPAPP6-1730) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.2.Final (EAP) (was: EAP 6.0.0) Component/s: EJB (was: EJB) (was: Transaction Manager) Security: (was: Public) Docs QE Status: (was: NEW) > EJB2 CMP/CMR problem reading CMR in ejbStore() - IllegalStateException: ARJUNA016082: Synchronizations are not allowed! > ----------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6185 > URL: https://issues.jboss.org/browse/AS7-6185 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.2.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Brad Maxwell > > If a CMR relation is loaded within the ejbStore() of an entity the transaction manager throw a IllegalStateException. > The scenario should be possible from EJB spec and it works in EAP5. > The log excerpt is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JASSIST-186) java.lang.VerifyError: Inconsistent args count operand in invokeinterface in method

by Matt Fowles (JIRA)

[ https://issues.jboss.org/browse/JASSIST-186?page=com.atlassian.jira.plugi... ] Matt Fowles commented on JASSIST-186: ------------------------------------- I just got hit by this issue as well. > java.lang.VerifyError: Inconsistent args count operand in invokeinterface in method > ----------------------------------------------------------------------------------- > > Key: JASSIST-186 > URL: https://issues.jboss.org/browse/JASSIST-186 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.17.0-GA, 3.17.1-GA > Reporter: Lauri Tulmin > Assignee: Shigeru Chiba > Attachments: javassist-bug2.zip > > > Happens when the argument of interface method call comes from anoter method call, like > {code} > m.insertBefore( > "{" + > " java.util.List l = new java.util.ArrayList();" + > " l.add(this.toString());" + > "}" > ); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBRULES-3706) Create a project that will allow Drools to be tested against many OSGi frameworks

by Cristiano Gavião (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3706?page=com.atlassian.jira.plug... ] Cristiano Gavião commented on JBRULES-3706: ------------------------------------------- Another important point that must be addressed is the package structure of existent tests. PAX-Exam requires that the test project be a OSGi bundle. So created "test-jar" must be OSGified before be reused. The problem is that currently tests packages names conflicts with source packages ones. So test packages names must be refactored. > Create a project that will allow Drools to be tested against many OSGi frameworks > --------------------------------------------------------------------------------- > > Key: JBRULES-3706 > URL: https://issues.jboss.org/browse/JBRULES-3706 > Project: JBRULES > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Cristiano Gavião > Assignee: Mark Proctor > Labels: OSGi > > The actual project that tests Drools in a OSGi platform was not defined for a reliable and consistent tests on more than one framework. > So the propose is to create a new project that will use Pax-Exam tool which will able to test Drools bundles in the most important existent frameworks: Equinox, Felix and Knopflerfish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBRULES-3706) Create a project that will allow Drools to be tested against many OSGi frameworks

by Cristiano Gavião (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3706?page=com.atlassian.jira.plug... ] Cristiano Gavião commented on JBRULES-3706: ------------------------------------------- The initial idea was to reuse many test cases already write for Drools as possible. But there are a thing that need be considered. At OSGi we get factories from services (KnowledgeBuilderFactoryService, KnowledgeBaseFactoryService, ResourceFactoryService). So existent tests that deals with factories must be refactored, or maybe recreated to be able to reused at OSGi. > Create a project that will allow Drools to be tested against many OSGi frameworks > --------------------------------------------------------------------------------- > > Key: JBRULES-3706 > URL: https://issues.jboss.org/browse/JBRULES-3706 > Project: JBRULES > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Cristiano Gavião > Assignee: Mark Proctor > Labels: OSGi > > The actual project that tests Drools in a OSGi platform was not defined for a reliable and consistent tests on more than one framework. > So the propose is to create a new project that will use Pax-Exam tool which will able to test Drools bundles in the most important existent frameworks: Equinox, Felix and Knopflerfish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012