cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-3485) When RabbitMQ plugin enabled with the simulator, simulator setup results in Unable to schedule async job for command org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
Date Thu, 11 Jul 2013 20:05:48 GMT
Chip Childers created CLOUDSTACK-3485:
-----------------------------------------

             Summary: When RabbitMQ plugin enabled with the simulator, simulator setup results
in Unable to schedule async job for command org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
                 Key: CLOUDSTACK-3485
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3485
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.2.0
         Environment: simulator
            Reporter: Chip Childers
            Priority: Critical


This may also effect 4.1, but I'm unsure.  Was the RabbitMQ plugin tested in a non-simulated
environment (i.e.: did anyone enable this plugin and configure a zone)?  This may just be
a simulator + rabbit combination issue.

Removing the rabbitMQ plugin and doing the steps below results in no errors.


Steps to reproduce on master:

I edit client/tomcatconf/simulatorComponentContext.xml.in to include the rabbit mq plugin.

I then confirm that I see a login event published for a valid admin user login to the gui.

I then restart and reset the mgmt server with:

mvn -Pdeveloper -Dsimulator clean install; mvn -Pdeveloper -pl developer -Ddeploydb; mvn -Pdeveloper
-pl developer -Ddeploydb-simulator; mvn -pl client jetty:run

I then run the simulator setup as:

mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin integration-test

Then I see the following errors in the console from the jetty:run command:

WARN  [apache.cloudstack.alerts] (Cluster-Notification-1:)  alertType:: 14 // dataCenterId::
0 // podId:: 0 // clusterId:: null // message:: Management server node 127.0.0.1 is up
WARN  [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:) Notifying management server
join event took 21 ms
WARN  [cloud.async.AsyncJobManagerImpl] (507572448@qtp-656336336-3:) Unable to schedule async
job for command org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
unexpected exception.
java.lang.NullPointerException
	at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337)
	at com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173)
	at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217)
	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
	at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199)
	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513)
	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
ERROR [cloud.api.ApiServer] (507572448@qtp-656336336-3:) unhandled exception executing api
command: updateNetworkServiceProvider
com.cloud.utils.exception.CloudRuntimeException: Unable to schedule async job for command
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd, unexpected
exception.
	at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:223)
	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
	at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199)
	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:513)
	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:326)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-6:job-6 = [ 53eb3155-1a47-458c-adbe-1401477e77fe
]) Unexpected exception while completing async job-6 = [ 53eb3155-1a47-458c-adbe-1401477e77fe
]
java.lang.NullPointerException
	at com.cloud.api.ApiDBUtils.findJobInstanceUuid(ApiDBUtils.java:1337)
	at com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:173)
	at com.cloud.async.AsyncJobManagerImpl.completeAsyncJob(AsyncJobManagerImpl.java:252)
	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
	at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:534)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:722)



--
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

Mime
View raw message