celery==5.2.7
rabbitmq:3.11.4
Python 3.9.16
i am upgrading the 3PP software for my project, from celery4.x.x to celery 5.2.7
celery stop unexpectedly if apply_async is called with eta set
#app.task(bind=True)
def healthcheck_exec(self,**parm):
......
healthcheck_exec.apply_async(None, parm,eta=next_planed_exec_datetime)
i turn on the debug log, no error detail in the log, only bellows
[2023-02-03 05:45:07,941: DEBUG/MainProcess] Canceling task consumer...
[2023-02-03 05:45:09,545: DEBUG/MainProcess] Canceling task consumer...
[2023-02-03 05:45:09,545: DEBUG/MainProcess] Closing consumer channel...
[2023-02-03 05:45:09,550: DEBUG/MainProcess] removing tasks from inqueue until task handler finished
i suspect there is a compatibility issue between rabbitmq and celery. no sure anybody met the issue?
Related
I am running several projects as spring boot applications, one of them specifically cannot start and is throwing:
java.lang.ClassNotFoundException: kotlinx.coroutines.debug.AgentPremain
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:304)
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)
Exception in thread "main" FATAL ERROR in native method: processing of -javaagent failed
Disconnected from the target VM, address: '127.0.0.1:64279', transport: 'socket'
Process finished with exit code 1
The command line has the option:
-javaagent:[...].m2/repository/org/jetbrains/kotlinx/kotlinx-coroutines-core/1.5.0/kotlinx-coroutines-core-1.5.0.jar
And this jar exists.
this happened after updating my Intellij'Idea to 2021.2
This issue happens only in debug mode.
Any idea how to solve this?
It is a known problem in the Kotlin plugin. As a workaround disable the coroutine agent option under Settings/Preferences | Build, Execution, Deployment | Debugger | Data Views | Kotlin | enable "Disable coroutine agent".
Please follow https://youtrack.jetbrains.com/issue/KTIJ-19345 , for updates.
I was working on my Mule 4 application today, and suddenly my Anypoint Studio went crazy. When I was trying to run my application, i recieved an error that a port used by the application is already in use. Nothing unusual, but when I have restarted my PC and wanted to run the app again, suspicious information showed up in the console:
INFO 2021-05-25 12:40:21,056 [WrapperListener_start_runner] [processor: ; event: ] org.mule.runtime.core.internal.construct.AbstractFlowConstruct: Flow ImportPendingCorrectionsFlow has not been started
INFO 2021-05-25 12:40:21,056 [WrapperListener_start_runner] [processor: ; event: ] org.mule.runtime.core.internal.construct.FlowConstructLifecycleManager: Starting flow: ImportInvoicesFlow
INFO 2021-05-25 12:40:21,056 [WrapperListener_start_runner] [processor: ; event: ] org.mule.runtime.core.internal.construct.FlowConstructLifecycleManager: Stopping flow: ImportInvoicesFlow
and the same message for all flows in my application.
Then I tried to run an existing MUnit test, which was running correctly since a month or more, and I recieved this error:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Running test: ImportInvoicesFlowTestWithIncorrectVehicleCount - Test +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
java.lang.AssertionError: The error ID thrown does not match the expected one. expected:<[APP:VALIDATION]> but was:<[HTTP:CONNECTIVITY]>
at org.mule.munit.runner.flow.TestFlow.run(TestFlow.java:313)
Caused by: java.io.IOException: Remotely closed
Caused by: java.io.IOException: Remotely closed
This is indeed very strange - as this flow has nothing to do with HTTP at all.
Finally, I have discovered a very strange WARN in the console:
WARN 2021-05-25 13:04:35,613 [Mule.app.deployer.monitor.1.thread.1] [processor: ; event: ] com.mulesoft.agent.configuration.descriptor.YamlMuleAgentDescriptor: Descriptor file /home/xxxxxxx/apps/AnypointStudio-7.7.0-linux64/AnypointStudio/plugins/org.mule.tooling.server.4.3.0.ee_7.3.5.202105101830/mule/conf/invoices-esb-mule4-app.yml not found.
I don't know what's happening here, i have never ever created such a file as invoices-esb-mule4-app.yml. I assume that this is some kind of a configuration file created by Mule itself basing on the application name. The path is strange here, as the workspace I'm working on is in /home/xxxxxxx/AnypointStudio7/workspace-2/
Other information that can be helpful (or not)
I was working on an ApiKit SOAP service, but still, it worked fine.
At one moment, I have misclicked Mule Design perspective and clicked Api Desing perspective, which ended in an application crash, but it SEEMED to be working correctly after starting Anypoint Studio again.
Is anyone having an idea what could have happened to my Anypoint Studio or my application?
I encountered a similar problem in which the logs said FlowConstructLifecycleManager: Starting flow [flow name], then FlowConstructLifecycleManager: Stopping flow [flow name], then AbstractFlowConstruct: Flow [flow name] has not been started. Then repeat those three with the next flow.
After spending more than a day trying various solutions, my team tried going to Run, Run Configurations, select Mule Applications, select the Mule application, General tab, "Clear Application Data:" and changing it to "Always". It had been "Never". After making this change and running it again, it started working. Hope this helps you or someone else with a similar "Stopping flow" problem.
The YML could be a per application configuration file created by the Runtime Manager Agent. It is strange that it is create in an execution inside Studio though. Check if the /home/xxxxxxx/apps/AnypointStudio-7.7.0-linux64/AnypointStudio/plugins/org.mule.tooling.server.4.3.0.ee_7.3.5.202105101830/mule/conf/mule-agent.yml is referencing it.
I does added in my project react-nativ-navigation library,Instruction
I tried to change the variables, because instruction outdated, but I get ERROR after compilations.
Building - completed;
Execution - ERORR
Skipping task ':react-native-navigation:javaPreCompileReactNative57Debug' as it is up-to-date.
:react-native-navigation:javaPreCompileReactNative57Debug (Thread[Execution worker for ':' Thread 2,5,main]) completed. Took 0.005 secs.
:react-native-navigation:compileReactNative57DebugJavaWithJavac (Thread[Daemon worker Thread 23,5,main]) started.
> Task :react-native-navigation:compileReactNative57DebugJavaWithJavac FAILED
Caching disabled for task ':react-native-navigation:compileReactNative57DebugJavaWithJavac' because:
Build cache is disabled
Task ':react-native-navigation:compileReactNative57DebugJavaWithJavac' is not up-to-date because:
Task has failed previously.
All input files are considered out-of-date for incremental task ':react-native-navigation:compileReactNative57DebugJavaWithJavac'.
Help me please, a not working witch react nativ.
Ask for any information.
Upgrade and reinstall your react-native-navigator version to ^3.2 and use RNN v3.
RNN v2 not work with react-native 060
After a VM shutdown, GraphDB Workbench would not start.
I have installed GraphDB on a cloud-hosted VM. Incidentally, the machine was shut down without stopping GraphDB. When trying to start it again, the Workbench would not start and the following message is displayed in the error log.
[ERROR] 2019-06-19 12:12:00,299 [Thread-10 | c.o.t.s.i.PluginManager]
Problem shutting down literals-index java.lang.RuntimeException:
com.ontotext.trree.transactions.TransactionException: Failed to
created journal file: /home/peio/graphdb-se-8.10.1/data/repositor
ies/bgnews/storage/literals-index/numerics.index.precommit
As Damyan suggested, delete literals-index in the storage folder and it will be rebuilt on start-up.
I installed Erlang and RabbitMQ on windows 7. RabbitMQ Service is running. But when I am trying to execute plugin enable command, I am getting below error
=SUPERVISOR REPORT==== 9-Jul-2018::14:14:46.134000 ===
supervisor: {local,'Elixir.Logger.Supervisor'}
errorContext: start_error
=INFO REPORT==== 9-Jul-2018::14:14:46.149000 ===
application: logger
exited: {{shutdown,
{failed_to_start_child,'Elixir.Logger.ErrorHandler',noproc}},
{'Elixir.Logger.App',start,[normal,[]]}}
type: temporary
Could not start application logger: Logger.App.start(:normal, []) returned an er
ror: shutdown: failed to start child: Logger.ErrorHandler
** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
You are using a version of RabbitMQ prior to 3.7.7 with Erlang 21. This is not supported and is clearly documented here: https://www.rabbitmq.com/which-erlang.html
Solution: upgrade to RabbitMQ 3.7.7 or downgrade Erlang to version 20.3.
Also, you could have found the answer to this yourself by searching Google with the following text:
rabbitmq "Elixir.Logger.ErrorHandler"
NOTE: the RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.