August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBXB-149) Inconsistent jaxb api dependency

by Scott M Stark (JIRA)

Inconsistent jaxb api dependency -------------------------------- Key: JBXB-149 URL: https://jira.jboss.org/jira/browse/JBXB-149 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR11 Reporter: Scott M Stark Fix For: JBossXB-2.0.0.CR13 The jbossxb jaxb api dependency is: <dependency> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <version>2.1</version> <scope>compile</scope> </dependency> but it needs to be updated to be consistent with what we are validating in jbossas as part of the tck: <dependency> <groupId>sun-jaxb</groupId> <artifactId>jaxb-api</artifactId> <version>2.1.4</version> </dependency> -- 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

17 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-991) Investigate MulticastDetector message flood

by Ron Sigal (JIRA)

Investigate MulticastDetector message flood ------------------------------------------- Key: JBREM-991 URL: http://jira.jboss.com/jira/browse/JBREM-991 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.2.SP8 A use has reported that org.jboss.remoting.detection.multicast.MulticastDetector is flooding the network with messages. The problem might lie MulticastDetector.listen(): else { // for now, assume anything *not* of type Detection // is a prompt to send out detection msg heartbeat(); } -- 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

17 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-999) Make sure all fixes on 2.2 branch are ported to 2.x branch.

by Ron Sigal (JIRA)

Make sure all fixes on 2.2 branch are ported to 2.x branch. ----------------------------------------------------------- Key: JBREM-999 URL: http://jira.jboss.com/jira/browse/JBREM-999 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.SP1 -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-925) SSLSocketBuilder config attribute names out of sync with v2.2 docs

by Tom Fennelly (JIRA)

SSLSocketBuilder config attribute names out of sync with v2.2 docs ------------------------------------------------------------------ Key: JBREM-925 URL: http://jira.jboss.com/jira/browse/JBREM-925 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: docs Reporter: Tom Fennelly The latest docs available for download are for 2.2.0.GA (http://labs.jboss.org/jbossremoting/docs/index.html). Table 5.1 (in pdf) outlines the attribute names for configuring the SSLSocketBuilder. They're not consistent with the actual definitions in the SSLSocketBuilder class, so errors result when used as per the docs. In the ESB, we do a manual mapping of the names in code, so we get around the issue, but other users may be stumped. -- 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

17 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBREM-1022) Fix misleading javadoc in InvokerLocator

by Ron Sigal (JIRA)

Fix misleading javadoc in InvokerLocator ---------------------------------------- Key: JBREM-1022 URL: https://jira.jboss.org/jira/browse/JBREM-1022 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP9, 2.4.0.GA (Pinto) Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.4.0.SP1, 2.2.2.SP10 The following note in the org.jboss.remoting.InvokerLocator javadoc is incorrect: * NOTE: the hostname will automatically be resolved to the outside IP address of the local machine * if <tt>localhost</tt> or <tt>127.0.0.1</tt> is used as the hostname in the URI. If it cannot be * determined or resolved, it will use what was passed. In fact, it is only a missing hostname (and 0.0.0.0 in the special case that the system property "jboss.bind.address" is set) that will be replaced. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-991) Non-JTA based mechanism for batching invocations

by Brian Stansberry (JIRA)

Non-JTA based mechanism for batching invocations ------------------------------------------------ Key: JBCACHE-991 URL: http://jira.jboss.com/jira/browse/JBCACHE-991 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Currently JBC uses the lifecycle of a JTA Transaction to scope a series of cache invocations doing things like lock release, replication and cache loader storage as part of the transaction commit. Need a mechanism to do this kind of invocation batching that doesn't depend on JTA. Needed to allow callers that don't wish their work to be associated with an active JTA transaction to still get the batching behavior JBC provides. AS web session replication is an example use case. It uses BatchModeTransactionManger to ensure its activity doesn't impact any ongoing transaction. But BatchModeTransactionManager isn't a good JTA transaction manager even though it implements the JTA interfaces. So using it is problematic; it can easily be misused by those who don't understand it's limitations (e.g. hooking it up to a JTA Datasource.) A couple of possible approaches have been discussed: 1) A new API added to Cache. Methods like startBatch(), commitBatch(), rollbackBatch(), along with some internal mechanism to timeout a batch that's been started but never committed/rolled-back. 2) Abstract away the JTA API such that JBC doesn't use JTA directly, but rather its own interfaces that largely parallel TransactionManager and Transaction. Provide an impl that simply wraps a real JTA TransactionManager. BatchModeTransactionManger would be another impl. API includes a method like 'boolean isJTACompliant()' that things like CacheLoader impls can check at startup to confirm they are working with a compatible impl (e.g. if JBDCCacheLoader is configured to use a JTA Datasource but isJTACompliant() returns false, throw an exception at startup.) Apologies if this is a duplicate issue. Thought there was something like this but couldn't find it. -- 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

17 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1408) Investigate failure on dev47 / libaio

by Clebert Suconic (JIRA)

Investigate failure on dev47 / libaio ------------------------------------- Key: JBMESSAGING-1408 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1408 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assignee: Clebert Suconic Priority: Critical Fix For: 2.0.0 Beta The integration testsuite is currently failing at hudson(a)dev47.qa.atl.jboss.com for no apparent reason. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2115) JBP_REGISTRATION_INFO sql error name key

by Chris Laprun (JIRA)

JBP_REGISTRATION_INFO sql error name key ---------------------------------------- Key: JBPORTAL-2115 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2115 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Beta1, 2.6.6 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.0 CR1 , 2.6.7 Final -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2114) Requesting an invalid mode results in unexpected behavior

by Chris Laprun (JIRA)

Requesting an invalid mode results in unexpected behavior --------------------------------------------------------- Key: JBPORTAL-2114 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2114 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Beta1, 2.6.6 Final Reporter: Chris Laprun Assignee: Chris Laprun Priority: Critical Fix For: 2.7.0 CR1 , 2.6.7 Final -- 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

17 years, 11 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-2101) identity admin ui testing

by Prabhat Jha (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2101?page=com.atlassian.jira.... ] Prabhat Jha commented on JBPORTAL-2101: --------------------------------------- By default, new user should be under "Users". Please also make sure that you have id of all all html elements. If some elements have missing ID, then I will work on adding id to missing elements. Regarding strength, the more you assert the better it is as long as it's not redundant. > identity admin ui testing > ------------------------- > > Key: JBPORTAL-2101 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2101 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Viliam Rockai > -- 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

17 years, 11 months

1
0
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 August 2008