[JBoss JIRA] (JBIDE-10318) EJB jar projects are deployed as exploded jars in war/WEB-INF/lib
by Mike Mosiewicz (Created) (JIRA)
EJB jar projects are deployed as exploded jars in war/WEB-INF/lib
-----------------------------------------------------------------
Key: JBIDE-10318
URL: https://issues.jboss.org/browse/JBIDE-10318
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Reporter: Mike Mosiewicz
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M4
Following up https://issues.sonatype.org/browse/MECLIPSEWTP-181.
Web Fragment projects are deployed as exploded jars in AS7 instead of zipped archives (probably other AS'es too). This leads to a deployment failure :
{noformat}
10:11:40,572 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "web.war"
10:11:40,600 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."web.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."web.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "web.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: failed to process "/home/fbricon/Dev/servers/jboss-as-web-7.0.2.Final/standalone/deployments/web.war/WEB-INF/lib/fragment.jar"
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:118)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: failed to process "/home/fbricon/Dev/servers/jboss-as-web-7.0.2.Final/standalone/deployments/web.war/WEB-INF/lib/fragment.jar"
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:173)
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createResourceRoots(WarStructureDeploymentProcessor.java:151)
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.deploy(WarStructureDeploymentProcessor.java:112)
... 6 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [:1.6.0_26]
at java.util.zip.ZipFile.<init>(ZipFile.java:127) [:1.6.0_26]
at java.util.jar.JarFile.<init>(JarFile.java:135) [:1.6.0_26]
at java.util.jar.JarFile.<init>(JarFile.java:99) [:1.6.0_26]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:95)
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:81)
at org.jboss.vfs.VFS.mountZip(VFS.java:408)
at org.jboss.vfs.VFS.mountZip(VFS.java:434)
at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:168)
... 8 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10325) Error logged when doing Run As > Run on Server on AS 7.0.2
by Fred Bricon (Created) (JIRA)
Error logged when doing Run As > Run on Server on AS 7.0.2
----------------------------------------------------------
Key: JBIDE-10325
URL: https://issues.jboss.org/browse/JBIDE-10325
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M5
When doing Run As > Run on server on a web project, after selecting an AS 7.0.2 instance, an error is caught and logged :
{noformat}
!ENTRY org.jboss.ide.eclipse.as.ui 4 0 2011-12-02 22:08:06.603
!MESSAGE Could not acquire the management service for this JBoss installation
!STACK 0
java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.getChild(ModelValue.java:108)
at org.jboss.dmr.ModelNode.get(ModelNode.java:798)
at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getDeploymentNames(AS71Manager.java:335)
at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.hasDeployment(AS71Manager.java:328)
at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.getDeploymentStateSafe(AS71Manager.java:189)
at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.getDeploymentState(JBoss71ManagerService.java:79)
at org.jboss.ide.eclipse.as.core.server.v7.management.JBoss7ManagerServiceProxy.getDeploymentState(JBoss7ManagerServiceProxy.java:59)
at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.waitJBoss7(JBTWebLaunchableClient.java:112)
at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.wait(JBTWebLaunchableClient.java:100)
at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient.launch2(JBTWebLaunchableClient.java:80)
at org.jboss.ide.eclipse.as.ui.launch.JBTWebLaunchableClient$1.run(JBTWebLaunchableClient.java:72)
{noformat}
The server response in AS71Manager.getDeploymentNames contains an array of war names, but doing response.get(RESULT) throws the IAE.
The error is then caught and logged in JBTWebLaunchableClient.waitJBoss7 under a misleading message : "Could not acquire the management service for this JBoss installation"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10340) Duplicate service name: as70 and as71 management services
by Rob Stryker (Created) (JIRA)
Duplicate service name: as70 and as71 management services
---------------------------------------------------------
Key: JBIDE-10340
URL: https://issues.jboss.org/browse/JBIDE-10340
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.M5
Error log shows the following:
!MESSAGE [SCR] Found components with duplicated names! Details:
Component1 : Component[
name = org.jboss.ide.eclipse.as.management.as7.service
activate = activate
deactivate = deactivate
modified =
configuration-policy = optional
factory = null
autoenable = true
immediate = true
implementation = org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService
state = Unsatisfied
properties = {as.version=710.beta1}
serviceFactory = false
serviceInterface = [org.jboss.ide.eclipse.as.core.server.v7.management.IJBoss7ManagerService]
references = null
located in bundle = org.jboss.ide.eclipse.as.management.as71_2.3.0.qualifier [821]
]
Component2: Component[
name = org.jboss.ide.eclipse.as.management.as7.service
activate = activate
deactivate = deactivate
modified =
configuration-policy = optional
factory = null
autoenable = true
immediate = true
implementation = org.jboss.ide.eclipse.as.internal.management.as7.JBoss7ManagerService
state = Unsatisfied
properties = {as.version=700}
serviceFactory = false
serviceInterface = [org.jboss.ide.eclipse.as.core.server.v7.management.IJBoss7ManagerService]
references = null
located in bundle = org.jboss.ide.eclipse.as.management.as7_2.3.0.qualifier [819]
]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10284) JBoss AS 7 quickstarts and JBoss AS 7.1
by Snjezana Peco (Created) (JIRA)
JBoss AS 7 quickstarts and JBoss AS 7.1
---------------------------------------
Key: JBIDE-10284
URL: https://issues.jboss.org/browse/JBIDE-10284
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 3.3.0.M4
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 3.3.0.M5
I have tested JBoss AS 7 Quickstarts using JBoss AS 7.1. They are all deployed and started correctly.
M2e 1.0.100 seems to not update the Maven configuration automatically. Now, the Project Example engine updates the Maven configuration after importing a project example of the maven and mavenArchetype type.
I have updated JBoss AS 7 Quickstarts declarations in the project examples xml file so that they are valid for the JBoss AS 7.0/7.1 runtime.
The downloadId element is still showing JBoss AS 7.0.2 because it is the latest stable JBoss AS 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months