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

[Design the new POJO MicroContainer] - Re: Context installation causes StackOverflowError

by pgier

Ales, I checked your debug output and didn't find any significant differences from mine. The classpath that surefire is using seems to be exactly the same other than the root directories. I don't get the same log4j warnings that you get. Could this be indirectly causing the NCDFE? Maybe you can try adding a log4j.properties file in the test resources directory. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222796#4222796 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222796

15 years, 1 month

1
0
0 / 0

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

by ron.sigal＠jboss.com

"bstansberry(a)jboss.com" wrote : | I guess an issue with #2 is it introduces a Timer thread in the client | Currently, each Client creates a new Timer in Client.disconnect(), but I plan (JBREM-1083 "Each Client creates a new invokerDestructionTimer") to make it as static timer. "bstansberry(a)jboss.com" wrote : | Anything else? | Setting "idleTimeout" to a positive integer to turn on idle thread harvesting. Note that the number is interpreted as seconds rather than milliseconds. Why? Boh. (http://forum.wordreference.com/showthread.php?t=67620) Question: This thread (JBAS-6665, in particular) started in the context of AS 5. What about AS 4.2? EAP 4.2/4.3? -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222794#4222794 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222794

15 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: Close the portlet programmatically

by apemberton

Benson: there are probably a few ways to implement this feature. One possible route: First, add a custom window state: <portlet-app> | ... | <custom-window-state> | <description>Closes the portlet window</description> | <name>close</name> | </custom-window-state> | ... | </portlet-app> Then, implement a custom WindowRenderer that does not display the portlet if it's in 'close' state. Good luck, Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222780#4222780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222780

15 years, 1 month

1
0
0 / 0

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

by bstansberry＠jboss.com

Sounds then like there are two things that need to be done: 1) Fix UnifiedInvokerProxy/UnifiedInvokeHAProxy to call disconnect. 2) Decide if we want to add the "invokerDestructionDelay" as a default config on the AS's Remoting Connectors. I guess an issue with #2 is it introduces a Timer thread in the client, which some may not like. Anything else? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222775#4222775 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222775

15 years, 1 month

1
0
0 / 0

[Design of PVM (Process Virtual Machine)] - undeploying and deleting deployments

by tom.baeyens＠jboss.com

the new repository service manages a set of deployments. you can create new deployments with the repository service and deploy those. long deploymentDbid = repositoryService.createDeployment() | .addResourceFromClasspath("org/jbpm/examples/services/process.jpdl.xml") | .deploy(); | business archive deployer that is part of the jboss integration will make sure that .bar files get deployed like this. now i want to make a distinction between undeploying and deleting deployments. undeploying will mark the deployment as undeployed. it will still exist in the db, but it will not show up in the api and new processes instances cannot be started for process definitions in undeployed deployments. deleting the deployment will remove the deployment from the db. optionally this cascades to active executions and history information. if not cascading and still active executions, then an exception will be thrown. does this distinction between undeployment and deletion of deployments make sense to you as well ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222769#4222769 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222769

15 years, 1 month

1
0
0 / 0

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

by scott.stark＠jboss.org

"charles.crouch(a)jboss.com" wrote : | So starting off I'm not sure adding support for activation policy to the JBAS layer and the console is not practical in the current timeframe (Scott/Emanuel can you comment on the JBAS side?). | Its a simple matter to add an actionvation config value on the property, but tieing it into the lifecycle of the runtime component as a pending config change that is to be applied if the component is restarted is not. Looking at the troublesome properties... "charles.crouch(a)jboss.com" wrote : | From the above its clear that JNDI name and ObjectName should be readonly from the console perspective. | 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. These should have a activation config value of SERVER_RESTART or DEPLOYMENT_RESTART (which is another level of activation we should have). "charles.crouch(a)jboss.com" wrote : | That leaves PageSize, FullSize and DownCacheSize properties which require the destination to be stopped in order for the change to be successfully applied. I don't think the current situation is tenable, i.e. a user tries to change the PageSize property when the queue is running and the profile service responds back with success and when the console queries the ManagedComponent its gets the new value, which does *not* reflect what is actually running in the JBAS instance. | | I think the least that can be done here is to have the profile service return back failure from the update if the values we supplied it didn't actually get applied (Is it possible for the profile service to query the underlying component to check that the suggested updates have been applied?). | 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. "charles.crouch(a)jboss.com" wrote : | Further if I'm not changing PageSize, FullSize and DownCacheSize properties, but one of the properties which can be updated fine while the destination is running, then I should clearly not get any sort of warning or failure. | There is too much of a disconnect between the component and its management object at this point to be able to ensure this behavior. 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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222768#4222768 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222768

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple ClassFileTransformers/Translators

by jason.greene＠jboss.com

"adrian(a)jboss.org" wrote : | I've fixed Jason's "half a job". :-) The release date was 10th March according to | repository.jboss.com. There's now a 2.0.5.GA in JIRA. Sorry about that, this was a late night rush job because it was blocking an AS release which was past due. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222721#4222721 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222721

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple ClassFileTransformers/Translators

by adrian＠jboss.org

"alesj" wrote : | What should be the order of transformation? | 1) domain | 2) policy | Having more "exact" transformation after more "general". | I would say all of them. And if the order matters, then there's something wrong. ;-) That's certainly the rule for Agents. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222710#4222710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222710

15 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: JBossRetro cannot replace final reference to StringBuild

by adrian＠jboss.org

Bug report: https://jira.jboss.org/jira/browse/JASSIST-77 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222706#4222706 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222706

15 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Multiple ClassFileTransformers/Translators

by alesj

"alesj" wrote : | "adrian(a)jboss.org" wrote : | | If you want to add classloader specific ClassFileTransformers to the | | BaseClassLoaderPolicy api that's ok with me. | | | Already done. | But I'm still using our Translator + adding ClassFileTransformer2Translator bridge. | What should be the order of transformation? 1) domain 2) policy Having more "exact" transformation after more "general". | protected byte[] transform(String className, byte[] byteCode, ProtectionDomain protectionDomain) throws Exception | { | byte[] result = byteCode; | | BaseClassLoaderDomain domain = getClassLoaderDomain(); | if (domain != null) | result = domain.transform(getClassLoader(), className, result, protectionDomain); | | ClassLoader classLoader = getClassLoaderUnchecked(); | if (classLoader != null) | result = TranslatorUtils.applyTranslatorsOnTransform(translators, classLoader, className, result, protectionDomain); | | return result; | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222702#4222702 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222702

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009