February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-609) Decide the way to go forward (with or without Remoting)

by Ovidiu Feodorov (JIRA)

Decide the way to go forward (with or without Remoting) ------------------------------------------------------- Key: JBMESSAGING-609 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-609 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.0.Alpha2 Conclude the http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971228 discussion thread and make a decision on how to go further: 1. Modify Remoting to include Messaging-specific requirements (asynchronicity, AMQP, etc) 2. Implement our own remoting solution. -- 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

19 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-848) Shutting down messaging with JBoss 4.0.3SP1 standalone fails

by Ovidiu Feodorov (JIRA)

Shutting down messaging with JBoss 4.0.3SP1 standalone fails ------------------------------------------------------------ Key: JBMESSAGING-848 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-848 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical -- 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

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-832) Develop CacheSPI impl for use in JBoss JMX microkernel

by Brian Stansberry (JIRA)

Develop CacheSPI impl for use in JBoss JMX microkernel ------------------------------------------------------ Key: JBCACHE-832 URL: http://jira.jboss.com/jira/browse/JBCACHE-832 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA If we want JBC 2.0 to work in AS 4.2, we'll need a way to construct a CacheSPI via the 4.x microkernel/SARDeployer. Initial thoughts: 1) Create class "CacheSPIWrapper" that implements CacheSPI, plus exposes all the configuration-related mbean attributes from JBC 1.4. This is the class that's used for the "class" attribute of the mbean in the -service.xml file. 2) Class when instantiated also instantiates a Configuration object. When SARDeployer invokes the setters on the legacy mbean attributes, the values are passed through to the Configuration object. 3) In createService(), the Configuration object is passed to DefaultCacheFactory, which returns an instance of the standard CacheSPI impl. CacheSPIWrapper holds a ref to this object for use as a delegate. 4) CacheSPIWrapper implements CacheSPI by delegation to the standard object. If we decide we don't want to support use of JBC 2.0 in 4.2, this task can be closed. -- 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

19 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-3949) Upgrade to log4j 1.2.14

by Dimitris Andreadis (JIRA)

Upgrade to log4j 1.2.14 ----------------------- Key: JBAS-3949 URL: http://jira.jboss.com/jira/browse/JBAS-3949 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Logging Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Upgrade to the latest stable log4j release 1.2.14 http://logging.apache.org/log4j/docs/download.html -- 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-928) Consider adding a method to expose lifecycle state

by Brian Stansberry (JIRA)

Consider adding a method to expose lifecycle state -------------------------------------------------- Key: JBCACHE-928 URL: http://jira.jboss.com/jira/browse/JBCACHE-928 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.0.0.BETA1 In 1.x, in the AS at least, the lifecycle state of a cache could be determined via the inherited ServiceMBeanSupport.getState(). Now there is no way to find out if the cache is created/started/stopped/destroyed. We should consider adding this, perhaps as a method in the Cache interface. -- 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

19 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-727) @Depends annotation does not work in EJB3 Embeddable release

by Magesh Kumar B (JIRA)

@Depends annotation does not work in EJB3 Embeddable release ------------------------------------------------------------ Key: EJBTHREE-727 URL: http://jira.jboss.com/jira/browse/EJBTHREE-727 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Magesh Kumar B The ServiceOne, ServiceTwo and ServiceThree example given in the EJB3.0 documentation does not work when testing with the embeddable release -- 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

19 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3985) EJB3 hot redeployment causes a permanently locked file handle

by Vladimir Ralev (JIRA)

EJB3 hot redeployment causes a permanently locked file handle ------------------------------------------------------------- Key: JBAS-3985 URL: http://jira.jboss.com/jira/browse/JBAS-3985 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3 Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP Pro, JRE 1.5_9, JBoss AS 4.0.5.GA, EJB3.CR9.patch1 Reporter: Vladimir Ralev Assigned To: Dimitris Andreadis I am not sure which component is responsible for the bug, but since it happened with an ejb3-jar I am rising it here. If it doesn't belong here please forward it the right place. 1. I copy titan.jar to the deploy folder -> the server deploys the ejb3 application and says ejb running 2. I delete titan.jar from the deploy folder -> the server says that the app is undeployed 3. I copy titian.jar in the deploy folder again -> the server deploys the ejb3 application and says ejb running again (everything seems ok for now, here comes the problem) 4. I try to delete titan.jar from the deploy folder -> I get a windows explorer error message saying that the file is in use and can't be deleted. When I checked with process explorer which process is using the file it turned out it's the java.exe process (the server didn't release the handle?). This doesn't not occur on Linux! -- 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

19 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4055) Hot Deploy doesn't work in JBoss 5.0.0.Beta1

by Charles Crouch (JIRA)

Hot Deploy doesn't work in JBoss 5.0.0.Beta1 -------------------------------------------- Key: JBAS-4055 URL: http://jira.jboss.com/jira/browse/JBAS-4055 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Charles Crouch Fix For: JBossAS-5.0.0.Beta2 Hot Deploy doesn't work in JBoss 5.0.0.Beta1 -- 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

19 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-843) Clustered ConnectionFactory with no load balancing, but failover capabilities needed

by Ovidiu Feodorov (JIRA)

Clustered ConnectionFactory with no load balancing, but failover capabilities needed ------------------------------------------------------------------------------------ Key: JBMESSAGING-843 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-843 Project: JBoss Messaging Issue Type: Feature Request Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR2 Needed by the MDB containers. An MDB creates several connections during its deployment. If using a load-balancing clustered ConnectionFactory, they'll end up on different cluster nodes, which is precisely what the MDB container doesn't need. On the other hand, if using a "dumb" non-clustered ConnectionFactory, the MDB container doesn't benefit from the cluster failover capabilities. A clustered ConnectionFactory with no load balancing, but failover capabilities is needed. -- 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

19 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-690) improve fron-end Standards and templates

by Fernando Meyer (JIRA)

improve fron-end Standards and templates ---------------------------------------- Key: JBRULES-690 URL: http://jira.jboss.com/jira/browse/JBRULES-690 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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

19 years, 1 month

2
3
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 February 2007