March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1946) Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings

by Joel Konieczny (JIRA)

Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings ---------------------------------------------------------------------------------- Key: EJBTHREE-1946 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1946 Project: EJB 3.0 Issue Type: Bug Components: proxy-clustered Affects Versions: 1.1.5 Environment: AS 5.1.0 GA Reporter: Joel Konieczny Combination of a clustered annotation and a HTTP(S) based remote proxy on a stateless session bean causes the bean to leave the HTTP(S) remote proxy binding still deployed after an undeploy operation, breaking re-deploys of the bean. For example: <session> <ejb-name>TestBean</ejb-name> <remote-binding> <jndi-name>TestBean/remote</jndi-name> </remote-binding> <remote-binding> <jndi-name>TestBean/remotehttp</jndi-name> <client-bind-url> http://${public.firewall.address}/servlet-invoker/ServerInvokerServlet </client-bind-url> </remote-binding> <clustered>true</clustered> </session> -- 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

14 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBREM-1187) Release 2.2.3.SP2

by Ron Sigal (JIRA)

Release 2.2.3.SP2 ----------------- Key: JBREM-1187 URL: https://jira.jboss.org/jira/browse/JBREM-1187 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2 -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1082) MessageDispatcher.ProtocolAdapter: check whether channel is closed in down()

by Bela Ban (JIRA)

MessageDispatcher.ProtocolAdapter: check whether channel is closed in down() ---------------------------------------------------------------------------- Key: JGRP-1082 URL: https://jira.jboss.org/jira/browse/JGRP-1082 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 We removed this check in 2.8.0.CR4 because it caused issues with ispan. We need to revisit when tackling 2.9 -- 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

14 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-540) Review notes from testsuite refactoring

by Paul Gier (JIRA)

Review notes from testsuite refactoring --------------------------------------- Key: JBBUILD-540 URL: https://jira.jboss.org/jira/browse/JBBUILD-540 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build - App Server (Phase 3) Attachments: dependency_notes.txt I kept some notes related to dependencies while refactoring the testsuite build. There are some dependencies that might be removed or improved in some way. -- 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

14 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JGRP-278) Externalization of socket creation in TCP/TCP_NIO (BasicTCP)

by Bela Ban (JIRA)

Externalization of socket creation in TCP/TCP_NIO (BasicTCP) ------------------------------------------------------------ Key: JGRP-278 URL: http://jira.jboss.com/jira/browse/JGRP-278 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 User configures a socket factory which creates client and server sockets. There is always 1 default factory configured. This allows developers to override socket creation, e.g. for use with SSL sockets. This way, TCP and TCP_NIO can be used with SSL. -- 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

14 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (JBMETA-250) Remove support for EJB3 @RemoteBinding.factory

by Andrew Lee Rubinger (JIRA)

Remove support for EJB3 @RemoteBinding.factory ---------------------------------------------- Key: JBMETA-250 URL: https://jira.jboss.org/jira/browse/JBMETA-250 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger EJBTHREE-1640 will be closed as unsupported, so stop exposing this information to users. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-1027) Race conditions can have NAKACK try to send to hosts don't have a receiver window yet

by Gray Watson (JIRA)

Race conditions can have NAKACK try to send to hosts don't have a receiver window yet -------------------------------------------------------------------------------------- Key: JGRP-1027 URL: https://jira.jboss.org/jira/browse/JGRP-1027 Project: JGroups Issue Type: Bug Affects Versions: 2.6.12 Reporter: Gray Watson Assignee: Bela Ban Priority: Minor We have seen NPEs in NAKACK trying to send to hosts who do not have a registered receiver window. I'd like to apply the attached patch which does a better job of creating a receiver window on the fly in these circumstances. One issue what the sequence number should be initialize to -- the patch uses 0 which has worked for us. Thanks, -- 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

14 years, 8 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMETA-263) Add support for processing concurrency management annotation and its xml equivalent

by jaikiran pai (JIRA)

Add support for processing concurrency management annotation and its xml equivalent ----------------------------------------------------------------------------------- Key: JBMETA-263 URL: https://jira.jboss.org/jira/browse/JBMETA-263 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Reporter: jaikiran pai Assignee: jaikiran pai Add support for processing @ConcurrencyManagement and its xml equivalent -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-224) Genericize ReplicantsManagerInterceptor

by Brian Stansberry (JIRA)

Genericize ReplicantsManagerInterceptor --------------------------------------- Key: JBCLUSTER-224 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-224 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Server-API 2.0.0.Beta1 Changes the constructor, so can only be done in a major release. -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7216) upgrade to the latest 2.x.x metadata

by Alexey Loubyansky (JIRA)

upgrade to the latest 2.x.x metadata ------------------------------------ Key: JBAS-7216 URL: https://jira.jboss.org/jira/browse/JBAS-7216 Project: JBoss Application Server Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossAS-6.0.0.Alpha1 In 2.x.x metadata got split into subprojects http://www.jboss.org/community/wiki/JBossMetaData. -- 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

14 years, 8 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010