[JBoss JIRA] Created: (JBIDE-7188) JBoss Tools appears to try to start remote server
by Pete Muir (JIRA)
JBoss Tools appears to try to start remote server
-------------------------------------------------
Key: JBIDE-7188
URL: https://jira.jboss.org/browse/JBIDE-7188
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud, JBossAS
Affects Versions: 3.2.0.M2
Reporter: Pete Muir
When I choose "Run On Server" I get this exception -- looks like JBoss Tools is trying to start the remote instance, and fails (nb remote instance is already running)
java.lang.IllegalArgumentException: classToLaunch cannot be null
at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49)
at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType.actualLaunch(AbstractJBossLaunchConfigType.java:108)
at org.jboss.ide.eclipse.as.core.server.internal.launch.JBossServerStartupLaunchConfiguration.superActualLaunch(JBossServerStartupLaunchConfiguration.java:91)
at org.jboss.ide.eclipse.as.core.server.internal.launch.LocalJBossServerStartupLaunchUtil.actualLaunch(LocalJBossServerStartupLaunchUtil.java:376)
at org.jboss.ide.eclipse.as.core.server.internal.launch.JBossServerStartupLaunchConfiguration.actualLaunch(JBossServerStartupLaunchConfiguration.java:86)
at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType.launch(AbstractJBossLaunchConfigType.java:70)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:695)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3209)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3159)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:359)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-7415) New Seam Web Project fails on JBDS4 B1, Seam 2.2.1.CR2 and AS6M5
by Burr Sutter (JIRA)
New Seam Web Project fails on JBDS4 B1, Seam 2.2.1.CR2 and AS6M5
----------------------------------------------------------------
Key: JBIDE-7415
URL: https://jira.jboss.org/browse/JBIDE-7415
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Win 7 64-bit (32-bit JVM)
Reporter: Burr Sutter
Priority: Critical
See video
Stack trace
13:30:07,495 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to PreReal: name=vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/MySeamProject.war state=PostClassLoader mode=Manual requiredState=PreReal: org.jboss.deployers.spi.DeploymentException: java.lang.ClassNotFoundException: org.jboss.seam.servlet.SeamResourceServlet from BaseClassLoader@1aa7971{vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/MySeamProject.war}
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:117) [:6.0.0.20100911-M5]
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.internalDeploy(ResteasyScannerDeployer.java:62) [:6.0.0.20100911-M5]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1]
at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.ClassNotFoundException: org.jboss.seam.servlet.SeamResourceServlet from BaseClassLoader@1aa7971{vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/MySeamProject.war}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480) [jboss-classloader.jar:2.2.0.Alpha8]
at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_20]
at org.jboss.resteasy.integration.deployers.ResteasyScannerDeployer.deployApplicationClass(ResteasyScannerDeployer.java:113) [:6.0.0.20100911-M5]
... 40 more
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-7399) ZipException: ZipFile closed
by Vitali Yemialyanchyk (JIRA)
ZipException: ZipFile closed
----------------------------
Key: JBIDE-7399
URL: https://jira.jboss.org/browse/JBIDE-7399
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 3.2.0.Beta2
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
java.util.zip.ZipException: ZipFile closed
at java.util.zip.ZipFile.ensureOpenOrZipException(Unknown Source)
at java.util.zip.ZipFile.access$1100(Unknown Source)
at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source)
at java.util.zip.ZipFile$1.fill(Unknown Source)
at java.util.zip.InflaterInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:215)
at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:97)
at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78)
at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildren(RegularObjectImpl.java:58)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:120)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:127)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:127)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:127)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:127)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parseInPackages(LibraryScanner.java:127)
at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parse(LibraryScanner.java:111)
at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.process(ClassPathMonitor.java:98)
at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:98)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-7608) JBossServerConnection (jmx related) executing long-running task after server status changed to 'started'
by Rob Stryker (JIRA)
JBossServerConnection (jmx related) executing long-running task after server status changed to 'started'
--------------------------------------------------------------------------------------------------------
Key: JBIDE-7608
URL: https://jira.jboss.org/browse/JBIDE-7608
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.2.0.Beta2
The proper class sets server to started, but the job doesn't complete because setting server state to started fires off to all server state listeners. Setting state to started (and executing all server state listeners) does not have a progress monitor at all. So when the JBossServerConnection class tries to access jmx on a remote server that doesn't have it enabled, it simply seems to freeze the "starting server" portion.
Answer is to have the JBossServerConnection class (which listens to server state) to fire off its own job rather than executing in the current thread. This also allows the user to see what's going on.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7058) Be able to install VPE without xulrunner
by Max Andersen (JIRA)
Be able to install VPE without xulrunner
----------------------------------------
Key: JBIDE-7058
URL: https://jira.jboss.org/browse/JBIDE-7058
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Reporter: Max Andersen
Assignee: Maxim Areshkau
Priority: Critical
Fix For: 3.2.0.Beta
It should be possible for users of platforms where xulrunner is not available to install jboss tools.
Today it forcefully requires a native xulrunner component - that should be optional (but installed if it is there).
This is to make users of i.e. windows 64bit and osx 64 bit use all the other features with the better/faster 64bit vms.
--
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, 4 months