[JBoss JIRA] (JBIDE-24138) Implement queryMbeans for Jolokia
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24138?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24138:
--------------------------------
Sprint: devex #130 April 2017
Labels: new_and_noteworthy (was: )
> 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
> Assignee: Aurélien Pupier
> Labels: new_and_noteworthy
> Fix For: 4.4.4.AM3
>
>
> 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)
8 years, 11 months
[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24291:
-------------------------------------
[~aurelien.pupier] is this standard jmx? Or is this jolokia? Or is the problem common to both?
> Improve initial loading of JMX Connection tree
> ----------------------------------------------
>
> Key: JBIDE-24291
> URL: https://issues.jboss.org/browse/JBIDE-24291
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.4.AM2
> Reporter: Aurélien Pupier
>
> JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me)
> It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server.
> For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24312 at 4/25/17 6:15 PM:
-------------------------------------------------------------------
the culprit why the certificates are not found is at SSLCertificatesPreference.Item.issuedBy
The parser (at
{code}
X509CertificateParser.getIssuer(X509Certificate certificate)
{code}
is using a whole block of certificate informations that contains the serial number.
In the case of the internal *redhat.com test instance this is what gets used:
{code}
Country (C): US
State (ST): North Carolina
Serial Number: 52616C65696768Organization (O): Red Hat, Inc.
Organizational Unit (OU): Information Technology
Common Name (CN): open.paas.redhat.com
Serial Number: 5B42403732636266343933
{code}
The serial number sent by the server is always a new "random" number. This causes our lookup for existing accepted (and stored) certificates to always think we have a new certificate (prior certificates match in fingerPrint, validity but not in issuedBy.
{code:title=Item#equals}
@Override
public boolean equals(Object o) {
if(!(o instanceof Item)) return false;
Item other = (Item)o;
return Objects.equals(this.issuedBy, other.issuedBy)
&& Objects.equals(this.validity, other.validity)
&& Objects.equals(this.fingerprint, other.fingerprint);
}
{code}
was (Author: adietish):
the culprit why the certificates are not found is at SSLCertificatesPreference.Item.issuedBy
The parser (at
{code}
X509CertificateParser.getIssuer(X509Certificate certificate)
{code}
is using a whole block of certificate informations that contains the serial number.
In the case of the internal *redhat.com test instance this is what gets used:
{code}
Country (C): US
State (ST): North Carolina
Serial Number: 52616C65696768Organization (O): Red Hat, Inc.
Organizational Unit (OU): Information Technology
Common Name (CN): open.paas.redhat.com
Serial Number: 5B42403732636266343933
{code}
The serial number sent by the server is always a new "random" number. This causes our lookup for existing accepted (and stored) certificates to always think we have a new certificate (prior certificates match in fingerPrint, validity but not in issuedBy.
{code:title=Item#equals}
@Override
public boolean equals(Object o) {
if(!(o instanceof Item)) return false;
Item other = (Item)o;
return Objects.equals(this.issuedBy, other.issuedBy)
&& Objects.equals(this.validity, other.validity)
&& Objects.equals(this.fingerprint, other.fingerprint);
}
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24312:
------------------------------------------
the culprit why the certificates are not found is at SSLCertificatesPreference.Item.issuedBy
The parser (at
{code}
X509CertificateParser.getIssuer(X509Certificate certificate)
{code}
is using a whole block of certificate informations that contains the serial number.
In the case of the internal *redhat.com test instance this is what gets used:
{code}
Country (C): US
State (ST): North Carolina
Serial Number: 52616C65696768Organization (O): Red Hat, Inc.
Organizational Unit (OU): Information Technology
Common Name (CN): open.paas.redhat.com
Serial Number: 5B42403732636266343933
{code}
The serial number sent by the server is always a new "random" number. This causes our lookup for existing accepted (and stored) certificates to always think we have a new certificate (prior certificates match in fingerPrint, validity but not in issuedBy.
{code:title=Item#equals}
@Override
public boolean equals(Object o) {
if(!(o instanceof Item)) return false;
Item other = (Item)o;
return Objects.equals(this.issuedBy, other.issuedBy)
&& Objects.equals(this.validity, other.validity)
&& Objects.equals(this.fingerprint, other.fingerprint);
}
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24312 at 4/25/17 5:04 PM:
-------------------------------------------------------------------
When looking up why the ssl certificate is still unverified (in {code}
SSLCertificatesPreference.getInstance().getAllowedByCertificate(X509Certificate){code} i found out that my preferences contains lots of certificates that are identical in all fields (SHA1 Fingerprint, etc.) but differ in Serial Number
!diff-in-serial.png!
was (Author: adietish):
When looking up why the ssl certificate is still unverified (in SSLCertificatesPreference.getInstance().getAllowedByCertificate(X509Certificate) i found out that my preferences contains lots of certificates that are identical in all fields (SHA1 Fingerprint, etc.) but differ in Serial Number
!diff-in-serial.png!
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24312:
------------------------------------------
When looking up why the ssl certificate is still unverified (in SSLCertificatesPreference.getInstance().getAllowedByCertificate(X509Certificate) i found out that my preferences contains lots of certificates that are identical in all fields (SHA1 Fingerprint, etc.) but differ in Serial Number
!diff-in-serial.png!
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months