March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9044) Merge managedbeans subsystem into ee subsystem

by David Lloyd (JIRA)

Merge managedbeans subsystem into ee subsystem ---------------------------------------------- Key: JBAS-9044 URL: https://issues.jboss.org/browse/JBAS-9044 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 There is no reason that the managedbeans subsystem needs to be external anymore. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9037) Hang in org.jboss.as.test.embedded.demos.ejb3.SingletonBeanTestCase

by Carlo de Wolf (JIRA)

Hang in org.jboss.as.test.embedded.demos.ejb3.SingletonBeanTestCase ------------------------------------------------------------------- Key: JBAS-9037 URL: https://issues.jboss.org/browse/JBAS-9037 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Environment: dirty 2902c003a90a3c59291e5109ed59360e1137fe5a Reporter: Carlo de Wolf Priority: Critical Fix For: 7.0.0.Beta2 Attachments: jstack.txt AS 7 hangs while trying to deploy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
16
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2241) Reimplement clustered sfsb using single cache instance for all deployments

by Paul Ferraro (JIRA)

Reimplement clustered sfsb using single cache instance for all deployments -------------------------------------------------------------------------- Key: EJBTHREE-2241 URL: https://issues.jboss.org/browse/EJBTHREE-2241 Project: EJB 3.0 Issue Type: Bug Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: TBD AS 7 To workaround ISPN-658, we should store all sfsbs for all applications (with the same cache name) within a single cache instance, using a composite key that includes the deployment name and bean ID. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8432) Clean up stale/unused XSD and XML files

by David Lloyd (JIRA)

Clean up stale/unused XSD and XML files --------------------------------------- Key: JBAS-8432 URL: https://jira.jboss.org/browse/JBAS-8432 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: David Lloyd Fix For: 7.0.0.M1 There are files whose validity is suspect. Don't worry about needing it later; the revisioning system will remember it forever! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-8980) Implement vendor-specific global JNDI context

by David Lloyd (JIRA)

Implement vendor-specific global JNDI context --------------------------------------------- Key: JBAS-8980 URL: https://issues.jboss.org/browse/JBAS-8980 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Name it "java:jboss" or "java:jbossas" or "java:appserver" or something. It should be implemented similarly to java:global in that it is appserver-wide. In the future with app client support, there may be a unique "java:global" per app client. In this case the new context probably would still be a appserver-wide. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9000) Multiple "xalan" are present and other JSFUnit problems

by David Lloyd (JIRA)

Multiple "xalan" are present and other JSFUnit problems ------------------------------------------------------- Key: JBAS-9000 URL: https://issues.jboss.org/browse/JBAS-9000 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: Stan Silvert Priority: Critical Fix For: 7.0.0.Beta2 The org.apache.xalan and org.apache.xerces modules are defined as: {noformat} <module-def name="org.apache.xalan"> <maven-resource group="org.apache.xalan" artifact="serializer"/> <maven-resource group="org.apache.xalan" artifact="xalan"/> </module-def> <module-def name="org.apache.xerces"> <maven-resource group="xerces" artifact="xercesImpl"/> </module-def> {noformat} however we also have: {noformat} <module-def name="org.jboss.jsfunit.core"> <maven-resource group="commons-codec" artifact="commons-codec"/> <maven-resource group="commons-collections" artifact="commons-collections"/> <maven-resource group="commons-io" artifact="commons-io"/> <maven-resource group="commons-lang" artifact="commons-lang"/> <maven-resource group="commons-logging" artifact="commons-logging"/> <maven-resource group="net.sourceforge.cssparser" artifact="cssparser"/> <maven-resource group="net.sourceforge.htmlunit" artifact="htmlunit"/> <maven-resource group="net.sourceforge.htmlunit" artifact="htmlunit-core-js"/> <maven-resource group="net.sourceforge.nekohtml" artifact="nekohtml"/> <maven-resource group="org.apache.httpcomponents" artifact="httpclient"/> <maven-resource group="org.apache.httpcomponents" artifact="httpcore"/> <maven-resource group="org.apache.httpcomponents" artifact="httpmime"/> <maven-resource group="org.apache.james" artifact="apache-mime4j"/> <maven-resource group="org.jboss.jsfunit" artifact="jboss-jsfunit-core"/> <maven-resource group="org.w3c.css" artifact="sac"/> <maven-resource group="xalan" artifact="xalan"/> <maven-resource group="xalan" artifact="serializer"/> <maven-resource group="xerces" artifact="xercesImpl"/> <maven-resource group="xml-apis" artifact="xml-apis"/> </module-def> {noformat} JSFUnit should be using external modules, plus dependencies, for: # xalan (use the existing xalan module; ban xalan:xalan) # xerces (use existing module) # xml APIs (use existing modules, ban xml-apis:xml-apis) # commons-codec (add new org.apache.commons.codec module) # commons-collections (") # commons-io (") # commons-lang (") # commons-logging (use existing org.apache.commons.logging module, ban commons-logging:commons-logging) # htmlunit (a single new net.sourceforge.htmlunit module for the two artifacts) # nekohtml (add new net.sourceforge.nekohtml module) # httpcomponents (a single new org.apache.httpcomponents module will suffice) # james (add new org.apache.james module) # sac (add new org.w3c.css.sac module) Also any non-essential dependencies should be removed, if any exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-8908) AS6 ZipException now seen in AS7

by Stan Silvert (JIRA)

AS6 ZipException now seen in AS7 -------------------------------- Key: JBAS-8908 URL: https://issues.jboss.org/browse/JBAS-8908 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: 7.0.0.Alpha2 Reporter: Stan Silvert Assignee: John Bailey Priority: Blocker Attachments: mojarra2.0-notbundled.war We have the exact same problem in AS7 as was shown in JBAS-8024. I'm attaching a small WAR that reproduces the problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8864) cannot scp war archive to remote AS6

by Andre Dietisheim (JIRA)

cannot scp war archive to remote AS6 ------------------------------------ Key: JBAS-8864 URL: https://issues.jboss.org/browse/JBAS-8864 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Andre Dietisheim I try to deploy a war to a jboss AS6 that runs on a ec2 instance. I therefore scp it directly to the deploy folder. I then see a deployment exception in the server log, that occurs before the scp is completely finished: 2011-02-10 06:20:33,010 WARN [org.jboss.profileservice.deployment.hotdeploy.HDScanner] (HDScanner) Failed to add deployment: vfs:///opt/jboss-as6/server/default/deploy/gwt-helloworld.war: org.jboss.deployers.spi.DeploymentException: Failed to mount archive: "/opt/jboss-as6/server/default/deploy/gwt-helloworld.war" at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.mountArchive(AbstractVFSArchiveStructureDeployer.java:132) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.determineStructure(AbstractVFSArchiveStructureDeployer.java:55) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:197) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:222) [:2.2.0.GA] at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1106) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:417) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:367) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:277) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.addDeployment(MainDeployerPlugin.java:77) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.addDeployment(ProfileControllerContext.java:133) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:221) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [:1.6.0_20] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) [:1.6.0_20] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) [:1.6.0_20] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [:1.6.0_20] at java.util.zip.ZipFile.<init>(ZipFile.java:131) [:1.6.0_20] at java.util.jar.JarFile.<init>(JarFile.java:150) [:1.6.0_20] at java.util.jar.JarFile.<init>(JarFile.java:114) [:1.6.0_20] at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:94) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:80) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.VFS.mountZip(VFS.java:428) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.VFS.mountZip(VFS.java:454) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.util.automount.Automounter$RegistryEntry.mount(Automounter.java:237) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.util.automount.Automounter$RegistryEntry.access$000(Automounter.java:208) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.util.automount.Automounter.mount(Automounter.java:117) [jboss-vfs.jar:3.0.0.GA] at org.jboss.vfs.util.automount.Automounter.mount(Automounter.java:77) [jboss-vfs.jar:3.0.0.GA] at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.performMount(AbstractVFSArchiveStructureDeployer.java:145) [:2.2.0.GA] at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.mountArchive(AbstractVFSArchiveStructureDeployer.java:128) [:2.2.0.GA] ... 31 more As soon as my scp transfers is finished, I get back to the admin-console and wait to see if my war was picked as web application. It is not. I dont see any further scanner activity in the server log. I then touch the war and check the web-apps in the admin-console again. No reaction. There's is also no scanner activity in the server log. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
15
0 / 0

[JBoss JIRA] Created: (JBAS-8664) ConcurrentModificationException on startup with IBK jdk

by alaisi alaisi (JIRA)

ConcurrentModificationException on startup with IBK jdk ------------------------------------------------------- Key: JBAS-8664 URL: https://jira.jboss.org/browse/JBAS-8664 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.CR1 Environment: JBossAS [6.0.0.20101110-CR1 "Neo"] Java version: 1.6.0,IBM Corporation Java Runtime: Java(TM) SE Runtime Environment (build jvmwi3260sr5ifx-20090821_41076) Java VM: IBM J9 VM 2.4,IBM Corporation OS-System: Windows XP 5.1 build 2600 Service Pack 3,x86 Reporter: alaisi alaisi Assignee: Ales Justin Starting AS 6 CR1 with IBM JDK fails with ConcurrentModificationException when installing deployers/metadata-deployer-jboss-beans.xml. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-9046) Problem with CXF POMs

by David Lloyd (JIRA)

Problem with CXF POMs --------------------- Key: JBAS-9046 URL: https://issues.jboss.org/browse/JBAS-9046 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Reporter: David Lloyd Assignee: Alessio Soldano Fix For: 7.0.0.Beta2 A dependency is declared twice in the root pom.xml with different parameters: [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.as:jboss-as-build:pom:7.0.0.Beta2-SNAPSHOT [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.cxf:cxf-rt-ws-security:jar -> duplicate declaration of version ${version.org.apache.cxf} @ org.jboss.as:jboss-as-parent:7.0.0.Beta2-SNAPSHOT, /home/david/src/java/as7/jboss-as/pom.xml, line 1417, column 25 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.as:jboss-as-osgi-configadmin:bundle:7.0.0.Beta2-SNAPSHOT [WARNING] The expression ${artifactId} is deprecated. Please use ${project.artifactId} instead. [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.as:jboss-as-parent:pom:7.0.0.Beta2-SNAPSHOT [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.cxf:cxf-rt-ws-security:jar -> duplicate declaration of version ${version.org.apache.cxf} @ line 1417, column 25 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
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 March 2011