June 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6937) Bad deployment scan order?

by Ondrej Žižka (JIRA)

Bad deployment scan order? -------------------------- Key: JBAS-6937 URL: https://jira.jboss.org/jira/browse/JBAS-6937 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ondrej Žižka (18:14:46) ozizka: emuckenhuber: I've noticed one interesting thing. AS 5 deployment scanner first scans what's new and then what was removed. Shouldn't it be the opposite way? (18:20:34) emuckenhuber: ozizka: well it first scans for removal and then for additions - where do you see that ? (18:20:47) ozizka: I've tried it this way: (18:21:18) ozizka: It scans recursively, so I've created an exploded ear directory, only without the .ear suffix. (18:21:28) ozizka: So AS scanned, found the .war inside this dir, (18:21:34) ozizka: and deployed it. (18:21:49) ozizka: Then I renamed the directory - added the .ear suffix, (18:22:01) ozizka: so what should happen IMO is first undeploying WAR, (18:22:11) ozizka: and then deploying newly found exploded EAR (18:22:24) ozizka: I know it's not usual use case :) (18:22:45) ozizka: But instead, the WAR is reported to be DOWN (in EmbJopr) (18:23:15) ozizka: and ear appears, but is DOWN too (18:24:22) ozizka: When I invoke the Start operation on the ear, everything gets to normal, that is, EAR UP, standalone WAR disappears and Embedded WAR appears and is UP 18:25 (18:26:02) ozizka: emuckenhuber: And to add why I think that deployment is done first is this: (18:26:02) ozizka: java.lang.IllegalStateException: jboss.web.deployment:war=/hellothere-inEAR is already installed. (18:26:19) ozizka: that happens after the rename -- 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

17 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-7001) Create a stand-alone JBossWeb integration project

by Carlo de Wolf (JIRA)

Create a stand-alone JBossWeb integration project ------------------------------------------------- Key: JBAS-7001 URL: https://jira.jboss.org/jira/browse/JBAS-7001 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf Create a stand-alone integration implementation of Tomcat and VDF usable in AS, Embedded and other runtimes based on Bootstrap. The working title is 'Spider'. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-530) Look at using refids instead of properties to refer to thirdparty jars in the dist build.

by Paul Gier (JIRA)

Look at using refids instead of properties to refer to thirdparty jars in the dist build. ----------------------------------------------------------------------------------------- Key: JBBUILD-530 URL: https://jira.jboss.org/jira/browse/JBBUILD-530 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server (Phase 3) Currently the AS distribution build uses properties set by the maven ant tasks to access the various thirdparty dependencies. It might be better to use refids since this will cause the build to immediately fail when one is expected but not found. -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBID-127) Release JBoss Identity Federation Stack 1.0.0.alpha3

by Anil Saldhana (JIRA)

Release JBoss Identity Federation Stack 1.0.0.alpha3 ---------------------------------------------------- Key: JBID-127 URL: https://jira.jboss.org/jira/browse/JBID-127 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.alpha3 -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-92) Expose partition name as a @ManagementProperty

by Andrew Lee Rubinger (JIRA)

Expose partition name as a @ManagementProperty ---------------------------------------------- Key: JBBOOT-92 URL: https://jira.jboss.org/jira/browse/JBBOOT-92 Project: JBoss Bootstrap Issue Type: Feature Request Components: legacy Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Requested by Brian for inclusion into EAP -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2115) Changing import / globals not considered a change

by Kris Verlaenen (JIRA)

Changing import / globals not considered a change ------------------------------------------------- Key: JBRULES-2115 URL: https://jira.jboss.org/jira/browse/JBRULES-2115 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: FUTURE When changing the imports or globals inside the properties dialog for split constraints or the event wait constraint, the editor is not aware of these changes. As a result, if you only change the imports or globals in your process, the editor will not pick up the change and you won't be able to save the process. Steps: 1. Create a new rules flow file using the "RuleFlow file" wizard. 2. Add an Event Wait and an End node. Create connections between them. 3. Save the file. Open the rf file in another editor (such as vi). Analyze the structure. 4. From the event wait node's properties, open the constraints -> global section. Add "global String testStr" 5. Try to save the file, which thinks it hasn't changed. Open the rf file in another editor (such as vi). Notice that the global variable is missing from the file. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBBOOT-85) Undeploy services/deployments on shutdown of server

by jaikiran pai (JIRA)

Undeploy services/deployments on shutdown of server --------------------------------------------------- Key: JBBOOT-85 URL: https://jira.jboss.org/jira/browse/JBBOOT-85 Project: JBoss Bootstrap Issue Type: Task Components: impl-as Affects Versions: 0.1.2 Reporter: jaikiran pai Assignee: Andrew Lee Rubinger Creating this task based on our email discussion: Updated my JBoss AS 5_x branch to see the bootstrap changes (0.1.2 of impl-as). Looks like the way shutdown is handled in AS has now changed? I did a Ctrl+C on the command prompt and the server shutdown "immidiately". In earlier versions, i remember a shutdown would trigger undeployments of various deployments. I don't see this happening anymore. Thought you might be interested in this :) Let me know if you need more information. -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6974) Ensure the Shutdown Hook fully shuts down the Server

by Andrew Lee Rubinger (JIRA)

Ensure the Shutdown Hook fully shuts down the Server ---------------------------------------------------- Key: JBAS-6974 URL: https://jira.jboss.org/jira/browse/JBAS-6974 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-5.1.1.GA Shutdown Hook is not calling full shutdown before the process exits. For starters, there's this: if (currentState.equals(LifecycleState.STARTED) || currentState.equals(LifecycleState.STARTING)) Find other possible problems and ensure the lifecycle goes through full shutdown before the VM can terminate. -- 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

17 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBBOOT-91) Resolve dependencies in preparation for 2.0.0-alpha-1 release

by Andrew Lee Rubinger (JIRA)

Resolve dependencies in preparation for 2.0.0-alpha-1 release ------------------------------------------------------------- Key: JBBOOT-91 URL: https://jira.jboss.org/jira/browse/JBBOOT-91 Project: JBoss Bootstrap Issue Type: Task Components: build, impl-as, impl-base, impl-mc, spi, spi-as, spi-mc Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 2.0.0-alpha-1 Used to track commits for upgrades in preparation for 2.0.0-alpha-1 release of: build spi spi-mc spi-as impl-base impl-mc impl-as -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-84) Missing ServerConfig @ManagedProperty annotations

by Emanuel Muckenhuber (JIRA)

Missing ServerConfig @ManagedProperty annotations ------------------------------------------------- Key: JBBOOT-84 URL: https://jira.jboss.org/jira/browse/JBBOOT-84 Project: JBoss Bootstrap Issue Type: Bug Affects Versions: 0.1.2 Reporter: Emanuel Muckenhuber Assignee: Andrew Lee Rubinger The BasicJBossASServerConfig is missing @ManagedProperty annotations, which causes those two tests failures: > org.jboss.test.cluster.defaultcfg.profileservice.test.FarmedClusterHotDeployUnitTestCase(ClusteredProfileService).testFarmHotDeployment > org.jboss.test.deployers.test.DeploymentManagerUnitTestCase(profileservice).testHotDeploymentBeans I assume that this ServerConfig is the one used previously (which seems to have the correct annotations): https://svn.jboss.org/repos/jbossas/projects/bootstrap/tags/jboss-bootstr... -- 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

17 years, 1 month

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2009