[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20108:
--------------------------------
Sprint: devex #123 November 2016 (was: devex #122 October 2016)
> 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
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> 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, 5 months
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19604:
-------------------------------------
I'll look into this issue. I have a similar action in download runtimes and if it fails we abort the 'next' press. The user can then change info on the page and press next again if they want.
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Labels: openshift_v2
> Fix For: 4.4.x
>
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-19604:
-----------------------------------
Assignee: Rob Stryker (was: Andre Dietisheim)
> Save Password in New Openshift Application Wizard is annoying
> -------------------------------------------------------------
>
> Key: JBIDE-19604
> URL: https://issues.jboss.org/browse/JBIDE-19604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Environment: Linux, x86_64, Open JDK 7
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Labels: openshift_v2
> Fix For: 4.4.x
>
> Attachments: openshif-save-password.mp4
>
>
> Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23022) "Unable to initializa some runtime paths" error when detecting seam runtimes.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23022?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-23022:
-----------------------------------
Assignee: Rob Stryker
> "Unable to initializa some runtime paths" error when detecting seam runtimes.
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23022
> URL: https://issues.jboss.org/browse/JBIDE-23022
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.1.AM3
> Environment: Devstudio 10.1.0.AM3-v20160819-0530-B5800
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: LATER
>
>
> Detecting seam runtime causes "Unable to initializa some runtime paths" error. I have tried seam 2.1.2 and seam 2.3.1.Final.
> The same is happening when downloading these runtimes via runtime detection.
> There is "All runtime detectors failed to initialize jboss-seam-2.3.1.Final" message in error log. Nothing more.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23403:
-------------------------------------
Well... I have patches up to get access to jmx / gc / etc, but unfortunately it doesn't seem there are any exposed beans to monitor your deployments at all.
> As a user I need to be able to inspect the state of my EAP deployments
> ----------------------------------------------------------------------
>
> Key: JBIDE-23403
> URL: https://issues.jboss.org/browse/JBIDE-23403
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: openshift_v3, server, web_console
> Fix For: 4.4.x
>
>
> The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment.
> The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23409) Server editor should allow 'edit...' option for selected username - followup
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23409?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23409:
-------------------------------------
OK I get your meaning now. I was reading it completely backwards. I'll consider this.
> Server editor should allow 'edit...' option for selected username - followup
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23409
> URL: https://issues.jboss.org/browse/JBIDE-23409
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, server
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.0.AM2
>
> Attachments: credentials.png, runtimes.png
>
>
> Today while creating a cdk server adapter, I noticed there is a new Edit button when selecting credentials for the adapter. This was recently added here: JBIDE-23382
> I would like to propose a change to make it consistent with other things like JREs when creating a server adapter.
> So in the server editor, we used to have just Add.. and now we also have Edit...:
> !credentials.png!
> Similar thing in the New Server adapter.
> Now look at the New Runtime dialog:
> !runtimes.png!
> I think it would be nice to do it similarly, wdyt?
> Meaning, instead of Edit.. and Add.., we would simply have a button for "Credentials..." which would open the appropriate Preference page (and upon closing, you would need to update the content on the page to show any added credentials).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23466) Refactor ConnectionWrapper class for better support of mulithreading
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23466?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23466:
-------------------------------------
I looked at the code here and everything seems fine except the fireChanged. There are other small improvements you can make to make it more efficient and block for a shorter time, but there's really no problem with using synchronized because sometimes you really do need to make sure the entire method completes as a block, not just the addition or removal of one k/v pair.
My point is, switching to concurrent might actually introduce more bugs. You will probably move to concurrent and remove all teh synchronized blocks, and end up with one variable modified and the other not yet modified, ie a model in inconsistant state.
> Refactor ConnectionWrapper class for better support of mulithreading
> --------------------------------------------------------------------
>
> Key: JBIDE-23466
> URL: https://issues.jboss.org/browse/JBIDE-23466
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Dmitrii Bocharov
> Labels: openshift_v3, watcher
> Fix For: 4.4.x
>
>
> The initial discussion started here: https://github.com/jbosstools/jbosstools-openshift/pull/1359#discussion_r...
> The problem is that ConnectionWrapper contains a lot of synchronized blocks, that can be bottlenecks. We need to think about using ConcurentHashMap for projects Map or refactor the whole logic of using global variables: projects and resourceCache to make them work synchronously.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22543) Different errors when closing Central right after it was opened
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22543?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22543:
-------------------------------------
Patch looks good +1
> Different errors when closing Central right after it was opened
> ---------------------------------------------------------------
>
> Key: JBIDE-22543
> URL: https://issues.jboss.org/browse/JBIDE-22543
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.0.Final
> Environment: Devstudio 10.0.0.GA-v20160603-1025-B5510
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.2.Final
>
>
> Opening and closing central gives me two different errors:
> {noformat}
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> ... 8 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:360)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> ... 12 more
> {noformat}
> and
> {noformat:title=Failed to get connectors from RemoteProxyWizardDiscoveryStrategy}
> org.eclipse.core.runtime.CoreException: IO failure: cannot load discovery directory
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:111)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: Cancelled by user
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.checkException(FileReader.java:337)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.close(FileReader.java:287)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.readResource(WebUtil.java:101)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:91)
> ... 6 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException: Cancelled by user
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$1.checkException(FileReader.java:334)
> ... 9 more
> Caused by: org.eclipse.ecf.filetransfer.UserCancelledException: Cancelled by user
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.newUserCancelledException(AbstractRetrieveFileTransfer.java:442)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setDoneCanceled(AbstractRetrieveFileTransfer.java:472)
> at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.cancel(HttpClientRetrieveFileTransfer.java:228)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.handleTransferEvent(FileReader.java:213)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.fireTransferReceiveDataEvent(AbstractRetrieveFileTransfer.java:390)
> at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.fireTransferReceiveDataEvent(HttpClientRetrieveFileTransfer.java:1116)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.handleReceivedData(AbstractRetrieveFileTransfer.java:294)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:179)
> at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
> ... 1 more
> {noformat}
> They do not appear every time, but pretty often.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months