December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-703) allow for total configuration of socket via socket invoker

by Tom Elrod (JIRA)

allow for total configuration of socket via socket invoker ---------------------------------------------------------- Key: JBREM-703 URL: http://jira.jboss.com/jira/browse/JBREM-703 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Currently remoting does not expose all the configuration properties for a socket for the socket invokers. Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize) -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-739) Fix java serialization leak.

by Ron Sigal (JIRA)

Fix java serialization leak. ---------------------------- Key: JBREM-739 URL: http://jira.jboss.com/jira/browse/JBREM-739 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP2 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP2 Bug was reported in JBAS-4359. -- 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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-809) Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct

by Tom Fennelly (JIRA)

Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct --------------------------------------------------------------------------------------------- Key: JBREM-809 URL: http://jira.jboss.com/jira/browse/JBREM-809 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: marshall Affects Versions: 2.2.2.GA Reporter: Tom Fennelly Assigned To: Trustin Lee At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream. This causes it to modify the message payload by removing the CR and LF characters. This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars. It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars. We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader. -- 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, 4 months

2
11
0 / 0

[JBoss JIRA] Created: (JBREM-842) Deprecate multiplex transport

by Ron Sigal (JIRA)

Deprecate multiplex transport ----------------------------- Key: JBREM-842 URL: http://jira.jboss.com/jira/browse/JBREM-842 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) The multiplex transport has never been used in JBoss software, and Remoting 3.0 will offer connection multiplexing capabilities. -- 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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-864) CLONE -ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6

by Ron Sigal (JIRA)

CLONE -ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6 ------------------------------------------------------------------------------------------ Key: JBREM-864 URL: http://jira.jboss.com/jira/browse/JBREM-864 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 Reporter: Takayoshi Kimura Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP3 IPv6 address contains ":" character, so it cannot be used in ObjectName. 2007-10-18 15:37:40,476 WARN [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer. javax.management.MalformedObjectNameException: Invalid character ':' in value part of property at javax.management.ObjectName.construct(ObjectName.java:529) at javax.management.ObjectName.<init>(ObjectName.java:1304) at org.jboss.remoting.transport.Connector.init(Connector.java:402) at org.jboss.remoting.transport.Connector.create(Connector.java:760) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at org.jboss.system.ServiceController.create(ServiceController.java:349) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.create(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) -- 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, 4 months

1
7
0 / 0

[JBoss JIRA] Created: (JBREM-865) CLONE -Verify IPv6 addresses are handled correctly

by Ron Sigal (JIRA)

CLONE -Verify IPv6 addresses are handled correctly -------------------------------------------------- Key: JBREM-865 URL: http://jira.jboss.com/jira/browse/JBREM-865 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP3 Need to make sure that Remoting can bind ServerSockets to IPv6 addresses. This issue is related to http://jira.jboss.com/jira/browse/JBREM-645. -- 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, 4 months

1
7
0 / 0

[JBoss JIRA] Created: (JBREM-877) New Socket Connection is being Created for Every Client Request to the Server

by Kumarselvan Somasundaram (JIRA)

New Socket Connection is being Created for Every Client Request to the Server ----------------------------------------------------------------------------- Key: JBREM-877 URL: http://jira.jboss.com/jira/browse/JBREM-877 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.2.SP2 Environment: Linux os , Pentium duo Processor with 3.6 Ghz clock Speed, 4GB Ram in this Postgresql Database also Running Reporter: Kumarselvan Somasundaram Priority: Critical whenever EJB3 client requests the Server new socket is being created. at the client side the socket connection pool is not being used. Hope there is some issue with the socket connection after getting response from the server,becoz of which the server side the connection is being closed. this increases the CPU utilization, The same code is running fine in jboss 4.0.4 with jboss remoting 1.4.0 new remoting 2.2.2 SP4 only handling 1/4 of the load with high CPU utilization. -- 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, 4 months

2
14
0 / 0

[JBoss JIRA] Created: (JBAS-4446) JGroups file in lib should be named jgroups-all.jar

by Brian Stansberry (JIRA)

JGroups file in lib should be named jgroups-all.jar --------------------------------------------------- Key: JBAS-4446 URL: http://jira.jboss.com/jira/browse/JBAS-4446 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Name the file jgroups-all.jar, which is what it's named in the JGroups dist. Using a different name makes it too easy to end up with duplicate jars when upgrading, a mistake I've made several times and which we hear about on support from time to 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

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-128) ClassInfo should be serialzable

by Adrian Brock (JIRA)

ClassInfo should be serialzable ------------------------------- Key: JBMICROCONT-128 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-128 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The ClassInfo objects should be serializable, this is currently not the case because they hold references back to their factory to support lazy initialization. -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-222) Write tests for the new convience methods in ComponentMutableMetaData

by Adrian Brock (JIRA)

Write tests for the new convience methods in ComponentMutableMetaData --------------------------------------------------------------------- Key: JBMICROCONT-222 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-222 Project: JBoss MicroContainer Issue Type: Sub-task Components: MetaData Affects Versions: JBossMC-2.0.0.Beta7 Reporter: Adrian Brock Fix For: JBossMC-2.0.0.CR1 Need to write tests for the new convience methods defined in ComponentMutableMetaData e.g. addAnnotation(Method, annotation); etc. -- 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, 4 months

2
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 December 2007