April 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Remoting, Unified Invokers] - Re: Server side thread leak?

by ron.sigal＠jboss.com

I wrote : | As long as the timeout is that short, then turning on idle thread reaping may not be necessary after all. | Nah, that doesn't make sense. It's true that the sockets would get closed, but the ServerThread would just return to the pool. And it's true that the ServerThread could be reused, but the number of threads would be monotonically non-decreasing, growing as the momentary demand exceeds the number of available threads. I.e., I'm back in favor of idle thread reaping. Flippity-flop. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222836#4222836 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222836

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by anil.saldhana＠jboss.com

With the lifecycle registration, I can see that xxxLifecycleCallback methods for my annotation xxx are being called. So currently I can proceed with my annotation. Kabir, regarding the @JMX annotation, maybe you want to change the lifecycle registration to aim at the JMXLifecycleCallback class rather than the call back methods from the system workspace. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222825#4222825 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222825

16 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Registering an XSD for use by a SchemaResolverDeployer

by david.lloyd＠jboss.com

Ales says this is a JBossXB question, not a MC question, so here goes: Where can I put my .xsd file so that my SchemaResolverDeployer uses it for validation? If I put it in META-INF, will JBossXB (or something else) find and register it? Original post was here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153408 Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222824#4222824 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222824

16 years, 6 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: JBAS-6689 add support for activation policy metadata on

by charles.crouch＠jboss.com

"scott.stark(a)jboss.org" wrote : I think these are warnings coming from updates post template creation of the destination. They can't be read-only as in ignored because the template uses the same properties. | I think its fine for the ObjectName, JNDIName, Clustered properties to be read-only in the console since we support being able to set read-only properties once at creation time and then not edit them later. "scott.stark(a)jboss.org" wrote : We don't know if the component has failed to apply the change without an exception being thrown here. This does not seem to be the case as the change is ignored and the log message the only indication of failure. | >From trying to make changes to properties such as DownCacheSize via the jmx-console its clear, as you say, that any updates that are attempted are ignored by the underlying messaging implementation, i.e. the old value remains after the update. Given that, would it not be possible for the profile service to try to make a change on a property, then requery that property to see if that change had "stuck"? If not an exception would be raised. This seems like a bit of hack to support this one particular case, (where really the managed resource itself should be throwing the exception) but I dont think its practical to expect the JBM team to change how this is implemented at this stage. "scott.stark(a)jboss.org" wrote : If the properties are updated to be *_RESTART, then we can avoid dispatching the change to the runtime component at the profileservice level and avoid the warning it emits. | If this is achievable quickly then it sounds like a reasonable use for the activation policies, since we're not really going to be able to use them elsewhere yet. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222821#4222821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222821

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by bstansberry＠jboss.com

"anil.saldhana(a)jboss.com" wrote : I think the lifecycle declaration for JndiBinding does not exist. Until that happens, the annotation is not useful. Yep, that's what I meant. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222820#4222820 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222820

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by bstansberry＠jboss.com

"bstansberry(a)jboss.com" wrote : just that applying the annotation doesn't currently do anything.) I should say it didn't do anything at one point in second half of last year; don't know about now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222819#4222819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222819

16 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: MessagingXAResourceRecovery?

by clebert.suconic＠jboss.com

NM: just found the JIRA: https://jira.jboss.org/jira/browse/JBMESSAGING-1506 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222818#4222818 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222818

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by anil.saldhana＠jboss.com

"bstansberry(a)jboss.com" wrote : There may not be one anywhere. I don't think @Jndi actually works. (Not that the code doesn't work if the lifecycle-xxx declaration is there; just that applying the annotation doesn't currently do anything.) I think the lifecycle declaration for JndiBinding does not exist. Until that happens, the annotation is not useful. As I see it, the code for the lifecycle callbacks for JMX in the system folder are quite identical to the JMXCallback class. Kabir, there are two sets of callback classes (one in the system folder and the other is the JMXCallback). The lifecycle declaration is for the former. I guess lifecycle declaration can be for the latter alone (I am going to try it out on my annotation). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222817#4222817 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222817

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by bstansberry＠jboss.com

There may not be one anywhere. I don't think @Jndi actually works. (Not that the code doesn't work if the lifecycle-xxx declaration is there; just that applying the annotation doesn't currently do anything.) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222814#4222814 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222814

16 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Annotation for MC bean

by anil.saldhana＠jboss.com

Kabir, do you know where the lifecycle declaration for the @JndiBinding annotation is? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222811#4222811 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222811

16 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009