September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBEE-10) JavaEE 6.0 Alpha1 Release

by Shelly McGowan (JIRA)

JavaEE 6.0 Alpha1 Release ------------------------- Key: JBEE-10 URL: https://jira.jboss.org/jira/browse/JBEE-10 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 Release of EE 6 APIs needed for JCA project. -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-977) Handle IPv6 link-local addresses correctly when used as bind addresses or multicast addresses

by Richard Achmatowicz (JIRA)

Handle IPv6 link-local addresses correctly when used as bind addresses or multicast addresses --------------------------------------------------------------------------------------------- Key: JGRP-977 URL: https://jira.jboss.org/jira/browse/JGRP-977 Project: JGroups Issue Type: Feature Request Affects Versions: 2.6.10, 2.4.6, 2.8 Environment: IPv6 addresses being used Reporter: Richard Achmatowicz Assignee: Bela Ban IPv6 has two types of IP addresses: global addresses and non-global addresses. Global addresses are unique across the internet (via judicious allocation of network prefixes by authorities). They make up the range 2000::/3 (2000:: to 3fff:ffff:ffff:ffff:ffff:ffff:ffff:ffff). Global addresses generally require no special treatment. Non-global addresses, like link-local (fe80::/10) and site-local addresses (fec0::/10) are not guaranteed to be unique - in the extreme case, two interfaces on the same host can have the same link-local address. This means that they cannot be used on their own when binding to a socket, but must have extra information (a zone id or sometimes called scope) added to them to disambiguate them. The zone id is basically the interface you want the message to go out on. A scoped link-local address is one which has a scope appended to it. The way to notate this is to append the scope to the link-local address after a % sign: <link-local IP address>%<zone id> where the zone Id can be numerical or simply the next name of the interface. For example, fe80::215:58ff:fec8:81a8%eth0. A JGroups user may make use of link-local addresses when binding. In that case, we need to make sure that the scope is present, and if not, take some action. Otherwise, when binding to a socket with an unscoped link-local address, a SocketException will be raised. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-906) Marshalling: requirement to use magic numbers

by Bela Ban (JIRA)

Marshalling: requirement to use magic numbers --------------------------------------------- Key: JGRP-906 URL: https://jira.jboss.org/jira/browse/JGRP-906 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Sometimes (e.g. Util.writeOtherAddress()), we use the classname if a magic number is not available, to marshall a type. We should change to always using magic numbers. If a magic number is not registered, we should throw an exception. This should at least be done for JGroups defined types -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1480) Specify Lock datarow on Sybase create tables

by Clebert Suconic (JIRA)

Specify Lock datarow on Sybase create tables -------------------------------------------- Key: JBMESSAGING-1480 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1480 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.0.SP3.CP04 Reporter: Clebert Suconic Assignee: Howard Gao Priority: Minor Fix For: 1.4.0.SP3.CP05, 1.4.3.GA Some users were complaining about dead locks on sybase with JBossMessaging. That trully is a config issue on sybase, but to avoid that maybe we should specify the lock schema at create table level, as shown on this doc. http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20021_125... -- 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, 5 months

2
18
0 / 0

[JBoss JIRA] Created: (JGRP-932) Replace header names and protocol names with IDs

by Bela Ban (JIRA)

Replace header names and protocol names with IDs ------------------------------------------------ Key: JGRP-932 URL: https://jira.jboss.org/jira/browse/JGRP-932 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader. This will solve https://jira.jboss.org/jira/browse/JGRP-872. -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2321) Upgrade to WSRP 2.0

by Fernando Ribeiro (JIRA)

Upgrade to WSRP 2.0 ------------------- Key: JBPORTAL-2321 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2321 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.1 Final Reporter: Fernando Ribeiro Assignee: Chris Laprun The recent increase in the adoption of portal servers can drive more interest in WSRP in the next couple of years. WSRP 2.0 was published more than 1 year ago and hasn't been widely implemented yet. This may be targeted at 3.0 or beyond. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1819) WSDL status should be persisted in the database for better handling

by Chris Laprun (JIRA)

WSDL status should be persisted in the database for better handling ------------------------------------------------------------------- Key: JBPORTAL-1819 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1819 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.3 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.8 Final -- 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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2120) Migrate WSRP implementation to JAX-WS

by Chris Laprun (JIRA)

Migrate WSRP implementation to JAX-WS ------------------------------------- Key: JBPORTAL-2120 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2120 Project: JBoss Portal Issue Type: Task 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.8 Final Moving forward, JAX-RPC is a deprecated technology... -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1461) Number of relivery attempts does not match with my settings

by Nicolas Laporte (JIRA)

Number of relivery attempts does not match with my settings ----------------------------------------------------------- Key: JBMESSAGING-1461 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1461 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.SP4 Environment: JBoss 4.0.4.GA Windows server 2003 Reporter: Nicolas Laporte Assignee: Tim Fox Priority: Minor I set <attribute name="MaxDeliveryAttempts">15</attribute> The time-to-live parameter used by the client is 1 hour. We call the setRollbackOnly() method of our CMT MDB if an recoverable exception occurrs. The number of redelivery is 5. I expected 15. Could you tell me if this problem is known and if it is fixed in an upper version ? Thanks a lot for your support. Nicolas Laporte PDF Solutions -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-6820) MDBs are hard-coded to use jms-ra.rar

by Clebert Suconic (JIRA)

MDBs are hard-coded to use jms-ra.rar ------------------------------------- Key: JBAS-6820 URL: https://jira.jboss.org/jira/browse/JBAS-6820 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3, JCA service Affects Versions: JBossAS-5.1.0.Beta1 Reporter: Clebert Suconic Assignee: Carlo de Wolf Priority: Critical We may have to deploy several resource-adapters for JBossMessaging. (Say.. remote servers, backup-servers and other configurations). It seems that the JNDI for Inbound is simply ignored at some level. Instead of getting the spec Inbound from the JCA configured factory, EJB3 is hard-coding the dependency to the resource adapter and this is not acceptable for JBoss Messaging. -- 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, 5 months

4
8
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 September 2009