September 2008 - jboss-dev-forums

[Design the new POJO MicroContainer] - Re: Concurrent (un)deployment

by adrian＠jboss.org

I changed the title of this thread so it is easier to find for future reference. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176767#4176767 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176767

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NPE in DeployersImpl

by adrian＠jboss.org

This is really this issue: https://jira.jboss.org/jira/browse/JBAS-5326 A simple fix for the current case is to just check the DeploymentControllerContext is not null, i.e. some other thread already won the race and undeployed it. What is really required (as discussed with Ales in Slovenia) is that there is a lock where we don't try to (un)deploy when somebody else is already doing stuff (with a timeout on the lock to trap broken/deadlocked deployment code). This code already exists within the MC controller, but there's no timeout which would mean shutdown would wait forever in the case that some deployment/undeployment callback does not return. Similar issues exist in JBoss-4.x so there's nothing new in this problem, it just remains unresolved in JBoss5 at the moment (but at least in JBoss5 it is fixable since the deployers, jmx and pojo all share the same controller model). It also needs testing/extending for this feature: https://jira.jboss.org/jira/browse/JBMICROCONT-327 e.g. allowing groups of unrelated dependencies to run in parallel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176765#4176765 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176765

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NPE in DeployersImpl

by alesj

It looks like some sort of synch issue: | if (deploy != null && deploy.isEmpty() == false) | { | // Create the controller contexts | for (DeploymentContext context : deploy) | { | checkShutdown(); | | DeploymentControllerContext deploymentControllerContext = new DeploymentControllerContext(context, this); | (A) context.getTransientAttachments().addAttachment(ControllerContext.class, deploymentControllerContext); | try | { | controller.install(deploymentControllerContext); | context.setState(DeploymentState.DEPLOYING); | log.debug("Deploying " + context.getName()); | if (scopeBuilder != null) | context.getTransientAttachments().addAttachment(ScopeBuilder.class, scopeBuilder); | if (repository != null) | context.getTransientAttachments().addAttachment(MutableMetaDataRepository.class, repository); | } | catch (Throwable t) | { | // Set the error on the parent | context.setState(DeploymentState.ERROR); | context.setProblem(t); | // Set the children to not deployed | setState(context, DeploymentState.UNDEPLOYED, DeploymentState.DEPLOYING); | } | } | | // Go through the states in order | ControllerStateModel states = controller.getStates(); | for (ControllerState state : states) | { | for (DeploymentContext context : deploy) | { | DeploymentControllerContext deploymentControllerContext = context.getTransientAttachments().getAttachment(ControllerContext.class.getName(), DeploymentControllerContext.class); | (B) ControllerState current = deploymentControllerContext.getState(); | The last line here is the 621 line in DeployerImpl. It looks like some other process 'cleaned' out the context between from (A) to (B) marks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176757#4176757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176757

17 years, 6 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Removing SFSB in HttpSessionListener

by pete.muir＠jboss.org

"brian" wrote : If the Seam guys can provide any input on when they do and don't want notifications, that would be great. From JBAS-5778, it seems a sessionDestroyed() callback on undeploy is not good; any other cases I should know about? Seam uses the sessionDestroyed callback to implement session cleanup. This includes going through and calling destroy on all objects in the session (which leads to the SFSB's remove method being called unless you explicitly ask it not to). As an undeploy does this anyway, I think you are right. I can't immediately see any other cases. Also, it's worth noting that in JBoss 5 we have the ability to automatically insert classes into a Seam apps classpath, allowing us to plugin alternative behaviour - this might be helpful here (Seam currently doesn't provide for plugability here, but it could if needed). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176755#4176755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176755

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - NPE in DeployersImpl

by wolfc

After some deployment errors because of EJB3 deployment failures. I shutdown AS and get: java.lang.NullPointerException | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:621) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812) | at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:587) At least it shouldn't give a NPE. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176754#4176754 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176754

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: The PostgreSQL Issue

by alex.guizar＠jboss.com

I just found evidence that the leaked connections can certainly be related to the growing number of processes. anonymous wrote : The PostgreSQL server uses one process per connection so you should provide for at least as many processes as allowed connections, in addition to what you need for the rest of your system. This is usually not a problem but if you run several servers on one machine things might get tight. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176751#4176751 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176751

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise

by tom.baeyens＠jboss.com

anonymous wrote : i would guess the whole purpose of an appserver is to take care of making a global transaction out of XA transactional resources, no ? even if we would use different DSs. managing a global/distributed transaction is the app server's business indeed, except that (1) some databases such as HSQL and (correct me if I'm wrong) MySQL do not provide XA data sources and (2) the EJB timer service's support for 2PC relies on its underlying data source, which affects the EntitySchedulerService. JMS's 2PC support does not rely on the underlying data source's XA capability and therefore the JmsMessageService is unaffected. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176750#4176750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176750

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: The PostgreSQL Issue

by alex.guizar＠jboss.com

anonymous wrote : Another concern is that the number of postgresql processes is increasing unexpectedly to over 100 This is probably related to connection pooling. See the comments on JBPM-1131. I cannot tell whether the leaked connections are causing PostgreSQL to fork new processes, but is definitely a starting point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176748#4176748 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176748

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Multiple 1PC resources in enterprise

by alex.guizar＠jboss.com

anonymous wrote : on the migration to ejb3: i don't think that is appropriate on jBPM 3. we can consider this on jBPM 4. +3.1415926 ejb3 is definitely a proposal for jbpm 4. I volunteer for that. anonymous wrote : i would guess the whole purpose of an appserver is to take care of making a global transaction out of XA transactional resources, no ? even if we would use different DSs. managing a global/distributed transaction is the app server's business indeed, except that (1) some databases such as HSQL and (correct me if I'm wrong) MySQL do not provide XA data sources and (2) the EJB timer service's support for 2PC relies on its underlying data source, which affects the EntitySchedulerService. JMS's 2PC support does not rely on the underlying data source's XA capability and therefore the JmsMessageService is unaffected. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176743#4176743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176743

17 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Facelets scanning for .taglib.xml is broken in trunk

by pete.muir＠jboss.org

iradix, why don't you write a blog about getting Seam working in JBoss 5 and include the gotchas like this... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176742#4176742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176742

17 years, 6 months

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 September 2008