July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9099) Handle reconnection of hosts to the domain

by Brian Stansberry (JIRA)

Handle reconnection of hosts to the domain ------------------------------------------ Key: JBAS-9099 URL: https://issues.jboss.org/browse/JBAS-9099 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.CR1 Establish processes for host controllers to reconnect to the master domain controller if communication is disrupted and thereafter synchronize themselves (and their servers) with the domain. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
8
0 / 0

[JBoss JIRA] Created: (AS7-1253) Package org.jboss.as.clustering has classes in multiple modules

by Brian Stansberry (JIRA)

Package org.jboss.as.clustering has classes in multiple modules --------------------------------------------------------------- Key: AS7-1253 URL: https://issues.jboss.org/browse/AS7-1253 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Fix For: 7.0.1.Final Package splitting is verbotten in AS 7, even if all the jars are meant to be used as a unit. This is probably the result of the split of the clustering module into multiple pieces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-9369) Implement Namespace resolution policy

by David Lloyd (JIRA)

Implement Namespace resolution policy ------------------------------------- Key: JBAS-9369 URL: https://issues.jboss.org/browse/JBAS-9369 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE, Naming Reporter: David Lloyd Assignee: John Bailey Fix For: 7.0.0.Beta4 Perform the following automatic translations: * {{foo/bar/baz}} becomes {{java:jboss/env/foo/bar/baz}} ** if a component is in scope, instead use {{java:comp/env/foo/bar/baz}} or {{java:module/env/foo/bar/baz}} as appropriate * {{java:/foo/bar/baz}} => {{java:jboss/root/foo/bar/baz}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-8338) handling of service start failure

by Alexey Loubyansky (JIRA)

handling of service start failure --------------------------------- Key: JBAS-8338 URL: https://jira.jboss.org/browse/JBAS-8338 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 In this case, the exception is logged, and all the service's dependents will be trapped in a waiting state. This type of error will typically be due to transient conditions, like an incorrectly configured IP address, disk space issues, and so on. The correct behavior here is to log the error and let the user decide (based on the GUI or perhaps by deployment plan policy) whether to fix the issue and retry the failed service, let the error stand, or pull out the deployment unit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
8
0 / 0

[JBoss JIRA] Created: (SECURITY-440) JBossXACML:: bug identified implementing RBAC

by Anil Saldhana (JIRA)

JBossXACML:: bug identified implementing RBAC --------------------------------------------- Key: SECURITY-440 URL: https://jira.jboss.org/jira/browse/SECURITY-440 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Reporter: Anil Saldhana Assignee: Anil Saldhana -- 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

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (SECURITY-590) RequestAttributeFactory.createTimeAttributeType(attName, issuer) API call causes a parsing exception

by Asankha Perera (JIRA)

RequestAttributeFactory.createTimeAttributeType(attName, issuer) API call causes a parsing exception ---------------------------------------------------------------------------------------------------- Key: SECURITY-590 URL: https://issues.jboss.org/browse/SECURITY-590 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Environment: Version was 2.0.6.Final Reporter: Asankha Perera Assignee: Anil Saldhana Priority: Minor Using the API call RequestAttributeFactory.createTimeAttributeType(attName, issuer) causes a "ParsingException: couldn't create http://www.w3.org/2001/XMLSchema#time attribute based on DOM node" Note that with the above API call, we do not supply any time string, but assume that the current time is used. As a comparison the similar API call RequestAttributeFactory.createDateTimeAttributeType(attName, issuer) works without any issues - hence it seems logical that the createTimeAttributeType() contains a possible bug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

7
8
0 / 0

[JBoss JIRA] Created: (JBAS-9424) MDB's are started *BEFORE* EJB's are jndi-bound

by Bernard Ligny (JIRA)

MDB's are started *BEFORE* EJB's are jndi-bound ----------------------------------------------- Key: JBAS-9424 URL: https://issues.jboss.org/browse/JBAS-9424 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB, Weld/CDI Affects Versions: 6.0.0.Final Environment: All (*NIX, Mac-Os-X and Win) Reporter: Bernard Ligny Assignee: Carlo de Wolf Priority: Critical I recently noticed a very strange behaviour (with JBOSS AS 6) with Message-Driven-Beans where we inject EJB. If the JMS queue is empty when the jboss server is started, then everything work's fine. If, no luck, the jms queue is *NOT* empty, my MDB is apparently mounted *BEFORE* the ejb's and the @Inject failed: => "Failure WELD-000079 Could not find the EJB in JNDI: class xxx" I further investigated the problem: I replaced the @Inject annotation, with a "manual" lookup of my ejb using the javax.enterprise.inject.spi.BeanManager capabilities (that i put in a @Postcontruct method of my MDB), The trick consisted in trying the lookup n times with a delay of x sec between each attempt. Here are the results (excerpt from server.log): 2011-07-28 12:05:06,180 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [1] Trying to lookup KernelResources 2011-07-28 12:05:06,190 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [1] Failure WELD-000079 Could not find the EJB in JNDI: class net.haulogy.energycomm.kernel.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Users$bli$Devware$jboss-6$0$0$Dev$server$default$deploy$energycomm-ear$ear"-SessionBean-KernelResources_$$_WeldProxy ... 2011-07-28 12:05:11,191 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [2] Trying to lookup KernelResources 2011-07-28 12:05:11,192 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [2] Failure WELD-000079 Could not find the EJB in JNDI: class net.haulogy.energycomm.kernel.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Users$bli$Devware$jboss-6$0$0$Dev$server$default$deploy$energycomm-ear$ear"-SessionBean-KernelResources_$$_WeldProxy ... 2011-07-28 12:05:16,193 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [3] Trying to lookup KernelResources 2011-07-28 12:05:16,193 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [3] Failure WELD-000079 Could not find the EJB in JNDI: class net.haulogy.energycomm.kernel.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Users$bli$Devware$jboss-6$0$0$Dev$server$default$deploy$energycomm-ear$ear"-SessionBean-KernelResources_$$_WeldProxy ... 2011-07-28 12:05:21,194 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [4] Trying to lookup KernelResources 2011-07-28 12:05:21,194 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [4] Failure WELD-000079 Could not find the EJB in JNDI: class net.haulogy.energycomm.kernel.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Users$bli$Devware$jboss-6$0$0$Dev$server$default$deploy$energycomm-ear$ear"-SessionBean-KernelResources_$$_WeldProxy ... 2011-07-28 12:05:26,195 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [5] Trying to lookup KernelResources 2011-07-28 12:05:26,195 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [5] Failure WELD-000079 Could not find the EJB in JNDI: class net.haulogy.energycomm.kernel.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$Users$bli$Devware$jboss-6$0$0$Dev$server$default$deploy$energycomm-ear$ear"-SessionBean-KernelResources_$$_WeldProxy ... 2011-07-28 12:05:26,215 INFO [org.jboss.ejb3.nointerface.impl.jndi.AbstractNoInterfaceViewBinder] (Thread-3) Binding the following entry in Global JNDI for bean:KernelResources => finally the EJB is bound ! 2011-07-28 12:05:31,196 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** [6] Trying to lookup KernelResources 2011-07-28 12:05:31,197 INFO [STDOUT] (Thread-0 (group:HornetQ-client-global-threads-183899831)) *** KernelResources = No-Interface view for endpoint [ jboss.j2ee:ear=energycomm-ear.ear,jar=energycomm-kernel-0.5.0-SNAPSHOT.jar,name=KernelResources,service=EJB3 ] => the 6th attempt now works :-) Conclusion: according to me, there is no doubt: dependencies between MDB's and EJB's are not correctly managed by the app server. The app server should wait for all EJB's to be bound before activating the MDB. MDB are activated too early (especially when jms queue is not empty at starttime) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1293) Cleanup dependencies of ejb3-core

by Carlo de Wolf (JIRA)

Cleanup dependencies of ejb3-core --------------------------------- Key: EJBTHREE-1293 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1293 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 The goal is to have ejb3-core not depend on any jboss-as artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2057) Fix testsuite regression related to HornetQ integration

by Carlo de Wolf (JIRA)

Fix testsuite regression related to HornetQ integration ------------------------------------------------------- Key: EJBTHREE-2057 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2057 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Priority: Critical Fix For: EJB3_1 1.0.6 -- 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

13 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1343) Remove the cyclical dependency from ejb3/core to org.jboss.jbossas-jboss-as-server

by Dimitris Andreadis (JIRA)

Remove the cyclical dependency from ejb3/core to org.jboss.jbossas-jboss-as-server ---------------------------------------------------------------------------------- Key: EJBTHREE-1343 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1343 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Dimitris Andreadis Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.CR1 ejb3/core -> jboss-as-server dependencies ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.corba.ORBFactory ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.naming.client.java.HandleDelegateFactory; ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/AllowedOperationsInterceptor.java ./org/jboss/ejb3/service/ServiceContainer.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.AllowedOperationsAssociation ejb3/core ./org/jboss/ejb3/mdb/MessagingContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.jms.jndi.JMSProviderAdapter; org.jboss.jbossas:jboss-as-server ----------------------------------------- ejb3/core ./org/jboss/ejb3/timerservice/jboss/JBossTimerServiceFactory.java ./org/jboss/ejb3/timerservice/TimedObjectInvoker.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.txtimer.EJBTimerService; org.jboss.ejb.txtimer.TimedObjectInvoker ----------------------------------------- ejb3/core ./org/jboss/ejb3/stateful/StatefulLocalProxyFactory.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.proxy.ejb.handle.StatefulHandleImpl; org.jboss.proxy.ejb.handle.HomeHandleImpl; ------------------------------------------ ejb3/core ./org/jboss/ejb3/AllowedOperationsInterceptor.java ./org/jboss/ejb3/ContainerPlugin.java ./org/jboss/ejb3/service/ServiceContainer.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.AllowedOperationsFlags ------------------------------------------- ejb3/core ./org/jboss/ejb3/EJBProxyFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.invocation.Invocation -------------------------------------------- ejb3/core ./org/jboss/ejb3/EJBProxyFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.GenericEntityObjectFactory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011