March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-639) Allow stream factory to specified for all transports

by Tim Fox (JIRA)

Allow stream factory to specified for all transports ---------------------------------------------------- Key: JBREM-639 URL: http://jira.jboss.com/jira/browse/JBREM-639 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tim Fox Assigned To: Tom Elrod Normally marshallers will receive the raw underlying transport Input/OuputStream. In some cases we want to wrap this in a different stream, e.g.in the case of JBossMessaging we want this wrapped in a DataInput/DataOutputStream. This is accomplished by specifiying a new Client/ServerSocketWrapper in the socket transport URI params which creates the DataInput/OutputStream. This works fine for the socket transport, but does not work for other transports which do not use SocketWrappers. E.g. JBM needs to use the HTTP transport too, and needs the underlying stream wrapped in a DataOutput/InputStream. The current remoting implementation will pass in the underlying stream to the marshaller when the HTTP transport is used, which means we have create and wrap a new DataInput/OuputStream on each invocation request and response which may have performance implications. Suggestion is to allow a InputStream/OuputStream factory to be specified for ANY transport, not just the socket transport. This would allow how streams are wrapped to be determined in a much more consistent way. Suggestion is to allow the stream factory to be specified in the URI params, e.g. &streamFactoryClass=org.jboss.tim.MyStreamFactory, and this to be allowed for any transport. If factory is not specified then raw stream is passed into marshaller. -- 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, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBREM-699) Extend the Marshaller/UnMarshaller interfaces by incorporating the PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces

by Ron Sigal (JIRA)

Extend the Marshaller/UnMarshaller interfaces by incorporating the PreferredStreamMarshaller/PreferredStreamUnMarshaller interfaces ----------------------------------------------------------------------------------------------------------------------------------- Key: JBREM-699 URL: http://jira.jboss.com/jira/browse/JBREM-699 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Alpha1 (Otter) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 3.0.0.Alpha1 (Otter) It is reasonable for all marshallers/unmarshallers to construct the streams they which to use, but the org.jboss.remoting.marshal.PreferredStreamMarshaller and PreferredStreamUnMarshaller interfaces were introduced in response to JBREM-692 to avoid API changes in between major releases. Release 3.0 would be the right time to incorporate and eliminate PreferredStreamMarshaller and PreferredStreamUnMarshaller. -- 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBREM-554) Let virtual MultiplexServerInvokers share master MultiplexServerInvoker's thread pool.

by Ron Sigal (JIRA)

Let virtual MultiplexServerInvokers share master MultiplexServerInvoker's thread pool. -------------------------------------------------------------------------------------- Key: JBREM-554 URL: http://jira.jboss.com/jira/browse/JBREM-554 Project: JBoss Remoting Issue Type: Task 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) This is JBREM-402, broken out from JBREM-390. -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBREM-729) Make multiplex server invoker more robust

by Ron Sigal (JIRA)

Make multiplex server invoker more robust ----------------------------------------- Key: JBREM-729 URL: http://jira.jboss.com/jira/browse/JBREM-729 Project: JBoss Remoting Issue Type: Task 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) Claudia Richter has reported some problems using Remoting JNDI detection with multiplex transport. If the JNDI heartbeat is looking for an old socket invoker at an address and port where a multiplex invoker currently runs, the multiplex invoker can get hung up trying to process in invocation intended for the socket invoker. It should be able to tolerate unexpected inputs. In particular, MultiplexServerInvoker should set a timeout on the MasterServerSocket so that it doesn't get hung up in accept(). -- 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, 11 months

1
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-879) Allow socket buffers to be configurable

by Tim Fox (JIRA)

Allow socket buffers to be configurable --------------------------------------- Key: JBMESSAGING-879 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-879 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 We should allow the socket send and receive buffers as well as the BufferedOutputStream/BufferedInputStream buffer sizes to be configurable. It is important to be able to have large buffer sizes especially when tuning for high RTT networks. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1247) "Save As" functionality for CMS content

by Martin Putz (JIRA)

"Save As" functionality for CMS content --------------------------------------- Key: JBPORTAL-1247 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1247 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha2, 2.4.1 SP1 Reporter: Martin Putz Assigned To: Roy Russo In addition to the copy and move functionality for CMS content, there should be something like a "Save As" feature that allows to move or copy a file elsewhere but change its name at the same time. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-599) remoting doc does not cover enabling or configuring leasing from the client side

by Tom Elrod (JIRA)

remoting doc does not cover enabling or configuring leasing from the client side -------------------------------------------------------------------------------- Key: JBREM-599 URL: http://jira.jboss.com/jira/browse/JBREM-599 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: docs Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4176) Error in delist masks the real error creating the connection handle in BaseConnectionManager2

by Adrian Brock (JIRA)

Error in delist masks the real error creating the connection handle in BaseConnectionManager2 --------------------------------------------------------------------------------------------- Key: JBAS-4176 URL: http://jira.jboss.com/jira/browse/JBAS-4176 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Assigned To: Weston Price Fix For: JBossAS-4.2.0.CR1 There is a problem with the error reporting in BaseConnectionManager2.allocationConnection(). When it can't get a connection handle, it invokes managedConnectionDisconnected() to make sure any work already done is undone, e.g. delist the resource and return to the pool. The problem is that an error thrown from managedConnectionDisconnected() will be given to the user rather than the original error thrown when getting the handle. // Ask the managed connection for a connection Object connection = null; try { connection = cl.getManagedConnection().getConnection(subject, cri); } catch (Throwable t) { // HERE: Error from this method managedConnectionDisconnected(cl); // Means this original error is not thrown JBossResourceException.rethrowAsResourceException( "Unchecked throwable in ManagedConnection.getConnection() cl=" + cl, t); } In fact, if we do get an error asking for a handle, we should probably just quietly (no logging above DEBUG) destroy the connection and then rethrow the original error. i.e. catch (Throwable t) { // HERE: Destroy the connection returnManagedConnection(cl, true); JBossResourceException.rethrowAsResourceException( "Unchecked throwable in ManagedConnection.getConnection() cl=" + cl, t); } -- 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, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate

by Brian Stansberry (JIRA)

Remove EJBTHREE-798 workaround once issue is fixed in Hibernate --------------------------------------------------------------- Key: EJBTHREE-799 URL: http://jira.jboss.com/jira/browse/EJBTHREE-799 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC10 - 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-20) Map the jboss TRACE level logging to log4j TRACE

by Dimitris Andreadis (JIRA)

Map the jboss TRACE level logging to log4j TRACE ------------------------------------------------ Key: JBCOMMON-20 URL: http://jira.jboss.com/jira/browse/JBCOMMON-20 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-old, logging-log4j Affects Versions: 1.0.4.GA, 2.0.1.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA, 2.0.4.GA See JBAS-4163 -- 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, 11 months

1
4
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 March 2007