[JBoss JIRA] (ERT-489) LogStream and LogReader not closed properly [EBZ#513175]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-489?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston reassigned ERT-489:
---------------------------------
Assignee: Jeff Johnston
> LogStream and LogReader not closed properly [EBZ#513175]
> --------------------------------------------------------
>
> Key: ERT-489
> URL: https://issues.jboss.org/browse/ERT-489
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: Docker, bzira
>
> Created attachment 267122
> console log
> I don't know the steps to reproduce,
> I restarted several times a container from the Docker Explorer view and also tried unsuccessfully to connect using JMX, then I notice these logs in the (Hibernate??) console:
> 2017-03-06 16:51:09,320 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@71f8be7c not closed properly
> 2017-03-06 16:51:09,326 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7308249e not closed properly
> 2017-03-06 16:52:32,482 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@264466d3 not closed properly
> 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@59ddd31f not closed properly
> 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@293ef016 not closed properly
> 2017-03-06 16:54:31,468 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@74675bfa not closed properly
> 2017-03-06 16:57:11,469 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7f02296e not closed properly
> 2017-03-06 17:21:27,815 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@76f4439 not closed properly
> 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@4c912048 not closed properly
> 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@2da4958a not closed properly
> 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@5017428b not closed properly
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24140:
------------------------------------
Tests are OK on my Win10 laptop as well as on my RHEL7 VM. I suspect timeing issues, maybe related to Neon.3 move
> Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24140
> URL: https://issues.jboss.org/browse/JBIDE-24140
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.4.4.AM2
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:*
> http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 0.56 sec 5
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 15 ms 11
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments (from org.jboss.tools.jst.web.test.JstWebAllTests)
> Failing for the past 11 builds (Since #69 )
> Took 15 ms.
> add description
> Error Message
> Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9
> Stacktrace
> junit.framework.AssertionFailedError: Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:200)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:413)
> at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:409)
> at org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments(WebXMLValidationTest.java:55){code}
> {code}
> Failed
> org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig (from org.jboss.tools.jst.web.test.JstWebAllTests)
> Failing for the past 5 builds (Since Unstable#75 )
> Took 0.56 sec.
> add description
> Stacktrace
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig(WebXMLValidationTest.java:103){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23961:
------------------------------------------
The problem here is the same as in JBIDE-24083. Thus this is included in the latter.
> Server adapter: "Start/Restart in Debug" is broken for Nodejs
> -------------------------------------------------------------
>
> Key: JBIDE-23961
> URL: https://issues.jboss.org/browse/JBIDE-23961
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: debugging, nodejs, server_adapter
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: image-2017-02-16-23-30-21-709.png, jbide-23961-restart-1.png, jbide-23961-restart-2.png, server-adapter-erroneous-debugging-state.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24083:
------------------------------------------
[~jeffmaury] [~rob.stryker] any chance you could test this fix before we freeze, please?
> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
> Key: JBIDE-24083
> URL: https://issues.jboss.org/browse/JBIDE-24083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.4.AM1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: regression
> Fix For: 4.4.4.AM2
>
> Attachments: jbide-23961-restart-1.png
>
>
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24083:
------------------------------------------
[~rhopp] good catch, you're absolutely right: the bug here also caused static changes not to be displayed in the browser even though they were sync'ed over. With my fix debugging and changing html when not debugging are fixed.
> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
> Key: JBIDE-24083
> URL: https://issues.jboss.org/browse/JBIDE-24083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.4.AM1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: regression
> Fix For: 4.4.4.AM2
>
> Attachments: jbide-23961-restart-1.png
>
>
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24083:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1459 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1458)
> Debug NodeJS app is broken - Failed to connect to Standalone V8 VM
> ------------------------------------------------------------------
>
> Key: JBIDE-24083
> URL: https://issues.jboss.org/browse/JBIDE-24083
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.4.AM1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: regression
> Fix For: 4.4.4.AM2
>
> Attachments: jbide-23961-restart-1.png
>
>
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4339) DevSuite installer on Windows should ask for hostfolder details
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik updated JBDS-4339:
------------------------------------
Component/s: platform-installer
(was: installer)
> DevSuite installer on Windows should ask for hostfolder details
> ---------------------------------------------------------------
>
> Key: JBDS-4339
> URL: https://issues.jboss.org/browse/JBDS-4339
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Hardy Ferentschik
>
> Minishift/CDK allows to mount a Samba/CIFS share into the VM. This is a replacement for the current approach of using vagrant-sshfs as part of ADB/CDK 2.x.
> The vagrant-sshfs approach was password free, but for the CIFS approach we at the very least need the users Windows password. On top of this we can also allow the user to specify any share (opposed to just this home directory) as well as a custom mount point in the VM.
> The question is where and how the user specifies this information. In order to have a fully integrated solution where after the install DevStudio can be launched and the CDK adapter starting the CDK, the installer would need to ask the user for the required information and write some additional configuration data.
> Without this additional setup, the user would not have any host folders available. They can be added later by running a {code}minishift{code} command, but this would be a manual step and it might not be obvious to the user.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4339) DevSuite installer on Windows should ask for hostfolder details
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik reassigned JBDS-4339:
---------------------------------------
Assignee: Denis Golovin
> DevSuite installer on Windows should ask for hostfolder details
> ---------------------------------------------------------------
>
> Key: JBDS-4339
> URL: https://issues.jboss.org/browse/JBDS-4339
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
>
> Minishift/CDK allows to mount a Samba/CIFS share into the VM. This is a replacement for the current approach of using vagrant-sshfs as part of ADB/CDK 2.x.
> The vagrant-sshfs approach was password free, but for the CIFS approach we at the very least need the users Windows password. On top of this we can also allow the user to specify any share (opposed to just this home directory) as well as a custom mount point in the VM.
> The question is where and how the user specifies this information. In order to have a fully integrated solution where after the install DevStudio can be launched and the CDK adapter starting the CDK, the installer would need to ask the user for the required information and write some additional configuration data.
> Without this additional setup, the user would not have any host folders available. They can be added later by running a {code}minishift{code} command, but this would be a manual step and it might not be obvious to the user.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4339) DevSuite installer on Windows should ask for hostfolder details
by Hardy Ferentschik (JIRA)
Hardy Ferentschik created JBDS-4339:
---------------------------------------
Summary: DevSuite installer on Windows should ask for hostfolder details
Key: JBDS-4339
URL: https://issues.jboss.org/browse/JBDS-4339
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: installer
Reporter: Hardy Ferentschik
Minishift/CDK allows to mount a Samba/CIFS share into the VM. This is a replacement for the current approach of using vagrant-sshfs as part of ADB/CDK 2.x.
The vagrant-sshfs approach was password free, but for the CIFS approach we at the very least need the users Windows password. On top of this we can also allow the user to specify any share (opposed to just this home directory) as well as a custom mount point in the VM.
The question is where and how the user specifies this information. In order to have a fully integrated solution where after the install DevStudio can be launched and the CDK adapter starting the CDK, the installer would need to ask the user for the required information and write some additional configuration data.
Without this additional setup, the user would not have any host folders available. They can be added later by running a {code}minishift{code} command, but this would be a manual step and it might not be obvious to the user.
Thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years