alsar
alsar
If you followed the tutorial http://jmsyst.com/bundles/JMSAopBundle#transaction-management, it should work without any problems. Where did you stuck?
It's `autoload-dev` is triggered on `composer install` (you don't need to specify --dev). I think it will load only dev sources from the root package, but I'm not 100% sure....
I checked it and composer will install and load only the `require-dev` packages defined the root package.
Why do you need to know if the install/update is run with or without `--no-dev`? Is the information available in the `composer.lock` not sufficient?
``` [program:project_dev_rabbitmq-cli-convert] command=/usr/bin/rabbitmq-cli-consumer -e "/home/user/development/project/current/app/console convert-upload --rabbitmq" -c /home/user/config/rabbitmq_cli_project_dev.conf process_name=%(program_name)s_%(process_num)02d numprocs=2 autostart=true autorestart=unexpected user=user stdout_logfile=/home/user/log/project_dev/convert-out.log stderr_logfile=/home/user/log/project_dev/convert-error.log ``` I cleared all logs today before I started testing. After the process stopped...
The problem seems to be in the Supervisor config. The minimal config seems to work now: ``` [inet_http_server] port = 127.0.0.1:9001 username=user password=pass [unix_http_server] file=/var/run/supervisor.sock chmod=0700 [supervisord] logfile=/tmp/supervisord.log pidfile=/var/run/supervisord.pid [rpcinterface:supervisor]...
It seems that the problem still exists. It worked for like 20 hours, but then stopped to processing messages. I restarted the Supervisor process and then again stopped processing after...
The error log is empty and in the stdout log is just ``` Waiting for messages... 2016/02/09 11:22:04 Processing message... 2016/02/09 11:22:09 Processed! 2016/02/09 11:22:09 Processing message... 2016/02/09 11:22:13 Processed!...
After 21 hours it stoped working and I got this in the RabbitMQ log: ``` =WARNING REPORT==== 11-Feb-2016::09:08:34 === closing AMQP connection (127.0.0.1:50993 -> 127.0.0.1:5672): client unexpectedly closed TCP connection...
It's a Ubuntu 14.04 machine. rabbitmq-cli-consumer v1.1.0 is installed via the APT repository. Supervisor 3.2.1 installed via pip. RabbitMQ is v3.6.0. Locally on my Vagrant environment I didn't encounter this...