February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3721) Clustered SSO entries not properly cleaned up if a server crashes

by Brian Stansberry (JIRA)

Clustered SSO entries not properly cleaned up if a server crashes ------------------------------------------------------------------ Key: JBAS-3721 URL: http://jira.jboss.com/jira/browse/JBAS-3721 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.6.CR1 If a server crashes, the entries for its sessions in the clustered sso cache will never be removed, and thus the sso may never be removed. TreeCacheSSOManager needs to listen for view changes and discard sessions associated with dead servers. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-640) Implement an asynchronous method for handling callbacks.

by Ron Sigal (JIRA)

Implement an asynchronous method for handling callbacks. -------------------------------------------------------- Key: JBREM-640 URL: http://jira.jboss.com/jira/browse/JBREM-640 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Tim Fox: Currently, it's my understanding that push callbacks (using socket transport anyway) are synchronous, i.e. the server side thread that executes the callback blocks until the callback has been delivered to the client side and returned. Is it currrently possible to execute asynch push callbacks? I.e. the thread that calls the callback returns immediately once it has registered the callback with remoting. And it is then delivered on a different thread? Ideally executing using some kind of executor (e.g. PooledExecutor) with a bounded queue size which blocks when it is full would be ideal. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-697) Horg.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory.ComparableHolder should use InetAddress for host.

by Ron Sigal (JIRA)

Horg.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory.ComparableHolder should use InetAddress for host. ------------------------------------------------------------------------------------------------------------------ Key: JBREM-697 URL: http://jira.jboss.com/jira/browse/JBREM-697 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) ComparableHolders are used as the keys in the static Map which maps InvokerLocators to configuration Maps for RemotingRMIClientSocketFactory's. It currently represents the host name as a string, which means that equals() will not correctly identify two names for the same host. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-863) StatefulTreeCache does not properly set thread context classloader

by Brian Stansberry (JIRA)

StatefulTreeCache does not properly set thread context classloader ------------------------------------------------------------------ Key: EJBTHREE-863 URL: http://jira.jboss.com/jira/browse/EJBTHREE-863 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - FD Before invoking prePassivate on a StatefulBeanContext, StatefulTreeCache needs to set the TCCL to the container's classloader. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4021) Distinct system properties for mcast_port in each config file

by Brian Stansberry (JIRA)

Distinct system properties for mcast_port in each config file ------------------------------------------------------------- Key: JBAS-4021 URL: http://jira.jboss.com/jira/browse/JBAS-4021 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Optional Fix For: JBossAS-4.2.0.CR1 Using a startup switch for the JGroups UDP mcast_port is not possible in a non-multiplexer environment, because every channel should use a separate port. But, we can add some properties to the standard config files to make it easier for users to set the ports via -D. cluster-service.xml -- ${jboss.hapartition.mcast_port:45566} jboss-web-cluster.sar/META-INF/jboss-service.xml -- ${jboss.webpartition.mcast_port:45577} ejb3-entity-cache-service.xml -- ${jboss.ejb3entitypartition.mcast_port:43333} ejb3-clustered-sfsbcache-service.xml -- ${jboss.ejb3sfsbpartition.mcast_port:45551} -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-159) Forums doesn't work with Portal 2.6-Alpha1 - org.jboss.portal.identity.User has changed.

by Ian White (JIRA)

Forums doesn't work with Portal 2.6-Alpha1 - org.jboss.portal.identity.User has changed. ---------------------------------------------------------------------------------------- Key: JBFORUMS-159 URL: http://jira.jboss.com/jira/browse/JBFORUMS-159 Project: JBoss Forums Issue Type: Bug Components: Portlet Productization Affects Versions: 1.0.0 Alpha Environment: AS 4.0.5.GA, Portal 2.6 Alpha1, Forums 1.0.0 AlphaP2.6DR Reporter: Ian White Assigned To: Ryszard Kozmik I realise that the latest distribution of Forums for Portal 2.6DR is meant for 2.6DR, but I'm trying to get it working with 2.6 Alpha1. Simple one: org.jboss.portal.portlet.Parameters is renamed PortletParameters. But I could really do with some help with the change to org.jboss.identity.User. Should I now use HibernateUserImpl ? This change would ripple through several interfaces and classes. Any help much appreciated. Thanks. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-696) ServerAddress.equals() and hashCode() are broken, they dont' take timeout into account

by Ovidiu Feodorov (JIRA)

ServerAddress.equals() and hashCode() are broken, they dont' take timeout into account -------------------------------------------------------------------------------------- Key: JBREM-696 URL: http://jira.jboss.com/jira/browse/JBREM-696 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha6 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 2.2.0.Alpha7 Added a test in messaging: org.jboss.test.thirdparty.remoting.ServerAddressTest.testEquals() I would reccommend you add a corrresponding test in Remoting. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-643) Snapshot of package capability

by Michael Neale (JIRA)

Snapshot of package capability ------------------------------ Key: JBRULES-643 URL: http://jira.jboss.com/jira/browse/JBRULES-643 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-402) Consolidate configuration instructions from the Getting Started and Release Notes

by Bruno Georges (JIRA)

Consolidate configuration instructions from the Getting Started and Release Notes --------------------------------------------------------------------------------- Key: JBESB-402 URL: http://jira.jboss.com/jira/browse/JBESB-402 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Reporter: Bruno Georges Assigned To: Mark Little Priority: Minor Fix For: 4.0 Maintenance Pack 1 In http://labs.jboss.com/file-access/default/members/jbossesb/downloads/4.0G... We have: In the server/default/conf directory you will find two config files: jbossesb-listener.xml jbossesb-gateway.xml !!! you can add xml fragments in there and when the controller reload your listeners and gateways come up !!! So try pasting in the Hello World config. and in jbossesb-4.0GA/docs/GettingStarted.pdf We have : They are the :jbossesb-listener.xml and jbossesb-gateway.xml. These represent the configuration as it will be consumed by the esb engine, which where generated from the jbossesb.xml file. There should be no need for you to interact with the generated file. You can add xml fragments in to the jbossesb.xml and when the controller reloads your listeners and gateways come up. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-399) Check document summaries are right

by Mark Little (JIRA)

Check document summaries are right ---------------------------------- Key: JBESB-399 URL: http://jira.jboss.com/jira/browse/JBESB-399 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Maintenance Pack 1 The Message Transformation Guide has "Highlevel Overview of Rosetta". -- 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, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007