Replacement of standard console application

[temp]

Why is the replacement of the standard console application needed? This leads to several disadvantages, for example that a database connection is always created on execution of app/console. Wouldn't it be better to just implement a command that runs a job by ID? In our project the tests now fail, because we have no database configured for the tests.

[kingcrunch]

:thumbsup:

[pborreli]

:+1:

[schmittjoh]

I don't see how we can gather debug information without overriding the application, a command which just runs another command cannot do this. The jms-job-queue:run command basically already does what you suggest and can only log output.

Maybe we can find another solution to lazily create the connection.

[Koc]

There are console events introduced in 2.3. Aren't they not enough?

[Tjeerd]

Just a quick note: in one of my projects we solved this by setting the jms_job_queue.statistics to false for the test environment.