[JBoss JIRA] (JBDS-3780) Lots of errors of type HTTP Server 'Gateway Timeout'
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-3780?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-3780:
-----------------------------------------
I saw these errors especially on Tuesday and Wednesday. I'm in Brno office so I'm in the internal network and I saw it when I was
* installing a new software (JBDS-IS) manually in JBDS
* installing a new software using automated installation using p2 director (locally and also on jenkins)
Unfortunately, this is not always reproducible :( Today I didn't get such error. Probably it was a temporary problem. I just wanted to let you know that some people have such problem.
> Lots of errors of type HTTP Server 'Gateway Timeout'
> ----------------------------------------------------
>
> Key: JBDS-3780
> URL: https://issues.jboss.org/browse/JBDS-3780
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 9.1.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Nick Boldt
> Priority: Critical
>
> Recently I'm often getting lots of errors such as
> {code}
> !ENTRY org.eclipse.equinox.p2.transport.ecf 4 1002 2016-04-06 21:42:20.140
> !MESSAGE HTTP Server 'Gateway Timeout': https://devstudio.redhat.com/9.0/development/updates/compositeArtifacts.xml
> !STACK 1
> org.eclipse.ecf.filetransfer.BrowseFileTransferException: HttpComponents connection error response code 504.
> at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:289)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 1 org.eclipse.ecf.identity 4 0 2016-04-06 21:42:20.142
> !MESSAGE HttpComponents connection error response code 504.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22128:
-------------------------------------------
{quote}
my problem was I didn't create the helloworld-msa project in the 1st place
{quote}
Exactly, so really it would have helped to get something like:" Project helloworld-msa does not exist. Unable to import resources", instead of: "Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"", which suggests (at least to me), that there is a project _helloworld-msa_, but I don't have permissions to modify it.
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22128:
-------------------------------------
my problem was I didn't create the helloworld-msa project in the 1st place
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22143) Changes done to OpenShift application are thrown away when debugging is enabled
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22143?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22143:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22143
> URL: https://issues.jboss.org/browse/JBIDE-22143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years