November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBREM-142) better configuration for stream server

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-142?page=all ] Tom Elrod updated JBREM-142: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > better configuration for stream server > -------------------------------------- > > Key: JBREM-142 > URL: http://jira.jboss.com/jira/browse/JBREM-142 > Project: JBoss Remoting > Issue Type: Feature Request > Components: stream > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Minor > Fix For: 2.2.0.Beta1 (Bluto) > > > The stream server does have basic configuration for transport, host, and port via system properties (see JBREM-125), but needs better alternative for configuration. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-510) SSLSocketBuilder should require a SocketFactory in server mode to have a keystore.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-510?page=all ] Tom Elrod updated JBREM-510: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > SSLSocketBuilder should require a SocketFactory in server mode to have a keystore. > ---------------------------------------------------------------------------------- > > Key: JBREM-510 > URL: http://jira.jboss.com/jira/browse/JBREM-510 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.0.Beta1 (Bluto) > > > SSLSocketBuilder needs to > 1. allow a ServerSocketFactory in client mode to not have a keystore, and > 2. require a SocketFactory in server mode to have a keystore. > Part 1 is fixed as of 6/20/06, as part of changes made for JBREM-368/JBREM-491. -- 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

19 years, 6 months

1
0
0 / 0

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

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-167?page=all ] Tom Elrod updated JBREM-167: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > 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 > Assigned To: Tom Elrod > Priority: Minor > Fix For: 2.2.0.Beta1 (Bluto) > > > 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-381) IIOP transport impl for remoting

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-381?page=all ] Tom Elrod updated JBREM-381: ----------------------------- Fix Version/s: 3.0.0.Alpha1 (Otter) (was: 2.2.0.Alpha3 (Bluto)) > IIOP transport impl for remoting > -------------------------------- > > Key: JBREM-381 > URL: http://jira.jboss.com/jira/browse/JBREM-381 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.1 final > Reporter: Tom Elrod > Assigned To: Ron Sigal > Priority: Minor > Fix For: 3.0.0.Alpha1 (Otter) > > -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-475) Eliminate ShutdownRequestThread in MultiplexingManager.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-475?page=all ] Tom Elrod updated JBREM-475: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > Eliminate ShutdownRequestThread in MultiplexingManager. > ------------------------------------------------------- > > Key: JBREM-475 > URL: http://jira.jboss.com/jira/browse/JBREM-475 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.0.Beta1 (Bluto) > > > When a MultiplexingManager is requesting permission from its remote counterpart to shut down, it periodically creates a ShutdownRequestThread to send a request permission message and wait for a response. It shoud be possible to handle the waiting on the pending action thread. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-525) Automatically set HostnameVerifier in HTTPSClientInvoker to allow all hosts if authorization is turned off.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-525?page=all ] Tom Elrod updated JBREM-525: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > Automatically set HostnameVerifier in HTTPSClientInvoker to allow all hosts if authorization is turned off. > ----------------------------------------------------------------------------------------------------------- > > Key: JBREM-525 > URL: http://jira.jboss.com/jira/browse/JBREM-525 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.0.Beta1 (Bluto) > > > Currently, HTTPSClientInvoker will set HostnameVerifier to inner class AnyhostVerifer, which accepts all host names, if it is configured with HTTPSClientInvoker.IGNORE_HTTPS_HOST set to "true". It could also check the values of SSLSocketBuilder.REMOTING_SERVER_AUTH_MODE and SSLSocketBuilder.REMOTING_CLIENT_AUTH_MODE and turn use AnyhostVerifier if authorization is turned off. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-344) support for NTLM authentication

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-344?page=all ] Tom Elrod updated JBREM-344: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > support for NTLM authentication > ------------------------------- > > Key: JBREM-344 > URL: http://jira.jboss.com/jira/browse/JBREM-344 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-433) point to multipoint invocation api

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-433?page=all ] Tom Elrod updated JBREM-433: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > point to multipoint invocation api > ---------------------------------- > > Key: JBREM-433 > URL: http://jira.jboss.com/jira/browse/JBREM-433 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time. The responses for each target server would be aggregated into one response as return to the client call. Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for this. -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBREM-369) For Connectors that support callbacks on SSL connections, there should be a unified means of configuring SSLServerSocket and callback Client SSLSocket.s.

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-369?page=all ] Ron Sigal reassigned JBREM-369: ------------------------------- Assignee: Ron Sigal (was: Tom Elrod) > For Connectors that support callbacks on SSL connections, there should be a unified means of configuring SSLServerSocket and callback Client SSLSocket.s. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-369 > URL: http://jira.jboss.com/jira/browse/JBREM-369 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Beta1 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta1 (Bluto) > > > Currently, the SSLServerSocket is configured by creating an SSLServerSocketFactory, e.g., by way of configuring an SSLSocketBuilder, and calling setServerSocketFactory() on the server invoker. The SSLSockets used by the Client that makes push callbacks are configured by passing a configuration Map to the Connector constructor, which is used to create a RemotingSSLSocketFactory. These should be unified. In particular, it would be nice to pass a single configuration Map to Connector(). -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-364) refactor client invoker config for common configurations

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-364?page=all ] Tom Elrod updated JBREM-364: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > refactor client invoker config for common configurations > -------------------------------------------------------- > > Key: JBREM-364 > URL: http://jira.jboss.com/jira/browse/JBREM-364 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > Currently client invoker implementations all do their own configuration processing. Since many share the same configuration properties, need to standardize these and handle them in the RemoteClientInvoker instead of individual implementations (i.e. SocketClientInvoker, HTTPClientInvoker, etc.). Should follow same model that has been done for ServerInvoker. -- 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

19 years, 6 months

1
0
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 2006