March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-258) Release jboss-metadata-common 2.0.0.Alpha12

by John Bailey (JIRA)

Release jboss-metadata-common 2.0.0.Alpha12 ------------------------------------------- Key: JBMETA-258 URL: https://jira.jboss.org/jira/browse/JBMETA-258 Project: JBoss Metadata Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: jboss-metadata-common 2.0.0-alpha-11 Reporter: John Bailey Assignee: John Bailey Fix For: jboss-metadata-ejb-2.0.0-alpha-7 A new alpha version is needed for VFS3 integration in JBossAS. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMETA-262) Ban org.jboss.javaee:jboss-ejb-api_3.1 dependency and use the new org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec

by jaikiran pai (JIRA)

Ban org.jboss.javaee:jboss-ejb-api_3.1 dependency and use the new org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ----------------------------------------------------------------------------------------------------------------- Key: JBMETA-262 URL: https://jira.jboss.org/jira/browse/JBMETA-262 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Affects Versions: jboss-metadata-ejb-2.0.0-alpha-6 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: jboss-metadata-ejb-2.0.0-alpha-7 After the changes in JBEE-15 the EJB3.1 related spec artifact now resides at org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec. Ban any dependencies on the earlier org.jboss.javaee:jboss-ejb-api_3.1 and instead use this new one. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-215) Allow for configuration of transaction-retry

by Carlo de Wolf (JIRA)

Allow for configuration of transaction-retry -------------------------------------------- Key: JBMETA-215 URL: https://jira.jboss.org/jira/browse/JBMETA-215 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.2.Beta2, 2.0.0.CR1 The @TransactionRetry annotation must have an equivalent configuration option in descriptors. @TransactionRetry(numRetries=4, waitTime=1, waitTimeUnit=TimeUnit.SECONDS) <assembly-descriptor> <transaction-retry>  <method> <ejb-name>*</ejb-name> <method-name>...</method-name> </method> ... <num-retries>4</num-retries> <wait-time>1</wait-time> <wait-time-unit>SECONDS</wait-time-unit> </transaction-retry> </assembly-descriptor> -- 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

16 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-1164) TCPGOSSIP doesn't maintain the Gossip Router state correctly

by vivek v (JIRA)

TCPGOSSIP doesn't maintain the Gossip Router state correctly ------------------------------------------------------------ Key: JGRP-1164 URL: https://jira.jboss.org/jira/browse/JGRP-1164 Project: JGroups Issue Type: Bug Affects Versions: 2.9, 2.8 Reporter: vivek v Assignee: Bela Ban This came out of discussion /w Vladimir on jira# 1162 (https://jira.jboss.org/jira/browse/JGRP-1162). Basically, the problem is currently TCPGossip.connect(..) calls RouterStubs.connect(..). The connect at router stub simply makes the socket connection /w Gossip Router and then sends the "Connect" command without waiting for the response from GR. The socket creation creates the Connection Handler on the Gossip Router. The problem is in a very lossy network we might lose the "Connect" command and thus GR will not add the node (RouterStub node) in its list. Since, the socket connection is established (and won't disconnect due keep alive even in lossy network), the router stub would assume it is connected (would set to CONNECTED if the socket is good), but will not get itself from GR when asking for nodes in the group. Theoretically in TCP connection we shouldn't lose the packets, but in our experiments we did. I tried the test with WANem setting 50% packet loss and was able to create the situation where the socket was created, but no CONNECT. This caused Gossip Router to publish wrong node list. Two possibles fixes, 1) When we make the socket connection assume CONNECTED - so we don't have to send a separate CONNECT command. - This is not a good design as the STATE should be kept by the application layer 2) Wait for the response from Gossip Router for CONNECT (same for DISCONNECT as well) before setting TCPGOSSIP to CONNECTED state -- 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

16 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7327) Connection validation should return valid connections to the pool when an invalid connection is found

by Borja Ruiz (JIRA)

Connection validation should return valid connections to the pool when an invalid connection is found ----------------------------------------------------------------------------------------------------- Key: JBAS-7327 URL: https://jira.jboss.org/jira/browse/JBAS-7327 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.3.GA Environment: unix, hp-ux Reporter: Borja Ruiz Assignee: Jesper Pedersen There is a bug in validation code, in org.jboss.resource.connectionmanager.InternalManagedConnectionPool class validateConnections method. It is easily reproducible by the following example. You have a set of 3 connections in the pool, and when you run this validation code, the fist one is not valid and the following 2 are valid. As you do not update "destroyed" variable to "false" on every iteraion, those 2 valid connections do not return to the pool, resulting in two ESTABLISHED connections going out of pool control. Also, resource adapter counters don't get updated, resulting in an inconsistent status. In JBoss forum reference I have provided affected code and a solution developed by me as a suggestion -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JASSIST-108) Better support for OSGi

by Pete Muir (JIRA)

Better support for OSGi ----------------------- Key: JASSIST-108 URL: https://jira.jboss.org/jira/browse/JASSIST-108 Project: Javassist Issue Type: Task Reporter: Pete Muir Assignee: Shigeru Chiba This is a container task to collect various issues with OSGi support -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-148) Port http://community.jboss.org/wiki/VFS3UserGuide to DocBook

by John Bailey (JIRA)

Port http://community.jboss.org/wiki/VFS3UserGuide to DocBook ------------------------------------------------------------- Key: JBVFS-148 URL: https://jira.jboss.org/jira/browse/JBVFS-148 Project: JBoss VFS Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR4 Reporter: John Bailey Assignee: John Bailey -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBVFS-113) Comprehensive VFS documentation

by Flavia Rainone (JIRA)

Comprehensive VFS documentation ------------------------------- Key: JBVFS-113 URL: https://jira.jboss.org/jira/browse/JBVFS-113 Project: JBoss VFS Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assignee: Flavia Rainone Provide a comprehensive documentation for the VFS project. This includes a user guide and a Javadoc (with the API/SPI). -- 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

16 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBVFS-146) Change Handling of file: URLs to delegate to the RootFileSystem Only

by John Bailey (JIRA)

Change Handling of file: URLs to delegate to the RootFileSystem Only -------------------------------------------------------------------- Key: JBVFS-146 URL: https://jira.jboss.org/jira/browse/JBVFS-146 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR3 Reporter: John Bailey Assignee: John Bailey Fix For: 3.0.0.CR4 Change the behavior of the file: handler to delegate to the RootFileSystem only. Should not use normal VFS mounted FileSystems. -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBVFS-145) Introduce Support for vfs: URL Protocol

by John Bailey (JIRA)

Introduce Support for vfs: URL Protocol ---------------------------------------- Key: JBVFS-145 URL: https://jira.jboss.org/jira/browse/JBVFS-145 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR3 Reporter: John Bailey Assignee: John Bailey Fix For: 3.0.0.CR4 There are a number of 3rd party libraries that handle file: URLs in ways that will not work with VFS. In order to avoid this, VFS should return a custom URL protocol that will ensure it is not misused as a simple file-system file. -- 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

16 years, 4 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 March 2010