[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20108:
---------------------------------------
I got bad news. I cannot make it work again :(
I'm trying to connect to a remote EAP 7 server and I even deleted the server, then added the admin user as it should be added and I keep getting the authentication failure :( I will have to dig more into it.
> Cannot connect to remote server in JMX Navigator - Authentication fails
> -----------------------------------------------------------------------
>
> Key: JBIDE-20108
> URL: https://issues.jboss.org/browse/JBIDE-20108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final
>
>
> When I try to connect to a remote server via JMX Navigator, it fails on authentication:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854
> !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin
> !STACK 1
> org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> ... 7 more
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854
> !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> !STACK 0
> javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work.
> Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4175:
-------------------------------
Attachment: JBDS-4175_logs_first_half.tar.gz
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Václav Kadlčík
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, sw_to_install.txt, workspace.log
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23490:
-----------------------------------------
it is in the context of having Eclipse Openshift Tooling working with Fuse Integration Services but this use case seems to be nice for all Openshift applications that are not exposing any services.
So the idea is to provide some logic that asks you to choose a pod or uses the only one it finds.
i'm not sure when is the best, but at deployment seems great. And yes, when tryign to create a server adapter, it will be nice to list pods to be able to attach to them and not only services.
> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23208.
---------------------------------
Closing. For details, see my previous comment. There is nothing else to be checked at this point as I was the only one seeing the problem and I stopped seeing it with a new workspace.
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: connection, openshift_v3, ssl
> Fix For: 4.4.2.AM3
>
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23263) CDK docker registry is filled for an existing OpenShift 3 connection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23263?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23263.
---------------------------------
Verified in devstudio-10.2.0.GA-v20161115-0558-B6461-installer-standalone.jar
What I did:
1. Start CDK and wait for OpenShift connection to be created
2. Edit the OpenShift connection to remove the registry
3. Restart CDK in Servers view
4. Check that the registry has been added in the OpenShift connection details again
> CDK docker registry is filled for an existing OpenShift 3 connection
> --------------------------------------------------------------------
>
> Key: JBIDE-23263
> URL: https://issues.jboss.org/browse/JBIDE-23263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Labels: openshift_v3
> Fix For: 4.4.2.AM3
>
>
> If I already have an existing OpenShift 3 connection, which would have been otherwise created by starting CDK server adapter, an the connection does not have filled CDK docker registry URL, then the field for registry is still empty even after successful start of CDK server adapter. I would like to have the registry URL filled for an existing connection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23490:
------------------------------------------
[~aurelien.pupier] you're are whishing this when deploying, correct? You'd like to be able to tell the server adapter wizard what pod to use?
> Provide ability to link pods when no service is available
> ---------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22762) JMX remote call results (and others) cannot be copied using Cmd+C
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22762?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22762.
---------------------------------
Now I can copy the results using Cmd+c.
Verified in devstudio-10.2.0.GA-v20161115-0558-B6461-installer-standalone.jar
> JMX remote call results (and others) cannot be copied using Cmd+C
> ------------------------------------------------------------------
>
> Key: JBIDE-22762
> URL: https://issues.jboss.org/browse/JBIDE-22762
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> I was verifying JBIDE-22549 which was supposed to add support for Ctrl+C in JMX remote call results. This doesn't work for me on Mac. Right-click -> Copy does work though.
> What I did was:
> 1. Start EAP 7
> 2. Connect in JMX Navigator
> 3. Go to MBeans -> jboss.as -> naming
> 4. Double click the mbean
> 5. Execute jndiView
> In the result window, I am not able to copy anything using Cmd+C, but I can copy using right-click -> Copy.
> I asked [~rhopp] to try this for me on Linux. But he got stuck on failed jmx connection of his local EAP 7 server (reported here: JBIDE-22761). And then I tried a similar thing in the Properties view and it turns out that I can't copy there either. Then I asked Radim to check that and he confirmed he cannot copy from Properties view using Ctrl+C on linux.
> Then I tried some more and noticed that in some occasions I can do that:
> For example if I select the active JMX connection in JMX Navigator, go to Properties view, expand Memory and select a row, I can copy with Cmd+C. But if I select an MBean and then click a row in the Properties view, I cannot copy with Cmd+C.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-13481) When runtime is not found, ask user before adding path to list for scanning
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13481?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-13481.
---------------------------------
Works as expected. I tried all three use cases:
Search for runtimes and:
a) press cancel - no path is added and no runtime is added
b) add path is checked and press OK - path is added and runtime is added
c) add path is unchecked and press OK - path is not added, but runtime is added
Verified in devstudio-10.2.0.GA-v20161115-0558-B6461-installer-standalone.jar
> When runtime is not found, ask user before adding path to list for scanning
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13481
> URL: https://issues.jboss.org/browse/JBIDE-13481
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final
>
>
> 1. Click Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
> 2. Click Add and select a random directory without a runtime
> 3. Next window displays 'No runtime found' (as expected!)
> 4. Click Cancel
> 5. Despite no runtime being found this path has been added to the list of paths to scan.
> I can understand that some users might want to add paths despite runtimes not being found - hence current behavior. But some users might just be searching for a runtime location using trial and error and it can become frustrating to have to then select the path and click Remove.
> Could this be improved by adding a step between 4 and 5? So after clicking Cancel a message is displayed to say 'No runtime was found. Are you sure you want to add this path?' with yes/no options, where yes adds the path and no doesn't add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months