Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Can't start crowd server

Benjamin Siegmund July 30, 2020

Hi all,

 

after the installation of our crowd server, all was good.

Yesterday the windows server had to restart. after this, crowd throws some errors and cant start right now:

 

 

2020-07-30 11:30:48fatalThis Crowd instance was unable to start the scheduler CrowdSchedulerService, and will not be usable. Please check the log for details.

 

In the log i can see a few errors like this:

2020-07-30 11:30:48,508 localhost-startStop-1 ERROR [atlassian.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.crowd.event.application.ApplicationReadyEvent@182d9c88] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.crowd.scheduling.JobRunnerRegistrar.onApplicationReady(com.atlassian.crowd.event.application.ApplicationReadyEvent) throws com.atlassian.scheduler.SchedulerServiceException, listener=com.atlassian.crowd.scheduling.JobRunnerRegistrar@28ce8287}]
java.lang.RuntimeException: Listener: com.atlassian.crowd.scheduling.JobRunnerRegistrar event: com.atlassian.crowd.event.application.ApplicationReadyEvent
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:50)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.lambda$null$0(AsynchronousAbleEventDispatcher.java:37)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:85)
at com.atlassian.crowd.core.event.TransactionAwareEventDispatcher.lambda$dispatch$0(TransactionAwareEventDispatcher.java:39)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)
at com.atlassian.crowd.core.event.TransactionAwareEventDispatcher.dispatch(TransactionAwareEventDispatcher.java:38)
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:200)
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:115)
at com.atlassian.crowd.core.event.TransactionAwareEventPublisher.publish(TransactionAwareEventPublisher.java:35)
at com.atlassian.crowd.console.listener.StartupListener.contextInitialized(StartupListener.java:108)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4699)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5165)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:614)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1823)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at org.hibernate.engine.transaction.jta.platform.internal.AbstractJtaPlatform.getCurrentStatus(AbstractJtaPlatform.java:136)
at org.hibernate.internal.StatelessSessionImpl.flushBeforeTransactionCompletion(StatelessSessionImpl.java:675)
at org.hibernate.internal.StatelessSessionImpl.beforeTransactionCompletion(StatelessSessionImpl.java:652)
at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:473)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.beforeCompletionCallback(JdbcResourceLocalTransactionCoordinatorImpl.java:178)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.access$300(JdbcResourceLocalTransactionCoordinatorImpl.java:39)
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:271)
at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:104)
at com.atlassian.crowd.util.persistence.hibernate.StatelessDao.withStatelessSession(StatelessDao.java:27)
at com.atlassian.crowd.dao.scheduling.ClusterJobDAOHibernate.find(ClusterJobDAOHibernate.java:34)
at com.atlassian.crowd.scheduling.ClusterJobDAODecorator.find(ClusterJobDAODecorator.java:96)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.getJobDetails(CaesiumSchedulerService.java:228)
at com.atlassian.crowd.scheduling.JobRunnerRegistrar.rescheduleJob(JobRunnerRegistrar.java:64)
at com.atlassian.crowd.scheduling.JobRunnerRegistrar.onApplicationReady(JobRunnerRegistrar.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:40)
... 22 more

 

All errors i can find have the same issue i think: 

java.lang.NullPointerException

 

Does anyone knows how the get rid of these errors and start crowd again? I check all databasetables for incorrect data and also the license in the config file.

 

 

1 answer

0 votes
Charlie Misonne
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 30, 2020
Benjamin Siegmund July 30, 2020

I checked it, but the result of the sql is null. i dont have duplicated keys

Charlie Misonne
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 3, 2020

Ok, perhaps it's better for you to contact Atlassian support.

Relying on part of a log file to troubleshoot this is not easy.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events