[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21746:
-----------------------------------------------
The log level can be setup in the config.ini file with the eclipse.log.level parameter. The value can be set to INFO, WARNING and ERROR. WARNING and ERROR will not write INFO messages.
However, user may want to see info, but not too much of it. I would suggest to write info in this case only if option org.jboss.tools.openshift.ui/debug is set to true. If exception is thrown then error is logged, that is good enough for non-debug mode. [~jcantrill], [~fbricon], what do you think?
> Too much info shown in log when deploying a docker image to OpenShift
> ---------------------------------------------------------------------
>
> Key: JBIDE-21746
> URL: https://issues.jboss.org/browse/JBIDE-21746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22133 at 4/8/16 2:22 PM:
------------------------------------------------------------------
I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. [~xiazhao2015] Do you?
was (Author: adietish):
I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. Do you?
> Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22133
> URL: https://issues.jboss.org/browse/JBIDE-22133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262
> Mac OS
> Reporter: Xia Zhao
> Assignee: Jeff Cantrill
> Labels: openshift_v3
>
> Get error "UnsupportedMediaType" when create project and applications from JBT on Mac
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22133 at 4/8/16 2:12 PM:
------------------------------------------------------------------
I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong. If this is the case you should experience the same using oc. Do you?
was (Author: adietish):
I suspect this to be an issue with the cloned template, not jboss tools, but I could be wrong.
> Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22133
> URL: https://issues.jboss.org/browse/JBIDE-22133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262
> Mac OS
> Reporter: Xia Zhao
> Assignee: Jeff Cantrill
> Labels: openshift_v3
>
> Get error "UnsupportedMediaType" when create project and applications from JBT on Mac
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22145:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> nio WatchService possibly causing errors / locking files on windows
> -------------------------------------------------------------------
>
> Key: JBIDE-22145
> URL: https://issues.jboss.org/browse/JBIDE-22145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Thomas Mäder
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22145:
-----------------------------------
Labels: (was: respin-b)
> nio WatchService possibly causing errors / locking files on windows
> -------------------------------------------------------------------
>
> Key: JBIDE-22145
> URL: https://issues.jboss.org/browse/JBIDE-22145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Thomas Mäder
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years