[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance not using port 8443 for connection url
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-24438:
------------------------------------
Summary: Server adapter: JMX connection is not working for OpenShift instance not using port 8443 for connection url (was: Server adapter: JMX connection is not working for OpenShift instance )
> Server adapter: JMX connection is not working for OpenShift instance not using port 8443 for connection url
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
> Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> 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: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24526) eap 7.1 missing runtime wizard fragment
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24526?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24526:
---------------------------------------
Indeed, I can see what Ondrej is reporting in devstudio-11.0.0.AM1-v20170601-1252-B198-installer-standalone.jar :(
Now downloading a nightly build and will verify there.
> eap 7.1 missing runtime wizard fragment
> ----------------------------------------
>
> Key: JBIDE-24526
> URL: https://issues.jboss.org/browse/JBIDE-24526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> The eap 7.1 runtime fragment is missing when accessed / created via properties -> runtime -> new (the wtp runtime wizard, not jbt's runtime detection)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24538) Wildfly 9 and above need remote+http protocol for jmx
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24538?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24538:
---------------------------------------
[~rob.stryker], I'm not sure where you saw this. I've never seen it. I tried EAP 7.0 now with devstudio 11.0.0.AM1 B198 (devstudio-11.0.0.AM1-v20170601-1252-B198-installer-standalone.jar) where it shouldn't be fixed yet and I don't see any such warning in the console view or workspace log or anywhere. Also, I don't see this format used anywhere - server console uses a different format. Can you help me reproduce this?
Also, do I need a special setup? I had a local server, then I tried a remote server using a local host.
> Wildfly 9 and above need remote+http protocol for jmx
> -----------------------------------------------------
>
> Key: JBIDE-24538
> URL: https://issues.jboss.org/browse/JBIDE-24538
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> When connecting to a wf9 / wf10 / wf11 or associated eap's via jmx, console spits out the following:
> {code}
> Jun 05, 2017 4:16:34 PM org.jboss.remotingjmx.Util warnDeprecated
> WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24541) Exception in LocalFilesystemController.deleteResource
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24541?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24541.
---------------------------------
I just checked that this fix is included in master. I don't really have a way to verify right now.
> Exception in LocalFilesystemController.deleteResource
> -----------------------------------------------------
>
> Key: JBIDE-24541
> URL: https://issues.jboss.org/browse/JBIDE-24541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to delete module Module[mee-web,org.eclipse.jst.jee.server:mee-web]
> java.lang.Exception: Could not delete /opt/keycloak-2.2.1.Final/standalone/deployments/mee-web-1.0-SNAPSHOT.war. May be locked by another process.
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.LocalFilesystemController.deleteResource(LocalFilesystemController.java:259)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:477)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:338)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> The reporter(s) left the following comment(s):
> --- Anonymous wrote on 0a66: ---
> Windows 10. Eclipse running as Administrator.
> --- Anonymous wrote on 0d9a: ---
> I have already deleted the folder manually myself as well as from Servers. This was what I did: Did Eclipse clean and build (not Wildfly 10 clean), and ran debug my other projects.
> Not sure when you guys delete it; apparently it seems on the next run. I will not be checking this url, please email me on the results, thank you!
> --- andremoriya wrote on ae18: ---
> I Cleaned the wildfly server and run
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.2.v20170113-2113 |
> | org.eclipse.ltk.core.refactoring | 3.7.0.v20160419-0705 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.8.0.v20160518-1817 | 3.8.0.v20160518-1817 |
> | org.eclipse.m2e.wtp.overlay | 1.3.2.20161026-1738 | 1.3.2.20161026-1738 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.9.0.v201610211907 |
> | org.jboss.ide.eclipse.archives.webtools | 3.2.4.v20170329-2126 | 3.2.4.v20170329-2126 |
> | org.jboss.ide.eclipse.as.ui | 3.2.2.v20161121-2100 | 3.2.4.v20170329-2126 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.2.v20161006-2008 | 3.2.4.v20170505-1406 |
> Operating Systems:
> | Linux | 3.2.0 | 4.10.10.fc25 |
> | MacOSX | 10.10.5 | 10.12.5 |
> | Windows | 6.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/580a0315e4b081752d6... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24491 at 6/13/17 6:34 AM:
-------------------------------------------------------------------
[~rob.stryker] I dont see where this issue isnt "directed" (see description and comments above):
1) it's not a matter of the current code "not working". It's a matter of lacking functionality: If you launch the cdk via the server adapter while you *DONT* have a connection to it in Eclipse, the server adapter will create everything for you just fine. Assuming that you *DONT* use the cdk server adapter or already have a connection to it in Eclipse when you launch the cdk via the adapter, then the registry is of course not set up for you. You have to look it up as indicated in the description. For this case we'd like to have Eclipse allowing you to look it up, sparing you from getting to the command line.
2) see 1)
3) this is not a bug, this is a missing piece of enhancement for our CDK tooling in Eclipse.
was (Author: adietish):
[~rob.stryker]:
1) it's not a matter of the current code "not working". It's a matter of lacking functionality: If you launch the cdk via the server adapter while you *DONT* have a connection to it in Eclipse, the server adapter will create everything for you just fine. Assuming that you *DONT* use the cdk server adapter or already have a connection to it in Eclipse when you launch the cdk via the adapter, then the registry is of course not set up for you. You have to look it up as indicated in the description. For this case we'd like to have Eclipse allowing you to look it up, sparing you from getting to the command line.
2) see 1)
3) this is not a bug, this is a missing piece of enhancement for our CDK tooling in Eclipse.
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24491:
------------------------------------------
[~rob.stryker]:
1) it's not a matter of the current code "not working". It's a matter of lacking functionality: If you launch the cdk via the server adapter while you *DONT* have a connection to it in Eclipse, the server adapter will create everything for you just fine. Assuming that you *DONT* use the cdk server adapter or already have a connection to it in Eclipse when you launch the cdk via the adapter, then the registry is of course not set up for you. You have to look it up as indicated in the description. For this case we'd like to have Eclipse allowing you to look it up, sparing you from getting to the command line.
2) see 1)
3) this is not a bug, this is a missing piece of enhancement for our CDK tooling in Eclipse.
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-24555:
----------------------------------
Summary: Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest (was: Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest)
> Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24555
> URL: https://issues.jboss.org/browse/JBIDE-24555
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.5.0.AM1
>
>
> *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [Search for Test Failure JIRAs in JBIDE 4.5.0.AM1 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 0.22 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 1.1 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-24555:
----------------------------------
Description:
*2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[Search for Test Failure JIRAs in JBIDE 4.5.0.AM1 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
-----
{code}
All Failed Tests
Test Name
Duration
Age
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
{code}
{code}
Failed
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
Failing for the past 194 builds (Since #1 )
Took 0.22 sec.
Error Message
Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
Stacktrace
junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
{code}
Failed
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
Failing for the past 194 builds (Since #1 )
Took 1.1 sec.
Error Message
Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
Stacktrace
junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
was:
*2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[Search for Test Failure JIRAs in JBIDE 4.5.0.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
-----
{code}
All Failed Tests
Test Name
Duration
Age
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
{code}
{code}
Failed
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
Failing for the past 194 builds (Since #1 )
Took 0.22 sec.
Error Message
Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
Stacktrace
junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
{code}
Failed
org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
Failing for the past 194 builds (Since #1 )
Took 1.1 sec.
Error Message
Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
Stacktrace
junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
> Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24555
> URL: https://issues.jboss.org/browse/JBIDE-24555
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.5.0.AM1
>
>
> *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [Search for Test Failure JIRAs in JBIDE 4.5.0.AM1 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 0.22 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 1.1 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-24555:
----------------------------------
Reporter: Martin Malina (was: Nick Boldt)
> Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24555
> URL: https://issues.jboss.org/browse/JBIDE-24555
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.5.0.AM1
>
>
> *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [Search for Test Failure JIRAs in JBIDE 4.5.0.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 0.22 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 1.1 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-24555:
----------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.5.0.AM2)
> Test Failure(s) in JBIDE 4.5.0.AM2 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24555
> URL: https://issues.jboss.org/browse/JBIDE-24555
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.5.0.AM1
>
>
> *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [Search for Test Failure JIRAs in JBIDE 4.5.0.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 0.22 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 1.1 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months