[JBoss JIRA] (JBIDE-13320) CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13320?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13320:
-----------------------------------
Fix Version/s: 3.3.2
(was: 4.0.0.CR1)
> CLONE - Execute permissions modified in merged openshift projects ("use existing") causing action hoooks to not execute
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13320
> URL: https://issues.jboss.org/browse/JBIDE-13320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Environment: Linux, Mac (NOT Windows)
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 3.3.2
>
> Attachments: hook-premissions-windows.jpg
>
>
> 1. EXEC: Create and import new app
> 2. ASSERT: execute permissions on action_hooks get resetted.
> {code}
> diff --git a/.openshift/action_hooks/build b/.openshift/action_hooks/build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/deploy b/.openshift/action_hooks/deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_deploy b/.openshift/action_hooks/post_deploy
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_start_jbosseap-6.0 b/.openshift/action_hooks/post_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/post_stop_jbosseap-6.0 b/.openshift/action_hooks/post_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build b/.openshift/action_hooks/pre_build
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_build_jbosseap-6.0 b/.openshift/action_hooks/pre_build_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_start_jbosseap-6.0 b/.openshift/action_hooks/pre_start_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/action_hooks/pre_stop_jbosseap-6.0 b/.openshift/action_hooks/pre_stop_jbosseap-6.0
> old mode 100755
> new mode 100644
> diff --git a/.openshift/cron/weekly/chronograph b/.openshift/cron/weekly/chronograph
> {code}
> 3. EXEC: publish the application to OpenShift
> Result:
> {code}
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> ...but the server is started.
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-12362) ZIpped publish over the wire sends zip file twice instead of once
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12362?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-12362:
---------------------------------------
I verified the same for JBDS 5.0.2.GA B235
> ZIpped publish over the wire sends zip file twice instead of once
> -----------------------------------------------------------------
>
> Key: JBIDE-12362
> URL: https://issues.jboss.org/browse/JBIDE-12362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: JBIDE-12362.33x.patch
>
>
> 3) An error in WTPZippedPublisher which sent the zipped archive to the remote machine TWICE unnecessarily.
> 4) Slightly enhanced API (added api, none changed or removed) to allow easier access to the deployment per-module preferences
> To reproduce, well, you'd have to use breakpoints really. Inspecting the progress monitor won't do much, because it will still look like it's sending the same file. It will be hard to tell when the first transfer has finished and the second began.
> The original commit to trunk was made over at JBIDE-12360
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13319:
-----------------------------------
Affects Version/s: 3.3.2
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2, 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13319:
-----------------------------------
Labels: (was: new_and_noteworthy)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2, 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak commented on JBIDE-13319:
----------------------------------------
This needs to be fixed in 3.3.2, the build QE recieved does not include fix for this issue: JBoss Developer Studio
Version: 5.0.2.GA
Build id: v20121213-1624-H235-GA
Build date: 20121213-1624
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2, 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13319:
-----------------------------------
Fix Version/s: 3.3.2
(was: 4.0.0.CR1)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13319:
-----------------------------------
Issue Type: Bug (was: Enhancement)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Stefan Bunciak updated JBIDE-13319:
-----------------------------------
Priority: Critical (was: Major)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 3.3.2
>
> Attachments: mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-13319:
--------------------------------------
Summary: CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
Key: JBIDE-13319
URL: https://issues.jboss.org/browse/JBIDE-13319
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.0.0.Beta2
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Fix For: 4.0.0.CR1
Attachments: mongodb22-installed.png, mongodb22.png
The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
Additionally I'm unable to embed those cartridges. I can see the following error message.
Could not embed cartridges for application myphptesting
Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.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
13 years, 4 months
[JBoss JIRA] (JBIDE-11990) When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11990?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-11990:
---------------------------------------
Verified the same for JBDS 5.0.2.GA B235 - works just as well.
> When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11990
> URL: https://issues.jboss.org/browse/JBIDE-11990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3 nightly 2012-05-24
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this is what happens:
> 1. The process keeps running on the remote host
> 2. The server is in Starting state until it reaches time out
> 3. This is where remote and local servers differ, but both behave wrongly
> 3.a - remote server: When time out is reached, server stops, but the process keeps running - you have to kill it manually
> 3.b - local server: When time out is reached, server tries to stop, but fails doing so. So you have to force stop and then it stops and the process is killed.
> The the bigger problem is with remote servers - you have no way of stopping the server other than sshing to the server and killing the process.
> In the case of local server, it is not so bad, but still after the time out the tools should be able to stop the server on first attempt.
--
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
13 years, 4 months