March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6635) EJB2 CMB beans: ejbActivate callback is called after the bean creation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6635?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-6635. ----------------------------------- Resolution: Won't Fix Resolving as Won't Fix as CMP support has been removed from upstream AS. The linked bugzilla entry can track this for EAP. > EJB2 CMB beans: ejbActivate callback is called after the bean creation > ----------------------------------------------------------------------- > > Key: AS7-6635 > URL: https://issues.jboss.org/browse/AS7-6635 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Labels: cmp, ejb, entities, entity > > Called ejbActive after the create() call on home interface is incorrect by spec. > 10.1.3 > There are two possible transitions from the pooled to the ready state: through the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods, or through the ejbActivate method. The container invokes the ejbCreate<METHOD> and ejbPostCreate<METHOD> methods when the instance is assigned to an entity object during entity object creation. > The container invokes the ejbActivate method on an instance when an instance needs to be activated to service an invocation on an existing entity object—this occurs because there is no suitable instance in the ready state to service the client’s call or the ejbTimeout method. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6780) Default config is not using most up to date schemas

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6780?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6780: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 926002|https://bugzilla.redhat.com/show_bug.cgi?id=926002] from POST to MODIFIED > Default config is not using most up to date schemas > --------------------------------------------------- > > Key: AS7-6780 > URL: https://issues.jboss.org/browse/AS7-6780 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > We also need to add a test to prevent this from happening in future -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6782) JAX-RS does not work with EJB's with a non-default name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6782?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6782: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 927021|https://bugzilla.redhat.com/show_bug.cgi?id=927021] from POST to MODIFIED > JAX-RS does not work with EJB's with a non-default name > ------------------------------------------------------- > > Key: AS7-6782 > URL: https://issues.jboss.org/browse/AS7-6782 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6681: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 920367|https://bugzilla.redhat.com/show_bug.cgi?id=920367] from POST to MODIFIED > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Fix For: 8.0.0.Alpha1 > > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6648) pooled-connection-factory's inbound-config is not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6648?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6648: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 900842|https://bugzilla.redhat.com/show_bug.cgi?id=900842] from POST to MODIFIED > pooled-connection-factory's inbound-config is not persisted > ----------------------------------------------------------- > > Key: AS7-6648 > URL: https://issues.jboss.org/browse/AS7-6648 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The code to persist pooled-connection-factory's inbound-config is not correct in MessagingXMLWriter (the pooled-connection-factory ModelNode layout does not have an intermediate inbound-config node): any changes to AS7 configuration will discard the <inbound-config> element from the persisted XML files -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6583) Performance regression comparing to previous release

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6583?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6583: --------------------------------------- Can this be resolved? > Performance regression comparing to previous release > ---------------------------------------------------- > > Key: AS7-6583 > URL: https://issues.jboss.org/browse/AS7-6583 > Project: Application Server 7 > Issue Type: Bug > Components: CDI / Weld, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: 7.2.0.Final (prerelease-1 tag) > Reporter: Tomas Remes > Assignee: James Perkins > Priority: Critical > Labels: performance > Attachments: AS7-snapshot-good.jps, AS7-snapshot-wrong.jps > > > There is significant performance regression in 7.2.0 prerelease. I discovered it in my Weld performance load tests (testing simple Weld numberguess example application), but I am quite sure that's not Weld issue at all. I did some investigations and it seems that problem occurred in org/jboss/as/logging module. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6526) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6526: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 928922|https://bugzilla.redhat.com/show_bug.cgi?id=928922] from NEW to POST > It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent > ----------------------------------------------------------------------------------------------------- > > Key: AS7-6526 > URL: https://issues.jboss.org/browse/AS7-6526 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6813) Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-6813: ------------------------------------- Summary: Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase Key: AS7-6813 URL: https://issues.jboss.org/browse/AS7-6813 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite, Web Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha1 I have marked this test as "@Ignore"d as I do not believe the capability that is being tested is actually valid. I can not find any evidence that we ever intended for a role to role mapping within the jboss-web.xml instead we only intended a principal to role mapping. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6526) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6526: ---------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> made a comment on [bug 928922|https://bugzilla.redhat.com/show_bug.cgi?id=928922] It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. https://issues.jboss.org/browse/AS7-6526 > It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent > ----------------------------------------------------------------------------------------------------- > > Key: AS7-6526 > URL: https://issues.jboss.org/browse/AS7-6526 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6526) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6526: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=928922 > It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent > ----------------------------------------------------------------------------------------------------- > > Key: AS7-6526 > URL: https://issues.jboss.org/browse/AS7-6526 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. -- 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

11 years, 1 month

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 March 2013