May 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6864) Break up ClassloaderLeakUnitTestCase

by Brian Stansberry (JIRA)

Break up ClassloaderLeakUnitTestCase ------------------------------------ Key: JBAS-6864 URL: https://jira.jboss.org/jira/browse/JBAS-6864 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.1.0.GA Create separate tests classes for each method. Reduce/eliminate the problem of JUnit timing out the test when there are failures, thus losing visibility into which methods failed. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Updated: (JGRP-105) GossipRouter: additionally listen on IP multicast group and bridge traffic

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-105?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic updated JGRP-105: ------------------------------------- Fix Version/s: 3.x (was: 2.8) Moved to 3.X after consultation with Bela > GossipRouter: additionally listen on IP multicast group and bridge traffic > --------------------------------------------------------------------------- > > Key: JGRP-105 > URL: https://jira.jboss.org/jira/browse/JGRP-105 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8 > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Fix For: 3.x > > > GossipRouter should be augmented to not just route traffic between TCP endpoints, but also between an IP multicast group and all TCP endpoints. > It should be configured with the properties for a (multicast-based) group X, and then forward messages from X to all of its attached endpoints, and vice versa. > In the future, this concept could be extended to generic bridging functionality, which will allow to construct hierarchical messaging trees, similar to the MBone -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-972) NAKACK: merge setDigest() and mergeDigest() into one method

by Bela Ban (JIRA)

NAKACK: merge setDigest() and mergeDigest() into one method ----------------------------------------------------------- Key: JGRP-972 URL: https://jira.jboss.org/jira/browse/JGRP-972 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Semantics: - If no entry is available in xmit_table: create an entry based on the seqno shipped with the digest - Else: - If not merging: skip (leave existing entry in there, entries of left members will be removed later on the view change) - Else (merging): - Skip my own entry - For all NakReceiverWindows: - If the seqno for sender S in the win is < the seqno from the digest: reset win and create a new win and add to xmit-table - Else: no-op -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6855) [WARN ] : [TxConnectionManager] : Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure.

by Dipen Bhatt (JIRA)

[WARN ] : [TxConnectionManager] : Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-6855 URL: https://jira.jboss.org/jira/browse/JBAS-6855 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-3.2.6 Final Environment: Windows XP,2.8MGhz,C2D Reporter: Dipen Bhatt Priority: Critical [WARN ] : [TxConnectionManager] : Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure. this woning message is coming.And data get rollback. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1135) Interceptor's tutorial page contains outdated XML

by Galder Zamarreno (JIRA)

Interceptor's tutorial page contains outdated XML ------------------------------------------------- Key: EJBTHREE-1135 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1135 Project: EJB 3.0 Issue Type: Bug Components: Documentation Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno ejb3/docs/tutorial/interceptor/interceptor.html contains outdated XML, i.e: <interceptor-binding> <ejb-name>org.jboss.tutorial.interceptor.bean.EmailSystemBean</ejb-name> <interceptor-class>org.jboss.tutorial.interceptor.bean.AccountsCancelInterceptor</interceptor-class> <method-name>sendBookingCancellationMessage</method-name> </interceptor-binding> should be: <interceptor-binding> <ejb-name>org.jboss.tutorial.interceptor.bean.EmailSystemBean</ejb-name> <interceptor-class>org.jboss.tutorial.interceptor.bean.AccountsCancelInterceptor</interceptor-class> <method> <method-name>sendBookingCancellationMessage</method-name> </method> </interceptor-binding> i.e.2: <interceptor-binding> <ejb-name>MyBean</ejb-name> <interceptor-class>SomeInterceptor</interceptor-class> <method-name>overLoadedMethod</method-name> <method-params> <method-param>int</method-param> <method-param>java.lang.String[][]</method-param> </method-params> </interceptor-binding> should be: <interceptor-binding> <ejb-name>MyBean</ejb-name> <interceptor-class>SomeInterceptor</interceptor-class> <method> <method-name>overLoadedMethod</method-name> <method-params> <method-param>int</method-param> <method-param>java.lang.String[][]</method-param> </method-params> </method> </interceptor-binding> -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1335) Populate container name in ejb3 meta data

by Heiko Braun (JIRA)

Populate container name in ejb3 meta data ----------------------------------------- Key: EJBTHREE-1335 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1335 Project: EJB 3.0 Issue Type: Feature Request Reporter: Heiko Braun Assigned To: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.CR1 -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-6221) Default JmsActivationSpec ignore configuration in standardjboss.xml

by mark.lowe (JIRA)

Default JmsActivationSpec ignore configuration in standardjboss.xml ------------------------------------------------------------------- Key: JBAS-6221 URL: https://jira.jboss.org/jira/browse/JBAS-6221 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, EJB3, JMS (JBoss Messaging), JMS (JBossMQ) Affects Versions: JBossAS-4.2.3.GA, JBossAS-4.2.2.GA Reporter: mark.lowe Assignee: Ales Justin Configuring an external MQ provider as DefaultJMSProvider works until there's an error and hence the genericdql handler is called into action. The GenericDQLHandler is broken is doesn't increment the JMSXDeliveryCount header, so being able to change the DLQHander implementation would be handy.. However, changing the values in standardjboss.xml has no effect. So you're forced into defining the DLQHander property in the ejb-jar.xml or worse still annotations for MDBs. This also creates problems when attempting to change the confguration of any invokers used in these cases.. Mapping the invokers /containers in jboss.xml also has no effect.. The defaukt values of JmsActivationSpec is all you have.. -- 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, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-6118) EJB3 InvokerLocator server socket binds only to 127.0.0.1 when the hostname is listed in /etc/host as 127.0.0.1

by Alejandro Isacovich (JIRA)

EJB3 InvokerLocator server socket binds only to 127.0.0.1 when the hostname is listed in /etc/host as 127.0.0.1 --------------------------------------------------------------------------------------------------------------- Key: JBAS-6118 URL: https://jira.jboss.org/jira/browse/JBAS-6118 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Environment: RedHat Linux 2.6.9-42.ELsmp Kernel Reporter: Alejandro Isacovich Assignee: Carlo de Wolf If the host name is listed in an entry of the /etc/hosts file as 127.0.0.1. For example as follows (where vm9-srv01 is the hostname): 127.0.0.1 localhost.localdomain localhost vm9-srv01 Then the EJB3 InvokerLocator server socket binds only to 127.0.0.0 regardless of what the jboss.bind.address is. That means clients from other machines will not be able to make EJB3 calls to the server. This issue was also discussed here for JBoss 4.2.1.GA: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098486#4098486 -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-757) getMessageContext Not Implemented

by ppc (JIRA)

getMessageContext Not Implemented --------------------------------- Key: EJBTHREE-757 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: ppc jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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, 2 months

4
17
0 / 0

[JBoss JIRA] Created: (EJBTHREE-989) Can't inject resources of type URL

by Carlo de Wolf (JIRA)

Can't inject resources of type URL ---------------------------------- Key: EJBTHREE-989 URL: http://jira.jboss.com/jira/browse/EJBTHREE-989 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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, 2 months

2
5
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 2009