May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-121) Check recovery

by Mark Little (JIRA)

Check recovery -------------- Key: JBTM-121 URL: http://jira.jboss.com/jira/browse/JBTM-121 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-804) Provide a clean jboss-messaging-client.jar without containing external dependencies

by Galder Zamarreno (JIRA)

Provide a clean jboss-messaging-client.jar without containing external dependencies ----------------------------------------------------------------------------------- Key: JBMESSAGING-804 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-804 Project: JBoss Messaging Issue Type: Feature Request Components: Build System Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Galder Zamarreno Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2, 1.0.1.SP4 We've installed JBoss messaging instead of JBossMQ and updated our application to connect to this. We have to include jboss-messaging-client.jar to be able to use it, but now the following problem arises: jboss-messaging-client.jar has log4j classes in it, which are of an old version. Therefore, our .war cannot deploy because it uses methods of log4j of the newer version (e.g. Logger.isTraceEnabled()). To your approach of patching jboss-messaging-client.jar: maybe we'll try it, but I'm afraid it includes more classes that may clash with our system... What we need is a clean jboss-messaging-client.jar file, without external dependencies, but I don't want to build it myself as it makes maintaining our JBoss setup very hard. -- 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, 2 months

6
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-957) Provide a configuration(installation) that will work in the All configuration.

by Jay Howell (JIRA)

Provide a configuration(installation) that will work in the All configuration. ------------------------------------------------------------------------------ Key: JBMESSAGING-957 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-957 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: 1.2.0.SP2 Reporter: Jay Howell Assigned To: Tim Fox When using the installation process for messaging, you install and it creates a new container based on the Default container. We need to also be able to have one for the All container also. Many customers want to run Messaging in clustered mode as well as everything else. The all configuration is the current way to do this. Note: Here's some background and some problems you may run into with the install of messaging 1.2.0 sp2 on 4.0.5 using an all configuration. Had an instance yesterday, where the customer moved thier clusterd post office configuration to all. This works as long as messaging is deployed in a scoped classloader. I know that sp2 will copy the remoting and aop libs into the main lib directory for the container in order to avoid the scoped classloader. So I had the customer do what sp 2 will do, copy over the old remoting and aop jars. Becasue messaging is using an updated version of jgroups also, and jgroups is in the lib directory of the container, it picks that one up first before the one in messaging. We copied over the jgroups jar just as we did for remoting and aop. I found that the container comes up with no problem, but I can no longer get to jconsole and things don't work correctly(no errors, but it won't work either). I don't know what the problem is, but running the all configuration with the clustered post office without a scoped classloader seems to have problems. Jay:) -- 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, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (SECURITY-52) Release Security 2.0.0.GA

by Anil Saldhana (JIRA)

Release Security 2.0.0.GA ------------------------- Key: SECURITY-52 URL: http://jira.jboss.com/jira/browse/SECURITY-52 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JBossSX, Security SPI Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.GA Security is almost ready for 2.0.0.GA Some documentation needs to be provided. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-53) Security SPI Integration Document

by Anil Saldhana (JIRA)

Security SPI Integration Document --------------------------------- Key: SECURITY-53 URL: http://jira.jboss.com/jira/browse/SECURITY-53 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JBossSX, Security SPI Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Blocker Fix For: 2.0.GA Need the Security SPI documentation before the 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-725) Add a release-admin check that would cleanly stop the installation process if ant version is too old

by Ovidiu Feodorov (JIRA)

Add a release-admin check that would cleanly stop the installation process if ant version is too old ---------------------------------------------------------------------------------------------------- Key: JBMESSAGING-725 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-725 Project: JBoss Messaging Issue Type: Feature Request Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 ... and avoid cryptic failures like this one: [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -f release-admin.xml Buildfile: release-admin.xml default: BUILD FAILED C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:36: The following error occurred while ex ecuting this line: C:\temp\jboss-messaging-1.2.0.Beta1\util\release-admin.xml:519: Class org.apache.tools.ant.taskdefs. ConditionTask doesn't support the nested "length" element. Total time: 1 second [C:/temp/jboss-messaging-1.2.0.Beta1/util] ant -version Apache Ant version 1.6.2 compiled on July 16 2004 -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-508) Finalize wire format for messages (optimization)

by Bela Ban (JIRA)

Finalize wire format for messages (optimization) ------------------------------------------------ Key: JGRP-508 URL: http://jira.jboss.com/jira/browse/JGRP-508 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Look at wire format (defined in JGroups/doc/design/MarshallingFormat.txt) and (a) make it more compact and (b) finalize it - IpAddress: write port as a short (gives us 65K ports) -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1062) CacheImpl.remoteAnnounceBuddyPoolName should take Address not IpAddress

by Brian Stansberry (JIRA)

CacheImpl.remoteAnnounceBuddyPoolName should take Address not IpAddress ----------------------------------------------------------------------- Key: JBCACHE-1062 URL: http://jira.jboss.com/jira/browse/JBCACHE-1062 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.CR2 The method signature specifies IpAddress, not Address, but the impl doesn't use anything from IpAddress. Method should just take Address. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-925) Remove requirement to deploy JBM scoped in JB AS <= 4.2

by Tim Fox (JIRA)

Remove requirement to deploy JBM scoped in JB AS <= 4.2 ------------------------------------------------------- Key: JBMESSAGING-925 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-925 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.GA Reporter: Tim Fox Priority: Critical Fix For: 1.2.0.SP1 Currently JBM needs to be deployed as a scoped deployment in every all the GA releases of JBoss AS. This causes considerable configuration headaches for users and more than likely acts as a major barrier to adoption of JBM. We currently scope because we use more recent versions of JBoss Remoting and JBoss AOP than the versions deployed in JBAS. It appears that, other than JBM, only EJB3 and parts of JBoss WS actually use AOP and remoting so instead of deploying scoped we should first verify whether WS and EJB3 work with the later versions of AOP and remoting, and if not we should patch AOP and remoting to get them to work. Then we can overwrite the versions of remoting and aop in server/lib in the AS during the JBM install procedure and deploy unscoped - this would be a huge win for the project. -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-961) WebServices SmokeTest

by Clebert Suconic (JIRA)

WebServices SmokeTest --------------------- Key: JBMESSAGING-961 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-961 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2 I should write a smoke test for a webService. -- 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, 2 months

2
6
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 May 2007