Skip to main content
3 votes

serialization issue while using ApacheMQ for tridion object cache

Apache ActiveMQ is blocking the JMS ObjectMessages for security reasons. This is the default configuration. Configure ActiveMQ to allow ObjectMessages to be deserialized. Either enable it for all ...
Velmurugan's user avatar
  • 8,205
2 votes
Accepted

How to configure JMS ConnectionFactory in DD4T2.0-Java webapp when its OSB as JMS server

You probably can use Spring's JMS listener combined with OSB. Configuration looks this this: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://...
Raimond's user avatar
  • 7,253
2 votes
Accepted

SDL Web 8.5 Synchronizing caches using Java Message Service doesn't work with 2 targets

Problem was caused by the RMIChannel Listenerport which is by default enabled in the quickinstall configs (SDL Web 8.5\Content Delivery\resources\quickinstall\config\deployer-combined\deployer-conf....
Gert de Heul's user avatar
2 votes

SDL Web 8.5 Synchronizing caches using Java Message Service doesn't work with 2 targets

The error is a sign of you starting up the CacheChannel service twice on the same port. Did you maybe merge the CCS in your Deployer startup? If you use ActiveMQ JMS, you don't actually need to setup ...
Raimond's user avatar
  • 7,253
1 vote
Accepted

ActiveMQ for caching invalidation messages using JMS for SDL Tridion sites 9.1

Answer to your question - No, only deployer and content service needs to be enabled Tridion object caching with ActiveMQ.
Velmurugan's user avatar
  • 8,205
1 vote

How to configure JMS ConnectionFactory in DD4T2.0-Java webapp when its OSB as JMS server

Configuration mentioned by Raimond above works and the spring webapp is now able to make connection to the JMS topic defined in OSB. Just couple of minor corrections thats why pasting the conf again ...
Gulshan Thakur's user avatar
1 vote
Accepted

Why DD4T JMSTransportListener implementation has hard binding with Apache ActiveMQ

There's no generic Transport Listener specification in the JMS Api / specification, so hence it's not possible to keep this part generic. You should be able simply remove the transportListener and ...
Raimond's user avatar
  • 7,253
1 vote

Why DD4T JMSTransportListener implementation has hard binding with Apache ActiveMQ

I guess the conclusion maybe is that the name of the class JMSTransportListener should possibly have been ActiveMQTransportListener instead, and if you are not intenting to use ActiveMQ, you should ...
Bart Koopman's user avatar
  • 29.6k

Only top scored, non community-wiki answers of a minimum length are eligible