Hot answers tagged


You can monitor SDL Tridion services using any monitoring application like WhatsUpGold or Nagios. SDL Tridion has an inbuilt service to monitor the internal functions of Tridion which will then fire SNMP trap (messages) that can be picked up by the above mentioned tools.


It seems the only answer we could assume was an internal network update relating to internal DNS settings. Unfortunately this is all the information we really have at the moment although we'll push to investigate what was changed (if anything, from what... to what...) as it's very interesting that the xmlHttp response would take 10 minutes every time ...


Not all requests are made from the browser to the webserver; for some requests the webserver connects back to itself. I would presume that in your case these are the "problematic" calls as apparently the browser could resolve the DNS name of the server without any problems. When the server->server connections take place in a blocking manner (probably going ...


The answer is - unfortunately: it is not possible to configure the CIL to pool connections to the microservices.


In my opinion JMS is more robust and much more scalable than the CCS. I explained why in this blog: Also, see for additional configuration tips.


This article explains it pretty well: Port 1099 is indeed used only as the initial listening port, and then another (somewhat) random port is used for the actual notifications. You can force Tridion to use a specific port by using the following code in a Java Listener (if using J2EE) package com.sdl....


Unfortunately, you will have to indeed open up all ports > 1024 if you want to keep using RMI in order to have reliable communication for CCS. If that's not an option, I would recommend to switch to JMS. Yes, its more work to setup, but you also get a lot more functionality and it works through firewalls as well. Julian Wraith wrote a nice guide to setup ...

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