January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBREM-238) JBossRemoting testsuite needs to generate artificats in the output folder

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-238?page=all ] Ron Sigal updated JBREM-238: ---------------------------- Fix Version/s: 2.4.0.CR1 (Pinto) (was: 2.4.0.Beta1 (Pinto)) Assignee: Ron Sigal > JBossRemoting testsuite needs to generate artificats in the output folder > ------------------------------------------------------------------------- > > Key: JBREM-238 > URL: http://jira.jboss.com/jira/browse/JBREM-238 > Project: JBoss Remoting > Issue Type: Task > Components: general > Reporter: Adrian Brock > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.4.0.CR1 (Pinto) > > > The JBossRemoting testsuite is dumping its artifacts in the root of the project rather than output. > e.g. cvs diff: > ? MultiThreadPerformanceTestCase_benchmark.txt > ? MultiThreadedRMIPerformanceTestCase_benchmark.txt > ? PerformanceClientSideTestCase_benchmark.txt > ? PerformanceServerSideTestCase_benchmark.txt > ? PerformanceTestCase_benchmark.txt > ? RMIPerformanceTestCase_benchmark.txt > ? data > ? debug_output.log > ? start_1132237128739.txt > ? start_1132237129627.txt > etc. > Eventually somebody is going to commit these to cvs by mistake. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-167) RMI Invoker does not use true remoting marshalling/unmarshalling

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-167?page=all ] Ron Sigal updated JBREM-167: ---------------------------- Fix Version/s: 2.4.0.CR1 (Pinto) (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > RMI Invoker does not use true remoting marshalling/unmarshalling > ---------------------------------------------------------------- > > Key: JBREM-167 > URL: http://jira.jboss.com/jira/browse/JBREM-167 > Project: JBoss Remoting > Issue Type: Bug > Components: transport > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > Fix For: 2.4.0.CR1 (Pinto) > > > In process of fixing JBREM-165 (RMI support for UnifiedInvoker), have added ability to call on mashaller when making request so that can modify payload before sending. Although the RMIInvokerClient does use the configured marshaller, it does not use the configured unmarshaller (RMIInvokerServer is the opposite). This was done to get JBREM-165 working, but is not a total solution and needs to be fixed so anyone can add a marshaller/unmarshaller for RMI invoker that will be called both ways (in and out) on both the client and server. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-799) Add a separate timeout parameter for callback clients, part 2

by Ron Sigal (JIRA)

Add a separate timeout parameter for callback clients, part 2 ------------------------------------------------------------- Key: JBREM-799 URL: http://jira.jboss.com/jira/browse/JBREM-799 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) This issue is a continuation of JBREM-765 "Add a separate timeout parameter for callback clients". The changes have been applied to branches remoting_2_2_0_GA and remoting_2_x, but unit tests exist only for transports socket and bisocket. A unit test should be written for the RMI transport as well. However, no additional changes will be made to Remoting 2.2.2.GA, so this issue is introduced for 2.4.0. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-851) In LeasePinger and TimerUtil replace Timer if it has shut down

by Ron Sigal (JIRA)

In LeasePinger and TimerUtil replace Timer if it has shut down -------------------------------------------------------------- Key: JBREM-851 URL: http://jira.jboss.com/jira/browse/JBREM-851 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When all of the TimerTasks running in a java.util.TimerTask have shut down, the TImer will also shut down, at which point it will accept no more TimerTasks. There are places in Remoting where there should be a test which will create a new Timer the attempt to schedule a TimerTask results in an exception. Two places the problem exists: 1. org.jboss.remoting.LeasePinger, and 2. org.jboss.remoting.util.TimerUtil. A similar problem is described in JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer" Reported by James on Remoting forum. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-804) Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator

by Ron Sigal (JIRA)

Enable HTTPClientInvoker to accept NO_THROW_ON_ERROR configuration by way of InvokerLocator ------------------------------------------------------------------------------------------- Key: JBREM-804 URL: http://jira.jboss.com/jira/browse/JBREM-804 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.GA Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, the value for the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.NO_THROW_ON_ERROR in org.jboss.remoting.transport.http.HTTPClientInvoker is configurable only by way of the invocation metadata map passed to org.jboss.remoting.Client.invoke(). However, for EJB3 invocations, the Client is created by the EJB3 proxy (org.jboss.aspects.remoting.InvokeRemoteInterceptor, in particular) and is not accessible by application code. If HTTPClientInvoker checked the InvokerLocator for this parameter, then it could be configured declaratively in the EJB3 jboss-service.xml file. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5188) RoleBasedAuthorizationInterceptorv2 needs to set the contextid on the PolicyContext

by Anil Saldhana (JIRA)

RoleBasedAuthorizationInterceptorv2 needs to set the contextid on the PolicyContext ----------------------------------------------------------------------------------- Key: JBAS-5188 URL: http://jira.jboss.com/jira/browse/JBAS-5188 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta4 The authorization layer may be configured with jacc authorization module. Hence the ejb3 layer needs to ensure that the policy context jacc id is set. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4943) jboss-ds_1_5.dtd is wrong

by Michael Lipp (JIRA)

jboss-ds_1_5.dtd is wrong ------------------------- Key: JBAS-4943 URL: http://jira.jboss.com/jira/browse/JBAS-4943 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, JCA service Affects Versions: JBossAS-4.0.5.GA Environment: Any Reporter: Michael Lipp Assigned To: Norman Richards The jboss-ds_1_5.dtd (as distributed in docs/dtd/) is wrong or not up-to-date (and there is no newer version and no out-of-date mark). As has been pointed out by Adrian Brock in JBAS-4942, it is possible to specify a loader-repository like this: <connection-factories>  <loader-repository>jboss.test:loader=JavaClassIsolation</loader-repository> <tx-connection-factory>  <rar-name>some.ear#some.rar</rar-name> <etc/> </tx-connection-factory> </connection-factories> ... although this is not compliant with the DTD! Keeping the DTD up-to-date would avoid unnecessary bug reports and/or forum questions because looking at the DTD is the first step in finding out how to configure required behavior. -- 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, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-5169) Typo Code Example for 6.5. Creating a JDBC client

by Robin Gower (JIRA)

Typo Code Example for 6.5. Creating a JDBC client ------------------------------------------------- Key: JBAS-5169 URL: http://jira.jboss.com/jira/browse/JBAS-5169 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Getting Started Guide Environment: na Reporter: Robin Gower Priority: Trivial The code example on this page has a typo: http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/G... The final "%>" tag is missing. ps. Great guide! -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5172) Typo in 5.2 setting JBOSS_HOME

by Scott Dickerson (JIRA)

Typo in 5.2 setting JBOSS_HOME ------------------------------ Key: JBAS-5172 URL: http://jira.jboss.com/jira/browse/JBAS-5172 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Getting Started Guide Affects Versions: JBossAS-5.0.0.Beta3 Environment: windows xp Reporter: Scott Dickerson Priority: Minor c:\Program\Files should be c:\Program Files. Don't you hate Microsoft for giving us the "Program Files" folder name. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4819) TECH REVIEW: Installation Guide - TRACKER

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - TRACKER ----------------------------------------- Key: JBAS-4819 URL: http://jira.jboss.com/jira/browse/JBAS-4819 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Tracker for Chapter Edits of the Installation Guide -- 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, 3 months

4
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 January 2008