[jira] [Assigned] (BROOKLYN-320) Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5

2016-08-04 Thread Duncan Godwin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duncan Godwin reassigned BROOKLYN-320:
--

Assignee: Duncan Godwin

> Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5
> -
>
> Key: BROOKLYN-320
> URL: https://issues.apache.org/jira/browse/BROOKLYN-320
> Project: Brooklyn
>  Issue Type: Bug
> Environment: CentOS 6.5, with nss 3.15, in aws-ec2 singapore
>Reporter: Aled Sage
>Assignee: Duncan Godwin
>
> Deploying Tomcat8Server failed (when waiting for service-up), using Brooklyn 
> 0.10.0-SNAPSHOT. This was in AWS-singapore, using 
> RightImage_CentOS_6.5_x64_v13.5.2.2_EBS (ami-42bfe910).
> TL;DR: the problem is fixed by upgrading nss (manually on the target VM).
> Looking on the VM, the file 
> {{/home/users/amp/brooklyn-managed-processes/apps/GfmrLSwE/entities/Tomcat8Server_pEKbtDGD/logs/catalina.out}}
>  had the following contents:
> {noformat}
> JmxmpAgent active at: 
> service:jmx:jmxmp://ip-10-167-0-52.ap-southeast-1.compute.internal:31001
> Aug 02, 2016 5:03:10 PM org.apache.catalina.core.AprLifecycleListener 
> lifecycleEvent
> INFO: The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> Exception in thread "main" java.lang.InternalError
> at sun.security.ec.SunEC.initialize(Native Method)
> at sun.security.ec.SunEC.access$000(SunEC.java:49)
> at sun.security.ec.SunEC$1.run(SunEC.java:61)
> at sun.security.ec.SunEC$1.run(SunEC.java:58)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ec.SunEC.(SunEC.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:383)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> at 
> sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:282)
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299)
> at sun.security.jca.Providers.getFullProviderList(Providers.java:173)
> at java.security.Security.getProviders(Security.java:456)
> at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:393)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:576)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:599)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)
> {noformat}
> The process was still running:
> {noformat}
> amp   2104  0.2  2.7 1941916 107360 ?  Sl   17:03   0:09 
> /etc/alternatives/jre/bin/java -Dnop 
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
> -javaagent:/home/users/amp/brooklyn-managed-processes/apps/GfmrLSwE/entities/Tomcat8Server_pEKbtDGD/brooklyn-jmxmp-agent-shaded-0.10.0-20160609.1043.jar
>  -Xms200m -Xmx800m -XX:MaxPermSize=400m -Dcom.sun.management.jmxremote 
> -Dbrooklyn.jmxmp.rmi-port=1099 -Dbrooklyn.jmxmp.port=31001 
> -Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Djava.endorsed.dirs=/home/users/amp/brooklyn-managed-processes/installs/Tomcat8Server_8.0.22/apache-tomcat-8.0.22/endorsed
>

[GitHub] brooklyn-library pull request #54: Added wait to RabbitMQ restart effector

2016-08-04 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-library/pull/54


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (BROOKLYN-319) RabbitMQ restart failure

2016-08-04 Thread Duncan Godwin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duncan Godwin resolved BROOKLYN-319.

Resolution: Fixed

> RabbitMQ restart failure
> 
>
> Key: BROOKLYN-319
> URL: https://issues.apache.org/jira/browse/BROOKLYN-319
> Project: Brooklyn
>  Issue Type: Bug
> Environment: Centos 6 on BlueBox and Google Compute
>Reporter: Duncan Godwin
>
> RabbitMQ intermittently fails to come back up after restart of the entity on 
> some clouds (BlueBox and Google Compute known to fail).
> The brooklyn.debug.log shows the following for stopping and starting:
> {code}
> 2016-07-28 09:49:58,719 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10422]: stopping 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, initiating ssh on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)]
>  (env {RABBITMQ_
> HOME=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  
> RABBITMQ_LOG_BASE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  RABBITMQ_NODENAME=d5kw04uk46, RABBITMQ_NODE_PORT=567
> 2, 
> RABBITMQ_PID_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq.pid,
>  
> RABBITMQ_CONFIG_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq}):
>  #!/bin/ba
> sh -e
>  ; export 
> INSTALL_DIR="/home/users/amp/brooklyn-managed-processes/installs/RabbitBroker_3.6.0"
>  ; export 
> RUN_DIR="/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46"
>  ; mkdir -p $RUN_DIR ; cd $RUN_DIR ; ./sbin/rabbitmqctl 
> stop
> 2016-07-28 09:49:59,071 DEBUG brooklyn.SSH [Thread-335764]: 
> [d5kw04uk46@10.104.2.181:stdout] Stopping and halting node 
> 'd5kw04uk46@qa-scheduler-rabbitmq-server-be5' ...
> 2016-07-28 09:49:59,071 DEBUG brooklyn.SSH [Thread-335764]: 
> [d5kw04uk46@10.104.2.181:stdout] Executed 
> /tmp/brooklyn-20160728-094958719-Sndu-stopping_RabbitBrokerImpl_id_d.sh, 
> result 0
> 2016-07-28 09:49:59,072 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10422]: stopping 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)],
>  completed: return status 0
> 2016-07-28 09:49:59,078 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10385]: launching 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, initiating ssh on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)]
>  (env 
> {RABBITMQ_HOME=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  
> RABBITMQ_LOG_BASE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  RABBITMQ_NODENAME=d5kw04uk46, RABBITMQ_NODE_PORT=5672, 
> RABBITMQ_PID_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq.pid,
>  
> RABBITMQ_CONFIG_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq}):
>  #!/bin/bash -e
>  ; export 
> INSTALL_DIR="/home/users/amp/brooklyn-managed-processes/installs/RabbitBroker_3.6.0"
>  ; export 
> RUN_DIR="/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46"
>  ; mkdir -p $RUN_DIR ; cd $RUN_DIR ; nohup ./sbin/rabbitmq-server > 
> console-out.log 2> console-err.log & ; for i in {1..60}
> do
> grep 'Starting broker... completed' console-out.log && exit
> sleep 1
> done ; echo "Couldn't determine if rabbitmq-server is running" ; exit 1
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH [Thread-335769]: 
> [d5kw04uk46@10.104.2.181:stdout]   Starting broker... completed 
> with 0 plugins.
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH [Thread-335769]: 
> [d5kw04uk46@10.104.2.181:stdout] Executed 
> /tmp/brooklyn-20160728-094959078-mjxF-launching_RabbitBrokerImpl_id_.sh, 
> result 0
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10385]: launching 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)],
>  completed: return status 0
> {code}
> the console-out.log of the RabbitMQ instance contains:
> {code}
> ERROR: node with name "d5kw04uk46" already running on 
> "qa-scheduler-rabbitmq-server-be5"
> {code}
> The brooklyn.debug.log then contains the following check running messages
> {code}
> 2016-07-28 14:05:12,642 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-12886]: check-running 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, initiating ssh on machine 
>

[jira] [Commented] (BROOKLYN-319) RabbitMQ restart failure

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407922#comment-15407922
 ] 

ASF GitHub Bot commented on BROOKLYN-319:
-

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-library/pull/54


> RabbitMQ restart failure
> 
>
> Key: BROOKLYN-319
> URL: https://issues.apache.org/jira/browse/BROOKLYN-319
> Project: Brooklyn
>  Issue Type: Bug
> Environment: Centos 6 on BlueBox and Google Compute
>Reporter: Duncan Godwin
>
> RabbitMQ intermittently fails to come back up after restart of the entity on 
> some clouds (BlueBox and Google Compute known to fail).
> The brooklyn.debug.log shows the following for stopping and starting:
> {code}
> 2016-07-28 09:49:58,719 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10422]: stopping 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, initiating ssh on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)]
>  (env {RABBITMQ_
> HOME=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  
> RABBITMQ_LOG_BASE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  RABBITMQ_NODENAME=d5kw04uk46, RABBITMQ_NODE_PORT=567
> 2, 
> RABBITMQ_PID_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq.pid,
>  
> RABBITMQ_CONFIG_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq}):
>  #!/bin/ba
> sh -e
>  ; export 
> INSTALL_DIR="/home/users/amp/brooklyn-managed-processes/installs/RabbitBroker_3.6.0"
>  ; export 
> RUN_DIR="/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46"
>  ; mkdir -p $RUN_DIR ; cd $RUN_DIR ; ./sbin/rabbitmqctl 
> stop
> 2016-07-28 09:49:59,071 DEBUG brooklyn.SSH [Thread-335764]: 
> [d5kw04uk46@10.104.2.181:stdout] Stopping and halting node 
> 'd5kw04uk46@qa-scheduler-rabbitmq-server-be5' ...
> 2016-07-28 09:49:59,071 DEBUG brooklyn.SSH [Thread-335764]: 
> [d5kw04uk46@10.104.2.181:stdout] Executed 
> /tmp/brooklyn-20160728-094958719-Sndu-stopping_RabbitBrokerImpl_id_d.sh, 
> result 0
> 2016-07-28 09:49:59,072 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10422]: stopping 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)],
>  completed: return status 0
> 2016-07-28 09:49:59,078 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10385]: launching 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, initiating ssh on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)]
>  (env 
> {RABBITMQ_HOME=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  
> RABBITMQ_LOG_BASE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46,
>  RABBITMQ_NODENAME=d5kw04uk46, RABBITMQ_NODE_PORT=5672, 
> RABBITMQ_PID_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq.pid,
>  
> RABBITMQ_CONFIG_FILE=/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46/rabbitmq}):
>  #!/bin/bash -e
>  ; export 
> INSTALL_DIR="/home/users/amp/brooklyn-managed-processes/installs/RabbitBroker_3.6.0"
>  ; export 
> RUN_DIR="/home/users/amp/brooklyn-managed-processes/apps/b6kxbm5fei/entities/RabbitBroker_d5kw04uk46"
>  ; mkdir -p $RUN_DIR ; cd $RUN_DIR ; nohup ./sbin/rabbitmq-server > 
> console-out.log 2> console-err.log & ; for i in {1..60}
> do
> grep 'Starting broker... completed' console-out.log && exit
> sleep 1
> done ; echo "Couldn't determine if rabbitmq-server is running" ; exit 1
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH [Thread-335769]: 
> [d5kw04uk46@10.104.2.181:stdout]   Starting broker... completed 
> with 0 plugins.
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH [Thread-335769]: 
> [d5kw04uk46@10.104.2.181:stdout] Executed 
> /tmp/brooklyn-20160728-094959078-mjxF-launching_RabbitBrokerImpl_id_.sh, 
> result 0
> 2016-07-28 09:49:59,110 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-10385]: launching 
> RabbitBrokerImpl{id=d5kw04uk46, amqpPort=5672}, on machine 
> SshMachineLocation[10.104.2.181:amp@10.104.2.181/10.104.2.181:22(id=t0tvrv6o0h)],
>  completed: return status 0
> {code}
> the console-out.log of the RabbitMQ instance contains:
> {code}
> ERROR: node with name "d5kw04uk46" already running on 
> "qa-scheduler-rabbitmq-server-be5"
> {code}
> The brooklyn.debug.log then contains the following check running messages
> {code}
> 2016-07-28 14:05:12,642 DEBUG brooklyn.SSH 
> [brooklyn-execmanager-E26Om0Sg-12886]: check-running 
>

[GitHub] brooklyn-library issue #54: Added wait to RabbitMQ restart effector

2016-08-04 Thread aledsage 
Github user aledsage commented on the issue:

https://github.com/apache/brooklyn-library/pull/54
  
LGTM; thanks @drigodwin - merging.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (BROOKLYN-320) Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407917#comment-15407917
 ] 

ASF GitHub Bot commented on BROOKLYN-320:
-

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-server/pull/290


> Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5
> -
>
> Key: BROOKLYN-320
> URL: https://issues.apache.org/jira/browse/BROOKLYN-320
> Project: Brooklyn
>  Issue Type: Bug
> Environment: CentOS 6.5, with nss 3.15, in aws-ec2 singapore
>Reporter: Aled Sage
>
> Deploying Tomcat8Server failed (when waiting for service-up), using Brooklyn 
> 0.10.0-SNAPSHOT. This was in AWS-singapore, using 
> RightImage_CentOS_6.5_x64_v13.5.2.2_EBS (ami-42bfe910).
> TL;DR: the problem is fixed by upgrading nss (manually on the target VM).
> Looking on the VM, the file 
> {{/home/users/amp/brooklyn-managed-processes/apps/GfmrLSwE/entities/Tomcat8Server_pEKbtDGD/logs/catalina.out}}
>  had the following contents:
> {noformat}
> JmxmpAgent active at: 
> service:jmx:jmxmp://ip-10-167-0-52.ap-southeast-1.compute.internal:31001
> Aug 02, 2016 5:03:10 PM org.apache.catalina.core.AprLifecycleListener 
> lifecycleEvent
> INFO: The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> Exception in thread "main" java.lang.InternalError
> at sun.security.ec.SunEC.initialize(Native Method)
> at sun.security.ec.SunEC.access$000(SunEC.java:49)
> at sun.security.ec.SunEC$1.run(SunEC.java:61)
> at sun.security.ec.SunEC$1.run(SunEC.java:58)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ec.SunEC.(SunEC.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:383)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> at 
> sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:282)
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299)
> at sun.security.jca.Providers.getFullProviderList(Providers.java:173)
> at java.security.Security.getProviders(Security.java:456)
> at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:393)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:576)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:599)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)
> {noformat}
> The process was still running:
> {noformat}
> amp   2104  0.2  2.7 1941916 107360 ?  Sl   17:03   0:09 
> /etc/alternatives/jre/bin/java -Dnop 
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
> -javaagent:/home/users/amp/brooklyn-managed-processes/apps/GfmrLSwE/entities/Tomcat8Server_pEKbtDGD/brooklyn-jmxmp-agent-shaded-0.10.0-20160609.1043.jar
>  -Xms200m -Xmx800m -XX:MaxPermSize=400m -Dcom.sun.management.jmxremote 
> -Dbrooklyn.jmxmp.rmi-port=1099 -Dbrooklyn.jmxmp.port=31001 
> -Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false 
>

[GitHub] brooklyn-server pull request #290: Upgrade NSS on yum based systems

2016-08-04 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-server/pull/290


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-server issue #290: Upgrade NSS on yum based systems

2016-08-04 Thread aledsage 
Github user aledsage commented on the issue:

https://github.com/apache/brooklyn-server/pull/290
  
LGTM; merging now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-server issue #290: Upgrade NSS on yum based systems

2016-08-04 Thread aledsage 
Github user aledsage commented on the issue:

https://github.com/apache/brooklyn-server/pull/290
  
All our PR builds are failing with:

```
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 42783
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[brooklyn-server-pull-requests] $ 
/home/jenkins/tools/java/latest1.7/bin/java -Xmx1024m -Xms512m 
-XX:MaxPermSize=512m -cp 
/home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3/conf/logging
 jenkins.maven3.agent.Maven32Main 
/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
 /home/jenkins/jenkins-slave/slave.jar 
/home/jenkins/jenkins-slave/maven32-interceptor.jar 
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 42783
Exception in thread "main" java.lang.ClassNotFoundException: 
hudson.remoting.Launcher
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:143)
at jenkins.maven3.agent.Maven32Main.main(Maven32Main.java:74)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:365)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:310)
at hudson.slaves.Channels.forProcess(Channels.java:115)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:297)
at hudson.maven.ProcessCache.get(ProcessCache.java:236)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1738)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Putting comment on the pull request
Finished: FAILURE
```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-server pull request #290: Upgrade NSS on yum based systems

2016-08-04 Thread drigodwin 
GitHub user drigodwin opened a pull request:

https://github.com/apache/brooklyn-server/pull/290

Upgrade NSS on yum based systems

Addesses [BROOKLYN-320](https://issues.apache.org/jira/browse/BROOKLYN-320) 
by upgrading NSS on yum based systems after the install of Java.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/drigodwin/brooklyn-server java-nss

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/290.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #290


commit f758dfb96e67a183b2aa091e1c3306df1f6fb56f
Author: Duncan Godwin 
Date:   2016-08-04T14:17:16Z

Upgrade NSS on yum based systems




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (BROOKLYN-320) Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407833#comment-15407833
 ] 

ASF GitHub Bot commented on BROOKLYN-320:
-

GitHub user drigodwin opened a pull request:

https://github.com/apache/brooklyn-server/pull/290

Upgrade NSS on yum based systems

Addesses [BROOKLYN-320](https://issues.apache.org/jira/browse/BROOKLYN-320) 
by upgrading NSS on yum based systems after the install of Java.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/drigodwin/brooklyn-server java-nss

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/290.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #290


commit f758dfb96e67a183b2aa091e1c3306df1f6fb56f
Author: Duncan Godwin 
Date:   2016-08-04T14:17:16Z

Upgrade NSS on yum based systems




> Tomcat8Server entity fails to start: using nss 3.15 on CentOS 6.5
> -
>
> Key: BROOKLYN-320
> URL: https://issues.apache.org/jira/browse/BROOKLYN-320
> Project: Brooklyn
>  Issue Type: Bug
> Environment: CentOS 6.5, with nss 3.15, in aws-ec2 singapore
>Reporter: Aled Sage
>
> Deploying Tomcat8Server failed (when waiting for service-up), using Brooklyn 
> 0.10.0-SNAPSHOT. This was in AWS-singapore, using 
> RightImage_CentOS_6.5_x64_v13.5.2.2_EBS (ami-42bfe910).
> TL;DR: the problem is fixed by upgrading nss (manually on the target VM).
> Looking on the VM, the file 
> {{/home/users/amp/brooklyn-managed-processes/apps/GfmrLSwE/entities/Tomcat8Server_pEKbtDGD/logs/catalina.out}}
>  had the following contents:
> {noformat}
> JmxmpAgent active at: 
> service:jmx:jmxmp://ip-10-167-0-52.ap-southeast-1.compute.internal:31001
> Aug 02, 2016 5:03:10 PM org.apache.catalina.core.AprLifecycleListener 
> lifecycleEvent
> INFO: The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> Exception in thread "main" java.lang.InternalError
> at sun.security.ec.SunEC.initialize(Native Method)
> at sun.security.ec.SunEC.access$000(SunEC.java:49)
> at sun.security.ec.SunEC$1.run(SunEC.java:61)
> at sun.security.ec.SunEC$1.run(SunEC.java:58)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ec.SunEC.(SunEC.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:383)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221)
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
> at 
> sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:282)
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299)
> at sun.security.jca.Providers.getFullProviderList(Providers.java:173)
> at java.security.Security.getProviders(Security.java:456)
> at 
> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:393)
> at 
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> at 
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:576)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:599)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at

[GitHub] brooklyn-server pull request #289: Fix non-deterministic test of SpecParamet...

2016-08-04 Thread grkvlt 
GitHub user grkvlt opened a pull request:

https://github.com/apache/brooklyn-server/pull/289

Fix non-deterministic test of SpecParameter by choosing correct entity

Fixes `SpecParameterUnwrappingTest#testParameterDefaultsUsedInConfig()`

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/grkvlt/brooklyn-server 
spec-parameter-test-non-deterministic

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/289.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #289


commit bf9e32c808f6367616ab7892dedc93e2e7d6ceff
Author: Andrew Donald Kennedy 
Date:   2016-08-04T14:01:53Z

Fix non-deterministic test of SpecParameter by choosing correct entity




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-server issue #288: BROOKLYN-323: Simplify Logout api

2016-08-04 Thread sjcorbett 
Github user sjcorbett commented on the issue:

https://github.com/apache/brooklyn-server/pull/288
  
@bostko Can you describe why we should change `/logout` from `POST` to 
`GET`? For one it means that if I can find a way to inject HTML into the page I 
can log every user that loads it out. It also risks browsers pre-fetching the 
page and users being unexpectedly logged out (as described in 
http://stackoverflow.com/questions/3521290/logout-get-or-post).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (BROOKLYN-323) Inconsistent logout behavior for Basic Authentication

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407548#comment-15407548
 ] 

ASF GitHub Bot commented on BROOKLYN-323:
-

Github user sjcorbett commented on the issue:

https://github.com/apache/brooklyn-server/pull/288
  
@bostko Can you describe why we should change `/logout` from `POST` to 
`GET`? For one it means that if I can find a way to inject HTML into the page I 
can log every user that loads it out. It also risks browsers pre-fetching the 
page and users being unexpectedly logged out (as described in 
http://stackoverflow.com/questions/3521290/logout-get-or-post).


> Inconsistent logout behavior for Basic Authentication
> -
>
> Key: BROOKLYN-323
> URL: https://issues.apache.org/jira/browse/BROOKLYN-323
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0, 0.10.0, 0.9.1
> Environment: Firefox, Internet Explorer, Google Chrome
>Reporter: Valentin Aitken
> Fix For: 0.10.0
>
>
> Observed behavior:
> When clicking logout browser asks for a password.
> When entering a password browser asks you sequentially to enter username and 
> password.
> How logout should be implemented for Basic Authentication:
> http://stackoverflow.com/questions/233507/how-to-log-out-user-from-web-site-using-basic-authentication
> My explanation for behavior with the current code:
> First to clear out how brooklyn-ui is working and what it does.
> It polls infinitely the brooklyn api to retrieve status for the applications 
> which are on the dashboard.
> To do that each request has to be authenticated.
> Logout:
> When user click logout, UI fires an ajax call to get a a proper Unauthorized 
> response.
> Current response for the logout request contains Unauthorized response which 
> should invalidate credentials.
> For Google Chrome it does invalidate the request credentials but it does not 
> reload the DOM (or the webpage)
> When user try to type username and password to login back again, it is 
> followed by another username and password prompt. 
> My explanation for this is that login actually appeared from one of the 
> application status calls rather than the index page and credentials are not 
> populated through the DOM.
> Because of this credentials have to be typed for every single request and  UI 
> is making status calls infinitely so in other words user have to enter 
> username and password infinitely.
> However for Internet Explorer it behaves differently.
> It just unauthenticate the one Ajax request and from there nothing happens. 
> Deletion of the session within Internet Explorer doesn't happen and browser 
> stays authenticated.
> My idea for solving those problems is to do a full reload of the web page 
> after deauthenticating.
> so Brooklyn can have only one javascript authentication cycle.
> I will provide a solution which does that in one simple step.
> Calling the /logout API call which returns Unauthorized response and redirect 
> to the home page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] brooklyn-ui issue #30: BROOKLYN-323: Improve logout script

2016-08-04 Thread nakomis 
Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-ui/pull/30
  
Tested alongside https://github.com/apache/brooklyn-server/pull/288 and 
this resolves the issue on Windows 10 on both IE and Edge. Behaviour on Chrome 
on OS X remains unchanged

LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (BROOKLYN-323) Inconsistent logout behavior for Basic Authentication

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407520#comment-15407520
 ] 

ASF GitHub Bot commented on BROOKLYN-323:
-

Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-ui/pull/30
  
Tested alongside https://github.com/apache/brooklyn-server/pull/288 and 
this resolves the issue on Windows 10 on both IE and Edge. Behaviour on Chrome 
on OS X remains unchanged

LGTM


> Inconsistent logout behavior for Basic Authentication
> -
>
> Key: BROOKLYN-323
> URL: https://issues.apache.org/jira/browse/BROOKLYN-323
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0, 0.10.0, 0.9.1
> Environment: Firefox, Internet Explorer, Google Chrome
>Reporter: Valentin Aitken
> Fix For: 0.10.0
>
>
> Observed behavior:
> When clicking logout browser asks for a password.
> When entering a password browser asks you sequentially to enter username and 
> password.
> How logout should be implemented for Basic Authentication:
> http://stackoverflow.com/questions/233507/how-to-log-out-user-from-web-site-using-basic-authentication
> My explanation for behavior with the current code:
> First to clear out how brooklyn-ui is working and what it does.
> It polls infinitely the brooklyn api to retrieve status for the applications 
> which are on the dashboard.
> To do that each request has to be authenticated.
> Logout:
> When user click logout, UI fires an ajax call to get a a proper Unauthorized 
> response.
> Current response for the logout request contains Unauthorized response which 
> should invalidate credentials.
> For Google Chrome it does invalidate the request credentials but it does not 
> reload the DOM (or the webpage)
> When user try to type username and password to login back again, it is 
> followed by another username and password prompt. 
> My explanation for this is that login actually appeared from one of the 
> application status calls rather than the index page and credentials are not 
> populated through the DOM.
> Because of this credentials have to be typed for every single request and  UI 
> is making status calls infinitely so in other words user have to enter 
> username and password infinitely.
> However for Internet Explorer it behaves differently.
> It just unauthenticate the one Ajax request and from there nothing happens. 
> Deletion of the session within Internet Explorer doesn't happen and browser 
> stays authenticated.
> My idea for solving those problems is to do a full reload of the web page 
> after deauthenticating.
> so Brooklyn can have only one javascript authentication cycle.
> I will provide a solution which does that in one simple step.
> Calling the /logout API call which returns Unauthorized response and redirect 
> to the home page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BROOKLYN-323) Inconsistent logout behavior for Basic Authentication

2016-08-04 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/BROOKLYN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407518#comment-15407518
 ] 

ASF GitHub Bot commented on BROOKLYN-323:
-

Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-server/pull/288
  
Tested alongside https://github.com/apache/brooklyn-ui/pull/30 and this 
resolves the issue on Windows 10 on both IE and Edge. Behaviour on Chrome on OS 
X remains unchanged

LGTM


> Inconsistent logout behavior for Basic Authentication
> -
>
> Key: BROOKLYN-323
> URL: https://issues.apache.org/jira/browse/BROOKLYN-323
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0, 0.10.0, 0.9.1
> Environment: Firefox, Internet Explorer, Google Chrome
>Reporter: Valentin Aitken
> Fix For: 0.10.0
>
>
> Observed behavior:
> When clicking logout browser asks for a password.
> When entering a password browser asks you sequentially to enter username and 
> password.
> How logout should be implemented for Basic Authentication:
> http://stackoverflow.com/questions/233507/how-to-log-out-user-from-web-site-using-basic-authentication
> My explanation for behavior with the current code:
> First to clear out how brooklyn-ui is working and what it does.
> It polls infinitely the brooklyn api to retrieve status for the applications 
> which are on the dashboard.
> To do that each request has to be authenticated.
> Logout:
> When user click logout, UI fires an ajax call to get a a proper Unauthorized 
> response.
> Current response for the logout request contains Unauthorized response which 
> should invalidate credentials.
> For Google Chrome it does invalidate the request credentials but it does not 
> reload the DOM (or the webpage)
> When user try to type username and password to login back again, it is 
> followed by another username and password prompt. 
> My explanation for this is that login actually appeared from one of the 
> application status calls rather than the index page and credentials are not 
> populated through the DOM.
> Because of this credentials have to be typed for every single request and  UI 
> is making status calls infinitely so in other words user have to enter 
> username and password infinitely.
> However for Internet Explorer it behaves differently.
> It just unauthenticate the one Ajax request and from there nothing happens. 
> Deletion of the session within Internet Explorer doesn't happen and browser 
> stays authenticated.
> My idea for solving those problems is to do a full reload of the web page 
> after deauthenticating.
> so Brooklyn can have only one javascript authentication cycle.
> I will provide a solution which does that in one simple step.
> Calling the /logout API call which returns Unauthorized response and redirect 
> to the home page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] brooklyn-server issue #288: BROOKLYN-323: Simplify Logout api

2016-08-04 Thread nakomis 
Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-server/pull/288
  
Tested alongside https://github.com/apache/brooklyn-ui/pull/30 and this 
resolves the issue on Windows 10 on both IE and Edge. Behaviour on Chrome on OS 
X remains unchanged

LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #99: Move entropy/ulimit docs to troubleshooting

2016-08-04 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-docs/pull/99


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #99: Move entropy/ulimit docs to troubleshooting

2016-08-04 Thread aledsage 
Github user aledsage commented on the issue:

https://github.com/apache/brooklyn-docs/pull/99
  
Thanks @drigodwin - I've made that change. Merging now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---