[JBoss JIRA] (JBIDE-12351) JMX connection to servers cannot be established with IPv6
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-12351.
---------------------------------
Verified in JBDS 8.1.0.Beta1 and 9.0.0.Alpha1.
> JMX connection to servers cannot be established with IPv6
> ---------------------------------------------------------
>
> Key: JBIDE-12351
> URL: https://issues.jboss.org/browse/JBIDE-12351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 3.3.0.Final
> Environment: Fedora 17 32bit
> EAP 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: f2f2014
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log:
> {code}
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit>
> INFO: XNIO Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1
> Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 3.2.8.GA-redhat-1
> Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException
> ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3375) JBDS target platform zip contains both packed and unpacked artifacts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3375?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3375:
--------------------------------------
Frankly, I do not think that this is an issue (since we also assume that the update-site zip can be used to have a local mirror on another network). So I don't think it's worth any effort and not worth adding any additional complexity to the build.
I find it accurate to have update-site zip matching the update-site thus I'd be in favour of rejecting this issue.
> JBDS target platform zip contains both packed and unpacked artifacts
> --------------------------------------------------------------------
>
> Key: JBDS-3375
> URL: https://issues.jboss.org/browse/JBDS-3375
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Components: build, target-platform, updatesite
> Affects Versions: 9.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.0.0.Alpha2
>
>
> I've got two approaches now for including the JBDS target platform into the JBDS update site.
> a) mirror the TP site - size on disk is 328M and the increase in size to JBDS update site is about 200M
> b) wget the TP zip and unpack - size on disk after unzipping is 458M
> So... not sure which approach is more efficient given the zip is a single file to download, but it's 130M (more than 1/3rd) larger.
> If we can remove the packed (or unpacked) artifacts from the zip, we'd certainly win.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3375) JBDS target platform zip contains both packed and unpacked artifacts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3375?page=com.atlassian.jira.plugin.... ]
Mickael Istria updated JBDS-3375:
---------------------------------
Priority: Minor (was: Major)
> JBDS target platform zip contains both packed and unpacked artifacts
> --------------------------------------------------------------------
>
> Key: JBDS-3375
> URL: https://issues.jboss.org/browse/JBDS-3375
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Components: build, target-platform, updatesite
> Affects Versions: 9.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.0.0.Alpha2
>
>
> I've got two approaches now for including the JBDS target platform into the JBDS update site.
> a) mirror the TP site - size on disk is 328M and the increase in size to JBDS update site is about 200M
> b) wget the TP zip and unpack - size on disk after unzipping is 458M
> So... not sure which approach is more efficient given the zip is a single file to download, but it's 130M (more than 1/3rd) larger.
> If we can remove the packed (or unpacked) artifacts from the zip, we'd certainly win.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19397) unify/merge "Debug As... > Remote Java Application" with JMX vm list
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19397?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19397.
---------------------------------
Resolution: Done
Both child issues have been pushed, so this issue is complete. Please see https://github.com/jbosstools/jbosstools-website/pull/355 for verification steps. Please Re-open if anything conflicts or breaks as per the blog usecase.
> unify/merge "Debug As... > Remote Java Application" with JMX vm list
> --------------------------------------------------------------------
>
> Key: JBIDE-19397
> URL: https://issues.jboss.org/browse/JBIDE-19397
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> today we got jmx view that lists running hotspot jvms and allow introspection.
> We also have Debug As > Remote Java Application which I believe uses the exact same API but allow for launching a remote java app.
> It would be nice if we could make jmx view have a context menu for "connect debugger" that works in similar fashion and even better, have remote java application just use the existing model so we don't have this use of sun api's spread out over two places.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month