[JBoss JIRA] (JBDS-3780) Lots of errors of type HTTP Server 'Gateway Timeout'
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3780?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3780:
-----------------------------------
I haven't run into any serious issues for a couple of days, guess the purge did the trick.
> 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: Andrej Podhradsky
> Priority: Blocker
> Labels: respin-c
> Fix For: 9.1.0.CR1
>
>
> 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-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21857:
--------------------------------------
Hi Rob,
I don't know, for me this works reliably. Two questions:
# Are you running the exact same Java code as I do?
# Were you able to try the patched JDK I mentioned in chat?
I will get Oracle JDK 1.8.0u31 and try to reproduce. If I can't let's do a telco this afternoon (my afternoon ;-))
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-648) Improve the tracking of BPMN2 issues
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky resolved JBTIS-648.
-------------------------------------
Resolution: Done
Hi Max, thx for your suggestions. Currently, we are following option b)
We will see if it is the right process. Then, we can close this issue.
> Improve the tracking of BPMN2 issues
> ------------------------------------
>
> Key: JBTIS-648
> URL: https://issues.jboss.org/browse/JBTIS-648
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: BPMN2
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Priority: Critical
>
> Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/).
> Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles.
> In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla).
> Other solutions could be
> * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ)
> * or move the whole project to the Jira JBoss Tools
> What do you think? Do you have any ideas how to improve the process?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3795) Cant start CDK
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3795?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3795:
-------------------------------------
I saw the same yesterday, but before I could test more, I started getting this other error during start>
{code}
==> default: Error pulling image (v3.1.1.6) from registry.access.redhat.com/openshift3/ose-haproxy-router, Server error: 404 trying to fetch remote history for b4802aef71cdc3c84813e7a9ad14c3d070dfe6981599ac0a17a3f5b46d60cb3c
{code}
Cc: [~rob.stryker]
> Cant start CDK
> --------------
>
> Key: JBDS-3795
> URL: https://issues.jboss.org/browse/JBDS-3795
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Labels: havoc, respin-c
> Fix For: 9.1.0.CR1
>
> Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 => 2222 (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection timeout. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default:
> default: Vagrant insecure key detected. Vagrant will automatically replace
> default: this with a newly generated keypair for better security.
> default:
> default: Inserting generated public key within guest...
> default: Removing insecure key from the guest if it's present...
> default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22129.
---------------------------------
Ok, in that case verified in JBDS 9.1.0.GA build B495.
> Watches should not try to reconnect when a project has been deleted
> -------------------------------------------------------------------
>
> Key: JBIDE-22129
> URL: https://issues.jboss.org/browse/JBIDE-22129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user).
> After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying.
> Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years