March 2010 - jboss-remoting-issues

[JBoss JIRA] Issue Comment Edited: (JBREM-827) Define a management interface for JBoss Remoting

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] Trustin Lee edited comment on JBREM-827 at 3/25/10 1:22 AM: ------------------------------------------------------------ If the number of connections are expected to be small, it might be fine as you said. As long as we have an option that disables JMX exports, it will be fine. Authentication failures could be represented as rejected clients? (i.e. clientCounters.failure) What information else could be provided by EndpointMXBean / ConnectionMXBean by the way? A user might want to know where exactly the endpoint / connection is pointing at. Will the MBean object name be enough? was (Author: trustin): If the number of connections are expected to be small, it might be fine as you said. As long as we have an option that disables JMX exports, it will be fine. Authentication failures could be represented as rejected clients? (i.e. clientCounters.failure) What information else could be provided by EndpointMXBean / ConnectionMXBean by the way? A user might want to know where exactly the endpoint is pointing at or what the client ID is in a connection. Will the MBean object name be enough? > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-827) Define a management interface for JBoss Remoting

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] Trustin Lee commented on JBREM-827: ----------------------------------- If the number of connections are expected to be small, it might be fine as you said. As long as we have an option that disables JMX exports, it will be fine. Authentication failures could be represented as rejected clients? (i.e. clientCounters.failure) What information else could be provided by EndpointMXBean / ConnectionMXBean by the way? A user might want to know where exactly the endpoint is pointing at or what the client ID is in a connection. Will the MBean object name be enough? > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-827) Define a management interface for JBoss Remoting

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] David Lloyd commented on JBREM-827: ----------------------------------- Also, an idea occurs to me - for the Remote protocol, we might want to track authentication failures (client & server). I'm not sure how we'd want to present that info though. > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-827) Define a management interface for JBoss Remoting

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] David Lloyd commented on JBREM-827: ----------------------------------- On the one hand, Connections shouldn't be all that common since you can have many clients opened per connection, so the expectation is that they'll be reused. Of course that doesn't mean they *will* be reused. Maybe instead, have an operation on Endpoint which enumerates connections somehow, with some information and an index of some sort? Then operations can be performed by index. > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-827) Define a management interface for JBoss Remoting

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] Trustin Lee commented on JBREM-827: ----------------------------------- Here's the draft: http://anonsvn.jboss.org/repos/jbossremoting/remoting3/trunk/jboss-remoti... There are two MXBeans: EndpointMXBean and ConnectionMXBean. They are almost identical except that ConnectionMXBean has close/forceClose operations while EndpointMXBean does not and that you can list the registered services with EndpointMXBean while you can't with ConnectionMXBean. They both provide some counters via the Counters object. Once agreed, I will finish documentation. One missing piece though is how we register an MBean for a connection. We could register all EndpointMXBeans automatically but we can't do that for Connections because there will be much more connections and registering that many connections will probably pollute the JMX console with overinformation. What user wants might be to register only the ConnectionMXBeans that meet some criteria..? Long time ago, I wrote a JMX operation that accepts some expression so that only the MBeans that meets the specified condition, but I'm not sure it's a good idea since it's a lot of work. > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1213) If the server fails to create a SaslServer, it never sends an error back to the client

by David Lloyd (JIRA)

If the server fails to create a SaslServer, it never sends an error back to the client -------------------------------------------------------------------------------------- Key: JBREM-1213 URL: https://jira.jboss.org/jira/browse/JBREM-1213 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBREM-661) Allow server sending a stream to the client

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-661?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-661. ----------------------------- Fix Version/s: 3.1.0.Beta3 (was: 2.5.3.Beta (Flounder)) Resolution: Done Assignee: David Lloyd This is an inherent part of Remoting 3. > Allow server sending a stream to the client > ------------------------------------------- > > Key: JBREM-661 > URL: https://jira.jboss.org/jira/browse/JBREM-661 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Helmut Wick > Assignee: David Lloyd > Fix For: 3.1.0.Beta3 > > > As of release 2.0.0 GA, there is no way for a server to send a stream to the client (only the other way around). > This is to request something like java.io.InputStream Client.invoke(java.lang.Object param) > that allows for true streaming (like java.lang.Object invoke(java.io.InputStream inputStream, java.lang.Object param) does). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-505) convert jndi to use remoting for transport

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-505?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-505. ----------------------------- Resolution: Duplicate Issue Duplicates JBAS-3151. > convert jndi to use remoting for transport > ------------------------------------------ > > Key: JBREM-505 > URL: https://jira.jboss.org/jira/browse/JBREM-505 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: External_issues > Reporter: Tom Elrod > > Need to convert jndi to use remoting as transport. Ties in with JBREM-424. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-398) bring AOP Remoting under JBossRemoting project

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-398?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-398. ----------------------------- Resolution: Out of Date > bring AOP Remoting under JBossRemoting project > ---------------------------------------------- > > Key: JBREM-398 > URL: https://jira.jboss.org/jira/browse/JBREM-398 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > > Need to bring AOP Remoting under the JBossRemoting project for further development and maintenance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-566) update jbossws to include 2.0.0 in component-info.xml

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-566?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-566. ----------------------------- Resolution: Out of Date Assignee: (was: Tom Elrod) > update jbossws to include 2.0.0 in component-info.xml > ----------------------------------------------------- > > Key: JBREM-566 > URL: https://jira.jboss.org/jira/browse/JBREM-566 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.CR1 (Boon) > Reporter: Tom Elrod > Fix For: External_issues > > > Have already e-mailed ws team. Need this to be updated in repository or won't be able to update build-thirdpary.xml within jbossas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues March 2010