[JBoss JIRA] (JBIDE-24643) NoStackTrace in StandardFileSystemPublishController.markModulePublished
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24643?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24643:
-----------------------------------------
{quote}1) Is it the openshift server adapter using the StandardFileSystemPublishController / WildFlyFileSystemPublishController? Or was this some unrelated publish?
{quote}
I have no idea what are the StandardFileSystemPublishController / WildFlyFileSystemPublishController
{quote}
2) The WildFlyFileSystemPublishController is primarily targeted to as/wf/eap. If Openshift is using this class, then it probably needs to subclass further or make other customizations. It's not written for openshift use.
{quote}
might worth asking Eclipse OpenShift team then: [~jeffmaury] perhaps?
{quote}
3) A grep on the openshift repo doesn't show any dependency, subclass, or reference, to WildFlyFileSystemPublishController. This leads me to believe the description is not as simple as described. It's likely this has nothing at all to do with openshift server adapter.
{quote}
if I remember well (8 months ago...), I did only the mentioned task and the was the error reporting tool which was reporting this stacktrace.
{quote}
4) The stack trace here is 8 months old. It last matched on Oct 4, 2016, so I'm wondering why an 8 month old stack is being used. In fact, the stack trace changed further just 1 day after this patch.
{quote}
so we can hope that it is fixed.
{quote}
5) An error should only exist here if getFilesystemController().deleteResource(remote, monitor) is returning a status object that is not "ok". In this case, it is appropriate for an error to be logged.{quote}
would be nice to improve log and specify which module/resource cannot be deleted in this case.
> NoStackTrace in StandardFileSystemPublishController.markModulePublished
> -----------------------------------------------------------------------
>
> Key: JBIDE-24643
> URL: https://issues.jboss.org/browse/JBIDE-24643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
>
> The following problem was reported via the automated error reporting:
> Message: Unable to delete module
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.markModulePublished(StandardFileSystemPublishController.java:584)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:482)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:332)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> The reporter(s) left the following comment(s):
> --- Aurélien Pupier wrote on a317: ---
> I created an openShift Server Adapter for a FIS project
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |
> | org.eclipse.jdt.debug | 3.10.0.v20160418-1524 | 3.10.1.v20160811-0441 |
> | org.eclipse.jface | 3.12.1.v20160923-1528 | 3.12.1.v20160923-1528 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.core.ui | 1.7.1.20161104-1805 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.wtp | 1.3.1.20160831-1005 | 1.3.1.20160831-1005 |
> | org.eclipse.m2e.wtp.overlay | 1.3.0.20160530-2310 | 1.3.2.20161026-1738 |
> | org.eclipse.swt | 3.105.2.v20161122-0613 | 3.105.2.v20161122-0613 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.10.0.v201705172051 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.ide.eclipse.as.ui | 3.2.3.v20170123-1748 | 3.2.3.v20170123-1748 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.3.0.v20170606-1714 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.jst.web.kb | 3.8.3.v20161214-1634 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.openshift.core | 3.3.3.v20170405-1252 | 3.3.3.v20170405-1252 |
> Operating Systems:
> | Linux | 2.6.32.13 | 4.11.7 |
> | MacOSX | 10.10.5 | 10.12.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a218b3e4b0fe642b1... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24643) NoStackTrace in StandardFileSystemPublishController.markModulePublished
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24643?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24643:
-------------------------------------
[~aurelien.pupier] Some questions here:
1) Is it the openshift server adapter using the StandardFileSystemPublishController / WildFlyFileSystemPublishController? Or was this some unrelated publish?
2) The WildFlyFileSystemPublishController is primarily targeted to as/wf/eap. If Openshift is using this class, then it probably needs to subclass further or make other customizations. It's not written for openshift use.
3) A grep on the openshift repo doesn't show any dependency, subclass, or reference, to WildFlyFileSystemPublishController. This leads me to believe the description is not as simple as described. It's likely this has nothing at all to do with openshift server adapter.
4) The stack trace here is 8 months old. It last matched on Oct 4, 2016, so I'm wondering why an 8 month old stack is being used. In fact, the stack trace changed further just 1 day after this patch.
5) An error should only exist here if getFilesystemController().deleteResource(remote, monitor) is returning a status object that is not "ok". In this case, it is appropriate for an error to be logged.
[~aurelien.pupier] is there any additional info you can provide to explain why this is a bug? Are you certain the error is caused by the given server and not a wf / eap server hanging around? Can you confirm that openshift is using the WildFlyFileSystemPublishController in some fashion?
If there's a bug I'd be glad to fix it, but I cannot be expected to know how everyone is extending my code without a proper usecase here.
> NoStackTrace in StandardFileSystemPublishController.markModulePublished
> -----------------------------------------------------------------------
>
> Key: JBIDE-24643
> URL: https://issues.jboss.org/browse/JBIDE-24643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
>
> The following problem was reported via the automated error reporting:
> Message: Unable to delete module
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.markModulePublished(StandardFileSystemPublishController.java:584)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:482)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:332)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> The reporter(s) left the following comment(s):
> --- Aurélien Pupier wrote on a317: ---
> I created an openShift Server Adapter for a FIS project
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |
> | org.eclipse.jdt.debug | 3.10.0.v20160418-1524 | 3.10.1.v20160811-0441 |
> | org.eclipse.jface | 3.12.1.v20160923-1528 | 3.12.1.v20160923-1528 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.core.ui | 1.7.1.20161104-1805 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.wtp | 1.3.1.20160831-1005 | 1.3.1.20160831-1005 |
> | org.eclipse.m2e.wtp.overlay | 1.3.0.20160530-2310 | 1.3.2.20161026-1738 |
> | org.eclipse.swt | 3.105.2.v20161122-0613 | 3.105.2.v20161122-0613 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.10.0.v201705172051 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.ide.eclipse.as.ui | 3.2.3.v20170123-1748 | 3.2.3.v20170123-1748 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.3.0.v20170606-1714 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.jst.web.kb | 3.8.3.v20161214-1634 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.openshift.core | 3.3.3.v20170405-1252 | 3.3.3.v20170405-1252 |
> Operating Systems:
> | Linux | 2.6.32.13 | 4.11.7 |
> | MacOSX | 10.10.5 | 10.12.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a218b3e4b0fe642b1... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24565) Prepare shell scripts for setup/install cdk 3 on jenkins
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24565?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24565:
----------------------------------
Sprint: devex #134 Jun 2017
> Prepare shell scripts for setup/install cdk 3 on jenkins
> --------------------------------------------------------
>
> Key: JBIDE-24565
> URL: https://issues.jboss.org/browse/JBIDE-24565
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.5.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.5.0.AM2
>
>
> To avoid having job full of "execute shell" build steps that configures cdk3 for integration tests It would be cleaner solution to have some set of scripts that:
> * clean up old cdk/minishift instances
> * download and install/configure cdk/minishift
> * stop/delete existing cdk/minishift instance
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4410:
-----------------------------------
Assignee: Denis Golovin
> DevSuite 1.4 Installer indicate download size during choice selection
> ---------------------------------------------------------------------
>
> Key: JBDS-4410
> URL: https://issues.jboss.org/browse/JBDS-4410
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.0.0.AM2
>
>
> During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late.
> The two use cases I see for this:
> # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later.
> # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V.
> Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4410:
--------------------------------
Fix Version/s: 11.0.0.AM2
> DevSuite 1.4 Installer indicate download size during choice selection
> ---------------------------------------------------------------------
>
> Key: JBDS-4410
> URL: https://issues.jboss.org/browse/JBDS-4410
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Environment: DevSuite 1.4 installer, Windows 10 Pro/64
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 11.0.0.AM2
>
>
> During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late.
> The two use cases I see for this:
> # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later.
> # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V.
> Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24643) NoStackTrace in StandardFileSystemPublishController.markModulePublished
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24643?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24643:
----------------------------------------
Assignee: Dmitrii Bocharov
> NoStackTrace in StandardFileSystemPublishController.markModulePublished
> -----------------------------------------------------------------------
>
> Key: JBIDE-24643
> URL: https://issues.jboss.org/browse/JBIDE-24643
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
>
> The following problem was reported via the automated error reporting:
> Message: Unable to delete module
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.markModulePublished(StandardFileSystemPublishController.java:584)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:482)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:332)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> The reporter(s) left the following comment(s):
> --- Aurélien Pupier wrote on a317: ---
> I created an openShift Server Adapter for a FIS project
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |
> | org.eclipse.jdt.debug | 3.10.0.v20160418-1524 | 3.10.1.v20160811-0441 |
> | org.eclipse.jface | 3.12.1.v20160923-1528 | 3.12.1.v20160923-1528 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.core.ui | 1.7.1.20161104-1805 | 1.7.1.20161104-1805 |
> | org.eclipse.m2e.wtp | 1.3.1.20160831-1005 | 1.3.1.20160831-1005 |
> | org.eclipse.m2e.wtp.overlay | 1.3.0.20160530-2310 | 1.3.2.20161026-1738 |
> | org.eclipse.swt | 3.105.2.v20161122-0613 | 3.105.2.v20161122-0613 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.10.0.v201705172051 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.ide.eclipse.as.ui | 3.2.3.v20170123-1748 | 3.2.3.v20170123-1748 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.3.0.v20170606-1714 |
> | org.jboss.tools.common.el.core | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.common.validation | 3.8.4.v20170316-1803 | 3.8.4.v20170316-1803 |
> | org.jboss.tools.jst.web.kb | 3.8.3.v20161214-1634 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.openshift.core | 3.3.3.v20170405-1252 | 3.3.3.v20170405-1252 |
> Operating Systems:
> | Linux | 2.6.32.13 | 4.11.7 |
> | MacOSX | 10.10.5 | 10.12.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/57a218b3e4b0fe642b1... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months