[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
Description:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 8.0:
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
*New* connector for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
*Beta1*
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
*CR1*
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
*CR1 or GA, TBD*
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
was:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
Proposed *new* connectors for JBDS 8.0:
* SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
*New* connector for JBDS 7.1:
* Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
*Beta1*
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
* pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
* testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
*CR1*
* VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
* eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
*CR1 or GA, TBD*
* gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
* springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
These are currently unchanged since December when we released JBDS 6.0.0:
* findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
Additionally (Target Platform):
* swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
* mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
* fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
See comments below for latest site URLs.
[1] https://github.com/jbosstools/jbosstools-locus/
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
[3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> *New* connector for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> *CR1 or GA, TBD*
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2719:
----------------------------------
This should be fixed now - I've added the not-so-optional org.springframework.ide.eclipse.ajdt.feature, and all its many dependencies, to these URLs (once the build finishes - see JBDS-2808, JBDS-2802):
* Spring 3.4 mirror: http://download.jboss.org/jbosstools/updates/requirements/springide/3.4.0...
* JBoss Central TP site (4.1.x): http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...
* JBoss Central TP site (4.2.x): http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.4...
To test it, fire up Eclipse or JBDS and point it at this discovery site to install the newer version of the Spring IDE connector, using these vmargs in eclipse.ini or jbdevstudio.ini:
{code}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/jbosstools-directory.xml \
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/
{code}
or
{code}
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/devstudio-directory.xml \
-Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
{code}
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15831) Server side errors while creating most of the scalable app. on Openshift Enterprise
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-15831.
--------------------------------------
Resolution: Rejected
REJECTED since there's nothing we can do about it, server-side error
> Server side errors while creating most of the scalable app. on Openshift Enterprise
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15831
> URL: https://issues.jboss.org/browse/JBIDE-15831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.x
>
> Attachments: gateway-timeout.png
>
>
> Most of the application while creating process of application show dialog with server error 504 (Gateway timeout), or server error 503 (service unavailable).
> !gateway-timeout.png!
> Altough, application in cloud is created, can be correctly showed in browser, in JBDS / JBT (tested in both) shows dialog with given error
> "Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout" or "Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com"
> This happens only with Openshift Enterprise. Openshift Online works fine.
> Eclipse log for HTTP error 504
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:176)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:83)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
> Eclipse log for HTTP error 503
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:155)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:79)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":null,"field":null,"severity":"error","text":"error adding app record test-test.itos.redhat.com"}],"status":"service_unavailable","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.2"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15831) Server side errors while creating most of the scalable app. on Openshift Enterprise
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15831:
-------------------------------------
Fix Version/s: 4.1.1.CR1
(was: 4.2.x)
> Server side errors while creating most of the scalable app. on Openshift Enterprise
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15831
> URL: https://issues.jboss.org/browse/JBIDE-15831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: gateway-timeout.png
>
>
> Most of the application while creating process of application show dialog with server error 504 (Gateway timeout), or server error 503 (service unavailable).
> !gateway-timeout.png!
> Altough, application in cloud is created, can be correctly showed in browser, in JBDS / JBT (tested in both) shows dialog with given error
> "Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout" or "Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com"
> This happens only with Openshift Enterprise. Openshift Online works fine.
> Eclipse log for HTTP error 504
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:176)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:83)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: Connection to https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: Gateway Timeout
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
> Eclipse log for HTTP error 503
> {code}
> com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...: error adding app record test-test.itos.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:136)
> at com.openshift.internal.client.RestService.request(RestService.java:115)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:159)
> at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:357)
> at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:155)
> at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:79)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":null,"field":null,"severity":"error","text":"error adding app record test-test.itos.redhat.com"}],"status":"service_unavailable","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.2"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 7 more
> Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: https://console.itos.redhat.com/broker/rest/domains/test/applications?inc...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> ... 11 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15895:
-----------------------------------
Component/s: browsersim
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Fix For: 4.1.1.CR1
>
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15895?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15895:
-----------------------------------
Component/s: upstream
(was: browsersim)
> Cordova API not working when added widget from jQuery Mobile palette
> --------------------------------------------------------------------
>
> Key: JBIDE-15895
> URL: https://issues.jboss.org/browse/JBIDE-15895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Reporter: Vlado Pakan
> Fix For: 4.1.1.CR1
>
>
> 1. Create Mobile Hybrid Project
> 2. Add Accelerometer testing page as described on phonegap wep page
> 3. Run Project on CordovaSim and/or Emulator and/or Android device
> 4. Open Acceleromer page
> ASSERT: App is displaying data from Accelerometer
> 5. Open index.html page add some widget from jQuery Mobile pallete and save
> 6. Repeat step 3. and 4.
> ERROR: App is not displaying data from Accelerometer. Event DeviceReady is not fired
> When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added
> {noformat}
> <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script>
> {noformat}
> and it seems is somehow breaking Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15880) openshift-java-client: provide its own lib specific timeout that may be set via system properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15880?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-15880.
------------------------------------
closing since nothing for QE to verify
> openshift-java-client: provide its own lib specific timeout that may be set via system properties
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15880
> URL: https://issues.jboss.org/browse/JBIDE-15880
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.CR1
>
>
> client timeouts when talking to OpenShift are unfortunaltey still a topic and cause errors (JBIDE-15835, JBIDE-15831) when OpenShift is installed on systems with poor performance. We should thus provide a client-lib specific default timeout that a user may override by setting it in the system properties.
> The timeout-setting order would thus then be:
> 1) specific operation timeout (ex. JBT is currently using a specific creation timeout)
> 2) client-lib default timeout (which may be set by a system property)
> 3) HttpUrlConnection default timeout (jdk timeout: -Dsun.net.client.defaultConnectTimeout=600000)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months