RabbitMQ for ES

51 views
Skip to first unread message

scorpiovn

unread,
Jul 5, 2011, 12:45:32 PM7/5/11
to Eureka Streams Development
I have used RabbitMQ for ES.
In QueueTaskHandlerMDB, I modified the method handleTask like this:

pulic void handleTask(final UserActionRequest inUserActionRequest)
{
..............
this.rabbitTemplate.convertAndSend(inUserActionRequest);
.............
}

I got this error:
ERROR org.quartz.core.JobRunShell - Job DEFAULT.cacheInitializationJob
threw an unhandled Exception:
org.springframework.scheduling.quartz.JobMethodInvocationFailedException:
Invocation of method 'initializeCache' on target class [class
org.eurekastreams.server.persistence.mappers.cache.CacheInitializer]
failed; nested exception is java.lang.NoClassDefFoundError: org/
springframework/util/MultiValueMap
at
org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean
$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:
269)
at
org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:
86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool
$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: java.lang.NoClassDefFoundError: org/springframework/util/
MultiValueMap

Please help me.

+++
thomas.kant

Rob Keane

unread,
Jul 5, 2011, 8:06:18 PM7/5/11
to eureka-st...@googlegroups.com
How are you pulling in RabbitMQ and it's dependencies?

It sounds like something is wrong with spring, maybe you have multiple versions?

scorpiovn

unread,
Jul 6, 2011, 6:04:39 AM7/6/11
to Eureka Streams Development
Rob,

I used these in the pom.xml files:

<dependency>

<groupId>org.springframework.amqp</groupId>

<artifactId>spring-amqp</artifactId>

<version>1.0.0.RC1</version>

</dependency>

<dependency>

<groupId>org.springframework.amqp</groupId>

<artifactId>spring-rabbit</artifactId>

<version>1.0.0.RC1</version>

</dependency>

<dependency>

<groupId>com.rabbitmq</groupId>

<artifactId>amqp-client</artifactId>

<version>2.5.0</version>

</dependency>

More question, should we change ES to spring 3.0?

Thanks,
+++
thomas.kant

On Jul 6, 7:06 am, Rob Keane <rob.ke...@gmail.com> wrote:
> How are you pulling in RabbitMQ and it's dependencies?
>
> It sounds like something is wrong with spring, maybe you have multiple versions?
>

Rob Keane

unread,
Jul 6, 2011, 7:59:28 AM7/6/11
to eureka-st...@googlegroups.com
I'm guessing if you do mvn dependency:tree you'll see that is pulling
in a second version of Spring, which is causing the errors you're
seeing. It RabbitMQ can run with the older version of Spring you may
be able to get away with it by adding an <exclusion>

We looked into Spring 3.0 at one point but found the upgrade looked
like more effort than we could support at that time. Of course you are
welcome to look into it (and contribute back the results :))

scorpiovn

unread,
Jul 6, 2011, 3:15:41 PM7/6/11
to Eureka Streams Development
Rob,

On the article, a Spring guy said that we should use Spring
3.0.5.RELEASE for Spring AMQP.
http://forum.springsource.org/showthread.php?110960-spring-amqp-with-spring-2.5

I have upgraded ES to Spring 3.0.5.RELEASE.
I saw that the RabbitTemplate can send data to RabbitMQ broker.
But as oppening ES http://localhost:8080, I got this error:

HTTP ERROR 500

Problem accessing /. Reason:
org.hibernate.SessionException: Session is closed!

Caused by:
javax.persistence.PersistenceException:
org.hibernate.SessionException: Session is closed!
at
org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:
614)
at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:76)
at
org.eurekastreams.server.persistence.mappers.GetRootOrganizationIdAndShortName.fetchRootOrg(GetRootOrganizationIdAndShortName.java:
82)
at
org.eurekastreams.server.persistence.mappers.GetRootOrganizationIdAndShortName.getRootOrganizationId(GetRootOrganizationIdAndShortName.java:
54)
at
org.eurekastreams.server.service.filters.RootOrgCheckFilter.doFilter(RootOrgCheckFilter.java:
64)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1212)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:
399)
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)
Caused by: org.hibernate.SessionException: Session is closed!
at
org.hibernate.impl.AbstractSessionImpl.errorIfClosed(AbstractSessionImpl.java:
72)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1137)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:67)
... 20 more


Please help me this error.

On Jul 6, 6:59 pm, Rob Keane <rob.ke...@gmail.com> wrote:
> I'm guessing if you do mvn dependency:tree you'll see that is pulling
> in a second version of Spring, which is causing the errors you're
> seeing.  It RabbitMQ can run with the older version of Spring you may
> be able to get away with it by adding an <exclusion>
>
> We looked into Spring 3.0 at one point but found the upgrade looked
> like more effort than we could support at that time. Of course you are
> welcome to look into it (and contribute back the results :))
>
Reply all
Reply to author
Forward
0 new messages