April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1280) Make the setting of the ORB name in org.jboss.ejb3.EJBContainer configurable

by Dimitris Andreadis (JIRA)

Make the setting of the ORB name in org.jboss.ejb3.EJBContainer configurable ---------------------------------------------------------------------------- Key: EJBTHREE-1280 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1280 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Dimitris Andreadis Priority: Minor Fix For: HEAD While removing the cyclical dependency of ejb3-core to org.jbossjbossas:jboss-as-iiop, the default ORB name defined in: org.jboss.iiop.CorbaORBService.ORB_NAME = ""JBossCorbaORB" It is now hardcoded in org.jboss.ejb3.EJBContainer. The correct approach would make it configurable in EJB3, somehow. -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-21) Update to latest jboss-common-core, jboss-logging-spi, jboss-test

by Dimitris Andreadis (JIRA)

Update to latest jboss-common-core, jboss-logging-spi, jboss-test ----------------------------------------------------------------- Key: JBVFS-21 URL: http://jira.jboss.com/jira/browse/JBVFS-21 Project: JBoss VFS Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 2.0.0.Beta11 - <version.jboss.common.core>2.2.4.GA</version.jboss.common.core> - <version.jboss.logging>2.0.4.GA</version.jboss.logging> - <version.jboss.test>1.0.4.GA</version.jboss.test> + <version.jboss.common.core>2.2.5.GA</version.jboss.common.core> + <version.jboss.logging>2.0.5.GA</version.jboss.logging> + <version.jboss.test>1.1.0.GA</version.jboss.test> -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5444) remove twiddle.bat/shutdown.bat %ARGS% processing in favour of %*

by Dimitris Andreadis (JIRA)

remove twiddle.bat/shutdown.bat %ARGS% processing in favour of %* ----------------------------------------------------------------- Key: JBAS-5444 URL: http://jira.jboss.com/jira/browse/JBAS-5444 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA In twiddle.bat/shutdown.bat we need to replace %ARGS% with %* when including the command line arguments in the final JAVA execution. It causes problems when parameters include characters like ':', so the following twiddle query would fail, unless you use quotes: twiddle invoke jboss:service=JNDIView list true 12:26:29,031 ERROR [Twiddle] Exec failed javax.management.MalformedObjectNameException: Unterminated key property part at javax.management.ObjectName.construct(ObjectName.java:465) at javax.management.ObjectName.<init>(ObjectName.java:1304) at org.jboss.console.twiddle.command.MBeanServerCommand.queryMBeans(MBea nServerCommand.java:68) at org.jboss.console.twiddle.command.InvokeCommand.execute(InvokeCommand .java:283) at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:306) twiddle invoke "jboss:service=JNDIView" list true -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1278) Ejb3Deployments are not properly installed into mc to allow for dependency error reporting

by Scott M Stark (JIRA)

Ejb3Deployments are not properly installed into mc to allow for dependency error reporting ------------------------------------------------------------------------------------------ Key: EJBTHREE-1278 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1278 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: AS 5.0.0.Beta4 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: AS 5.0.0.CR1 The current direct installation of the ejb3 beans into the mc kernel bypasses the dependency error reporting mechanism associated with the deployers. All that should be happening is that the AbstractBeanMetaData that described the bean be added as an attachment to the deployment. -- 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-2575) Hibernate usage in JBoss Messaging

by Jesse Williams (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2575?page=comments#action_12408769 ] Jesse Williams commented on JBAS-2575: -------------------------------------- Was this issue recreated in messaging? I could not find it int he messaging category. It appears that tim Fox reported JBMESSAGING-1172 http://jira.jboss.org/jira/browse/JBMESSAGING-1172. Is this the same issue or has it been resolved already? > Hibernate usage in JBoss Messaging > ---------------------------------- > > Key: JBAS-2575 > URL: http://jira.jboss.com/jira/browse/JBAS-2575 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > > Currently, JBoss Messaging is going down the path of pluggable "persistence managers" attempted by JBossMQ in order to achieve database portability. As discussed numerous times, we should introduce Hibernate here to achieve this portability rather than maintaining all this stuff for the various databases. Plus would give Messaging a much easier way to introduce some of the other benefits/features of using Hibernate (caching, etc). -- 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-197) ResultType from the ResponseContext

by Anil Saldhana (JIRA)

ResultType from the ResponseContext ----------------------------------- Key: SECURITY-197 URL: http://jira.jboss.com/jira/browse/SECURITY-197 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: 2.0.2-BETA6 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA It should be possible to get to the result (and from where we can get hold of the status and obligations). -- 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1275) Enable PER_INSTANCE and PER_JOINPOINT interceptors for the EJB instances

by Kabir Khan (JIRA)

Enable PER_INSTANCE and PER_JOINPOINT interceptors for the EJB instances ------------------------------------------------------------------------ Key: EJBTHREE-1275 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1275 Project: EJB 3.0 Issue Type: Feature Request Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: AS 5.0.0.CR1 Since the bean instances are not woven, they have no instance advisor. Hence we need some other mechanism to associate the instances with an InstanceAdvisorDelegate, and set in the ManagedObjectAdvisor -- 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

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5307) Upgrade apache xerces to 2.9.1 (from 2.9.0)

by Dimitris Andreadis (JIRA)

Upgrade apache xerces to 2.9.1 (from 2.9.0) ------------------------------------------- Key: JBAS-5307 URL: http://jira.jboss.com/jira/browse/JBAS-5307 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XML services Reporter: Dimitris Andreadis Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.CR1 JBossXB likes the latest xerces 2.9.1. -- 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

18 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1316) recycleQueue.put() could block forever halting evictions and eventually any replications

by Galder Zamarreno (JIRA)

recycleQueue.put() could block forever halting evictions and eventually any replications ---------------------------------------------------------------------------------------- Key: JBCACHE-1316 URL: http://jira.jboss.com/jira/browse/JBCACHE-1316 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.1.0.GA, 1.4.1.SP8, 2.0.0.GA, 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno In BaseEvictionAlgorithm, whenever we can't evict a node, we add it to the recycle queue: protected void evict(NodeEntry ne) { // NodeEntry ne = evictionQueue.getNodeEntry(fqn); if (ne != null) { evictionQueue.removeNodeEntry(ne); if (!this.evictCacheNode(ne.getFqn())) { try { recycleQueue.put(ne.getFqn()); } catch (InterruptedException e) { log.debug("InterruptedException", e); } } } } For that to happen, an Exception must have been thrown in: protected boolean evictCacheNode(Fqn fqn) { if (log.isTraceEnabled()) { log.trace("Attempting to evict cache node with fqn of " + fqn); } EvictionPolicy policy = region.getEvictionPolicy(); // Do an eviction of this node try { policy.evict(fqn); } catch (Exception e) { if (e instanceof TimeoutException) { log.warn("eviction of " + fqn + " timed out. Will retry later."); return false; } e.printStackTrace(); return false; } if (log.isTraceEnabled()) { log.trace("Eviction of cache node with fqn of " + fqn + " successful"); } return true; } In a production environment, specially if the user ignores warnings or Exceptions, we could end up blocking indefinitely in recycleQueue.put(ne.getFqn()); if there's no more room. If this deadlocks, evictions deadlock leading to either OOME or replication exceptions because no more events can be put in the eviction queue. Rather than calling put() on the EDU.oswego.cs.dl.util.concurrent.BoundedBuffer, we should call offer(Object x, long msecs) so that we never run the chance of blocking forever here again. Same thing happens for 2.x, it uses LinkedBlockingQueue and calls put() on it, which waits if necessary for space to become available. Now, the chances of this issue occurring in 2.x are lower because LinkedBlockingQueue is initialised with a capacity of 500000. In 1.4.x, the BoundedBuffer was initialised with the default capacity, which was 1024. -- 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

18 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-5431) PooledInvokerProxy is not using the TPC factory setup by the UserTransaction client

by Adrian Brock (JIRA)

PooledInvokerProxy is not using the TPC factory setup by the UserTransaction client ----------------------------------------------------------------------------------- Key: JBAS-5431 URL: http://jira.jboss.com/jira/browse/JBAS-5431 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA The PooledInvokerProxy is expecting the TPC factory to be injected onto the client side class. It should be using the shared object for all protocols setup by the UserTransaction client side. -- 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

18 years, 3 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008