[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-18366.
------------------------------------
Resolution: Done
Let's mark this issue as resolved for 4.2.1.CR1 but [~mmalina], please reopen it if it's not fixed by JBIDE-18267.
> Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18366
> URL: https://issues.jboss.org/browse/JBIDE-18366
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log:
> {code}
> INFO: JBoss MSC version 1.1.5.Final-redhat-1
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start
> INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
> Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292)
> at org.jboss.as.server.ServerService.boot(ServerService.java:346)
> at org.jboss.as.server.ServerService.boot(ServerService.java:321)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
> at java.lang.Thread.run(Thread.java:695)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
> ... 11 more
> Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot
> FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18844) Fix min table size for platformList
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18844?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18844:
----------------------------------------
[~gercan], is it fixed in new Thym (JBIDE-18868)? Can we resolve the issue for 4.2.1.CR1 (respin-a)?
> Fix min table size for platformList
> -----------------------------------
>
> Key: JBIDE-18844
> URL: https://issues.jboss.org/browse/JBIDE-18844
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.2.1.CR1
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
> Attachments: hybrid-tooling.png
>
>
> Table with platforms is too small. Please see attached screenshot.
> On mac the ios platform is hidden and user needs to scroll.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17818:
----------------------------------------
+1 to push it to 4.2.x
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy, respin-a
> Fix For: 4.2.1.CR1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18591) "Error while JSDT ClassPath changed" exception occurs when creating thym project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18591?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-18591.
------------------------------------
Resolution: Done
It should be resolved by JBIDE-18868
> "Error while JSDT ClassPath changed" exception occurs when creating thym project
> --------------------------------------------------------------------------------
>
> Key: JBIDE-18591
> URL: https://issues.jboss.org/browse/JBIDE-18591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> Error message is "Error while JSDT ClassPath changed." and stacktrace is:
> {code}org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications.
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1322)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1376)
> at tern.eclipse.ide.core.TernNature.configure(TernNature.java:59)
> at tern.eclipse.ide.internal.core.IDETernProject.ensureNatureIsConfigured(IDETernProject.java:817)
> at tern.eclipse.ide.internal.core.IDETernProject.<init>(IDETernProject.java:111)
> at tern.eclipse.ide.internal.core.IDETernProject.getTernProject(IDETernProject.java:134)
> at tern.eclipse.ide.core.TernCorePlugin.getTernProject(TernCorePlugin.java:99)
> at tern.eclipse.ide.jsdt.internal.JSDTClassPathManager.elementChanged(JSDTClassPathManager.java:67)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1591)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1581)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1416)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1392)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1945)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.wst.jsdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:807)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:2992)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:3023)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.setUpJavaScriptProject(HybridProjectCreator.java:135)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createProject(HybridProjectCreator.java:104)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createBasicTemplatedProject(HybridProjectCreator.java:78)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard$1.run(NewHybridProjectWizard.java:91)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.performFinish(NewHybridProjectWizard.java:103)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:697)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:682)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:636)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18877) New Canvas wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18877:
---------------------------------------------
Summary: New Canvas wizard for HTML5 palette
Key: JBIDE-18877
URL: https://issues.jboss.org/browse/JBIDE-18877
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.2.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3208:
----------------------------------
OK, then we just need [~maxandersen] and [~mickael_istria] and [~fbricon] to +1 this and we can proceed.
I'm thinking that the eclipse.org mirrors we have currently in /updates/requirements/ [1] could move to /\{quality\}/updates/requirements/ since we only need them to build target platforms and when target platforms are Final and moved to /static/, we could purge them based on their quality (eg., snapshots & development can go away after GA; but we should keep the R builds that go into our target platforms.
[1] http://download.jboss.org/jbosstools/updates/requirements/
*BIG DISCLAIMER* re: implementing an aggressive cleanup policy for these mirrored upstream requirements: if a mirrored upstream snapshot or dev milestone is used in a GA or a version of the IS we support through Central, we need to keep it much longer.
Therefore:
* /\{mars,9.0}/
** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
*** /*updates*/
**** /\{*requirements*, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
*** /*builds*/
**** /<job-name>/
***** /<build-version = B123, B124, B125...>/
I'd also be happy renaming "requirements" to "upstream" or "mirrors" if people prefer that term.
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> {code}
> download.jboss.org
> <earlyaccess,updates,discovery>/mars
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/mars/stable is a pointer back into updates/mars)
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> and
> {code}
> devstudio.redhat.com
> <earlyaccess,updates,discovery>/9.0
> /snapshots
> /staging
> /development
> /stable (updates/9.0/stable is a pointer back into updates/9.0)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last 2 builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months