November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1821) modifyRegistration does not properly check that passed data is acceptable

by Chris Laprun (JIRA)

modifyRegistration does not properly check that passed data is acceptable ------------------------------------------------------------------------- Key: JBPORTAL-1821 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1821 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5020) Incorrect system property usage in JMX console clustering service

by Brian Stansberry (JIRA)

Incorrect system property usage in JMX console clustering service ----------------------------------------------------------------- Key: JBAS-5020 URL: http://jira.jboss.com/jira/browse/JBAS-5020 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.2.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA In ./deploy/jmx-console.war/WEB-INF/web.xml: <param-value>UDP(ip_mcast=true;ip_ttl=16;loopback=false;mcast_addr=${jboss.partition.udpGroup:228.1.2.3};mcast_port=${jboss.partition.udpPort:45566}): Should not be jboss.partition.udpPort as that property should NOT be set; it will cause all channels to use the same port. Will switch it to jboss.jmxconsolepartition.mcast_port to be consistent with JBAS-4021 usage. -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5012) Trim MetaData getSecurityDomain newline characters

by Anil Saldhana (JIRA)

Trim MetaData getSecurityDomain newline characters -------------------------------------------------- Key: JBAS-5012 URL: http://jira.jboss.com/jira/browse/JBAS-5012 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2, EJB3, Web (Tomcat) service Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 Legacy jboss.xml /jboss-web.xml descriptors could have a security domain defined as: <security-domain> something </security-domain> So the read of the metadata.getSecurityDomain should take into consideration newline characters in the value. A trim is necessary. -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1110) Support configuring home-load-balance-policy

by Brian Stansberry (JIRA)

Support configuring home-load-balance-policy -------------------------------------------- Key: EJBTHREE-1110 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1110 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.Beta3 Users are allowed to configure a home interface on an @Clustered EJB3 bean. They should be able to configure the load balance policy used by that home, the same as they can for EJB2 homes. This means an added attribute for the @Clustered annotation and a change to the jboss_5_0.xsd. -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5018) Support bean declarations only in jboss.xml

by Brian Stansberry (JIRA)

Support bean declarations only in jboss.xml ------------------------------------------- Key: JBAS-5018 URL: http://jira.jboss.com/jira/browse/JBAS-5018 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, EJB3 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 JBossEnterpriseBeansMetaData.merge is not including any beans only declared in jboss.xml in the merged view. Since we have expanded the jboss.xml to essentially make the ejb-jar.xml unnecessary, we should be allowing for jboss.xml only entries. -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5017) Error opening Server Session rc=202

by Yang Yu (JIRA)

Error opening Server Session rc=202 ----------------------------------- Key: JBAS-5017 URL: http://jira.jboss.com/jira/browse/JBAS-5017 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: Windows2000, Sun JDK 1.5.0_10 b03 Reporter: Yang Yu The JBoss server is functioning very well, but there are a bunch of error messages "Error opening Server Session rc=202" showing up in the JBoss console. I'd like to know what could cause this issue and how to avoid it, thanks in advance. -- 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

18 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4802) FirstAvailable target should not be transient

by Brian Stansberry (JIRA)

FirstAvailable target should not be transient --------------------------------------------- Key: JBAS-4802 URL: http://jira.jboss.com/jira/browse/JBAS-4802 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end. This can lead to invocations against the same target bean on multiple servers. I don't see any reason for FirstAvailable.electedTarget to be transient. Problem here is changing this changes the serialized form of the class, breaking interoperability. Class also does not implement Externalizable. -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5005) Upgrade to JBoss Cache 1.4.1.SP7

by Brian Stansberry (JIRA)

Upgrade to JBoss Cache 1.4.1.SP7 -------------------------------- Key: JBAS-5005 URL: http://jira.jboss.com/jira/browse/JBAS-5005 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA Includes some useful fixes around buddy replication. -- 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

18 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4925) Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)

by Dimitris Andreadis (JIRA)

Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5) ------------------------------------------------- Key: JBAS-4925 URL: http://jira.jboss.com/jira/browse/JBAS-4925 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBoss Cache Affects Versions: JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA Upgrade JBossCache to the latest SP6. -- 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

18 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4934) JBossCacheWrapper should not re-use data gravitation option

by Brian Stansberry (JIRA)

JBossCacheWrapper should not re-use data gravitation option ----------------------------------------------------------- Key: JBAS-4934 URL: http://jira.jboss.com/jira/browse/JBAS-4934 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA JBossCacheWrapper has a minor optimization where it creates an instance of Option, sets it to forceDataGravitation=true and then tries to re-use it across all invocations where we need to gravitate. This is invalid usage; JBC does not promise an Option will be in its original state when an invocation returns. Just need to create an Option for each call; no big deal. -- 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

18 years, 7 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 November 2007