[JBoss JIRA] (JBIDE-23785) WF11 server adapter needed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23785?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23785:
---------------------------------------
I prefer JIRA comments to PR comments, so I am commenting here.
Here's the PR:
https://github.com/jbosstools/jbosstools-server/pull/481
{quote}
I created a PR for maintenance with some fixes.
{quote}
Where is the PR for maintenance? I cannot find it - there is only one open PR for this repo and it's this one.
Anyway, I tried this PR again - installed into Neon.2, but I feel dirty about it. I started the server and then got this:
Unable to retrieve a list of remote deployment scanners for server WildFly 11
{code}
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.execute(WildFly11Manager.java:390)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11ManagerService.execute(WildFly11ManagerService.java:171)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:295)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:293)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:164)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:124)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:114)
at org.jboss.ide.eclipse.as.ui.dialogs.ModifyDeploymentScannerIntervalDialog$DeploymentScannerUIServerStartedListener$1.run(ModifyDeploymentScannerIntervalDialog.java:82)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
at org.jboss.ide.eclipse.as.internal.management.wf11.WildFly11Manager.execute(WildFly11Manager.java:379)
... 11 more
Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:121)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 13 more
Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Server rejected authentication
DIGEST-MD5: javax.security.sasl.SaslException: Server rejected authentication
at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:108)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:395)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:465)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:427)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:415)
at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:177)
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:113)
... 23 more
Suppressed: javax.security.sasl.SaslException: Server rejected authentication
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:716)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:560)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
Suppressed: javax.security.sasl.SaslException: Server rejected authentication
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:716)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:560)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
{code}
This is a basic local server, so I think it should just work, no?
Also, same as last time I tried, server stop fails. There is not much detail, just:
Server WildFly 11 failed to stop.
At least now I can select the WF 11 runtime when creating a dynamic web project - this didn't work last time I tried. And I can deploy the project on the server just fine.
> WF11 server adapter needed
> ---------------------------
>
> Key: JBIDE-23785
> URL: https://issues.jboss.org/browse/JBIDE-23785
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> WF 11 server adapter needed. THis may require a new set of jars (or may not). Current test of wf11 nightly build seems to work with mgmt, no significant changes, but that can break.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24138) Implement queryMbeans for Jolokia
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24138?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-24138:
------------------------------------
Comment: was deleted
(was: I recommend to review and merge this PR before starting work on this feature)
> Implement queryMbeans for Jolokia
> ---------------------------------
>
> Key: JBIDE-24138
> URL: https://issues.jboss.org/browse/JBIDE-24138
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jmx
> Affects Versions: 4.4.4.AM1
> Reporter: Aurélien Pupier
>
> Currently JolokiaMBeanServerConnection.queryMBeans is not implemented
> @Override
> public Set<ObjectInstance> queryMBeans(ObjectName name, QueryExp query) throws IOException {
> // TODO Auto-generated method stub
> return null;
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1069) Missing org.jboss.tools.ws.feature in JBTIS-TP
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1069:
----------------------------------------
Summary: Missing org.jboss.tools.ws.feature in JBTIS-TP
Key: JBTIS-1069
URL: https://issues.jboss.org/browse/JBTIS-1069
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: target-platform
Affects Versions: 4.4.2.Final-TP
Reporter: Andrej Podhradsky
I noticed that the feature
{code}
org.jboss.tools.ws.feature
{code}
was removed in 4.4.2.Final-TP but it was available in 4.4.1.Final-TP. Is there any reason for that?
--
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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4339:
-------------------------------------
As a simple MVP solution I would suggest to start with just home directory sharing. Installer can ask for local user name and password during cdk install in modal dialog and then execute required minishift command. When MVP works, we can think about extending this solution and could add additional step between confirmation where components are selected for installation and installation progress page.
> 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
> Fix For: 10.4.0.GA
>
>
> 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 Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4339:
--------------------------------
Fix Version/s: 10.4.0.GA
> 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
> Fix For: 10.4.0.GA
>
>
> 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] (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:
-------------------------------------
Fix Version/s: 4.5.0.AM1
> 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, 4.5.0.AM1
>
> 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:
------------------------------------------
merged into jbosstools-4.4.x and cherry-picked into master
> 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, 4.5.0.AM1
>
> 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] (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 updated ERT-489:
------------------------------
Sprint: devex #129 March 2017
> 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