<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Rob,</p>
<p>thanks for that input. Can you point me to some documentation
about theses labels and what values they can have? I'm trying to
prevent a case where stuff breaks with each minor update.</p>
<p>Thomas<br>
</p>
<div class="moz-cite-prefix">Am 19.05.2016 um 16:28 schrieb Rob
Cernich:<br>
</div>
<blockquote
cite="mid:888940734.15871958.1463668114858.JavaMail.zimbra@redhat.com"
type="cite">
<div style="font-family: times new roman, new york, times, serif;
font-size: 12pt; color: #000000">
<div>Hey Thomas,<br>
</div>
<div><br>
</div>
<div>You can look at the labels for the image. There should be
a JBOSS_PRODUCT label in each image, along with something like
JBOSS_EAP_VERSION, JBOSS_DATAGRID_VERSION, etc., which has the
version.<br>
</div>
<div><br>
</div>
<div>You can also look at the image name. EAP 6.4 images are
named:<br>
</div>
<div>jboss-eap-6/eap64 - base product image (i.e. no openshift
integration)<br>
</div>
<div>jboss-eap-6/eap64-openshift - OpenShift s2i image (with
clustering and all the configuration goodies)<br>
</div>
<div><br>
</div>
<div>Hope that helps.<br>
</div>
<div>Rob<br>
</div>
<div><br>
</div>
<div><br>
</div>
<hr id="zwchr">
<blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
Hi folks,<br>
<br>
as part of a larger effort, I'm trying to establish jmx
connections to eap or wildfly servers inside Openshift/CDK. In
a prototype version, this all works well. However, I've
recently learned that the version of jmx remoting used is
tightly coupled with the wildfly/eap version (see here for an
indication: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://paste.fedoraproject.org/368295/14636462/"
target="_blank">https://paste.fedoraproject.org/368295/14636462/</a>)<br>
The problem now is to use the exact right remoting-jmx client
version for the server running inside the Openshift pod. This
has two facets:<br>
<br>
<ol>
<li>How do I know the exact version of the Widlfly or EAP
running in the pod<br>
Curently, we do some guessing of the version via the
template name of the application. Can anyone suggest a
generally applicapble and reliable way to find out what
server is running inside a pod?<br>
</li>
<li>Where do I get the appropriate client jar for that
version<br>
With local servers, we work around this problem by
dyncamically adding a classloader for the
jbossclient(-all).jar in the server runtime. The trouble
with Openshift is that we don't really have access to the
server runtime. So assuming we know the server version, we
have two options:</li>
<ol>
<li>Bundle client jars with eclipse or</li>
<li>get the client jar from the pod via rsync.<br>
</li>
</ol>
</ol>
I'd love to hear you guys chime in, since I am a bit lost
here.<br>
<br>
/Thomas<br>
<br>
_______________________________________________<br>
Devtools mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Devtools@redhat.com">Devtools@redhat.com</a><br>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/devtools">https://www.redhat.com/mailman/listinfo/devtools</a><br>
</blockquote>
<div><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>