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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Strings Experiments...

by timfox

Your conmparison is invalid: | public void testPutString() throws Exception | { | ChannelBufferWrapper buffer = new ChannelBufferWrapper(10 * 1024); | | for (int c = 0; c < TIMES; c++) | { | long start = System.currentTimeMillis(); | | for (int i = 0; i < numberOfIteractions; i++) | { | if (i == 10000) | { | start = System.currentTimeMillis(); | } | buffer.rewind(); | buffer.putString(str + i); | } | | long spentTime = System.currentTimeMillis() - start; | | System.out.println("spentTime putString = " + spentTime); | } | | } | You are adding the integer i to the string in some of the tests. These will cause a new string and a copy. You're not doing that when you're testing with SimpleString View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211751#4211751 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211751

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Locks on MainDeployerImpl

by alesj

I guess if I just write lock the deploy and undeploy lists processing, you should be fine. | Index: deployers-impl/src/main/java/org/jboss/deployers/plugins/main/MainDeployerImpl.java | =================================================================== | --- deployers-impl/src/main/java/org/jboss/deployers/plugins/main/MainDeployerImpl.java (revision 84459) | +++ deployers-impl/src/main/java/org/jboss/deployers/plugins/main/MainDeployerImpl.java (working copy) | @@ -322,33 +322,41 @@ | @@ -623,13 +631,13 @@ | if (deployers == null) | throw new IllegalStateException("No deployers"); | | + List<DeploymentContext> undeployContexts = null; | lockWrite(); | try | { | if (shutdown.get()) | throw new IllegalStateException("The main deployer is shutdown"); | | - List<DeploymentContext> undeployContexts = null; | if (undeploy.isEmpty() == false) | { | // Undeploy in reverse order (subdeployments first) | @@ -640,21 +648,33 @@ | Collections.sort(undeployContexts, reverted); | undeploy.clear(); | } | - if (undeployContexts != null) | - { | - deployers.process(null, undeployContexts); | - } | + } | + finally | + { | + unlockWrite(); | + } | | - try | - { | - processToDeploy(); | - } | - catch (DeploymentException e) | - { | - throw new RuntimeException("Error while processing new deployments", e); | - } | + if (undeployContexts != null) | + { | + deployers.process(null, undeployContexts); | + } | | - List<DeploymentContext> deployContexts = null; | + try | + { | + processToDeploy(); | + } | + catch (DeploymentException e) | + { | + throw new RuntimeException("Error while processing new deployments", e); | + } | + | + List<DeploymentContext> deployContexts = null; | + lockWrite(); | + try | + { | + if (shutdown.get()) | + throw new IllegalStateException("The main deployer is shutdown"); | + | if (deploy.isEmpty() == false) | { | deployContexts = new ArrayList<DeploymentContext>(deploy); | @@ -662,15 +682,16 @@ | Collections.sort(deployContexts, comparator); | deploy.clear(); | } | - if (deployContexts != null) | - { | - deployers.process(deployContexts, null); | - } | } | finally | { | unlockWrite(); | } | + | + if (deployContexts != null) | + { | + deployers.process(deployContexts, null); | + } | } | | public DeploymentStage getDeploymentStage(String deploymentName) throws DeploymentException | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211731#4211731 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211731

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Ending executions API

by heiko.braun＠jboss.com

I was just looking at the ActivityExecution interface, it says: | /** view upon an {@link Execution path of execution} exposed to | * {@link ActivityBehaviour} implementations. | * | * @author Tom Baeyens | */ | public interface ActivityExecution extends OpenExecution { | However it exposes e method to end the execution which states: | /** ends this execution and all of its child executions. | * | * <p>The execution will be removed from it's parent. Potentially this can cause | * a parent execution to start executing in case this is the last concurrent | * execution for which the parent is waiting.</p> | * | * <p>This method should not be called in {@link ActivityBehaviour}s. It can be called from | * outside the process execution and in {@link ExternalActivityBehaviour}s. </p> */ | void end(); | This method should not be called in {@link ActivityBehaviour}s. Why is in the interface then? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211726#4211726 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211726

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by jbarrez

1) is the way I'm currently doing it today, but it feels like I'm doing the engine's work by doing so ... Users won't get in to trouble by using option 1, but it certainly overloads the execute method, even if you want to do something simple like adding 2 runtime variables and store the result: first fetch and 'interprete' them, add them, store them ... this is not the jbpm-way Option (2) is a viable alternative, but it's a bit error-prone and hard to debug IMO. Stateful should be the default choice then, and those who want extra performance can set the stateless option where needed So, I'm not liking any of the 2 options ... but if I had to choose, I'd choose option (2). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211725#4211725 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211725

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: history problem

by tom.baeyens＠jboss.com

good point. i didn't test history with concurrency yet. this is indeed a bug. your fix is good indeed. only, method execution.getProcessInstance() is easier then your while loop :-) i'll fix it today. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211722#4211722 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211722

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by tom.baeyens＠jboss.com

alejandro, your point is correct. when sharing a single instance, context sensitive expressions cannot be used as they were. i see two options: 1) not doing any expression resolution in the injections. only make it possible to inject the static string "${actor.sauce.preference}" in a member field. and then make expression resolution available to the delegation classes through an api method invocation. 2) create a property to specify whether a delegation is stateless or not. i'm leaning towards 1) because that is a performant default which users cannot get into trouble with. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211720#4211720 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211720

17 years, 1 month

1
0
0 / 0

[Design of JBoss Labs] - Access to this forum failed

by Repadit

I've logged in, but if I open the page http://www.jboss.org/index.html?module=bb i got only the message anonymous wrote : Cannot invoke the operation : the module threw an exception I test it with Firefox 3 and IE 7 under Windows XP... It only happens, if I'm logged in... But I can access to forums directly like http://www.jboss.org/index.html?module=bb&op=main&c=17 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211719#4211719 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211719

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Little fight over slf4j on eclipse .classpath

by jmesnil

When I updated MINA, I removed by accident the right version of slf4j. Clebert is right: we need slf4j-api-1-5-2 and its log4j wrapper to run tests with MINA inside eclipse. We should always change intellij settings when we change eclipse .classpath: there is no reason Andy shouldn't share our fun ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211714#4211714 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211714

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Locks on MainDeployerImpl

by alesj

It looks like I over did it with introducing write lock on MainDeployerImpl::process (which now creates deployment contexts). The deadlock can be seen here: - https://jira.jboss.org/jira/browse/JBAS-6529 - http://lists.jboss.org/pipermail/jboss-development/2009-February/013693.html My idea was to let others have read lock - the one's that are adding/removing on already concurrent maps, while the one's that actually process things should have a write lock. Is this really good/necessary? Or what would be the right way to have these locks? I used to have just write lock on shutdown. Which I guess could result in the same lock Brian sees if he would apply similar construct on the shutdown? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211713#4211713 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211713

17 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - TCK testcases for JCA spec 10 chapter - WorkManager

by jeff.zhang

1. WorkManager.doWork 2. WorkManager.startWork 3. WorkManager.scheduleWork Create some Work implement and run the test 4. Test for WorkListener/WorkAdapter/WorkEvent , verify it can be reached some status: workSubmit, workStarted, workAccepted, workRejected, workCompleted. Include catch some exception 5. Test ExecutionContext class, how? 6. Using Timer to periodic execution of work instance. 7. DistributableWork, do testcase as Work View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211693#4211693 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211693

17 years, 1 month

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-dev-forums February 2009