Hi,
I wonder if somebody can help me with an issue, and sorry if this is obvious. Basically I would like help and to know if there is something special I need to do when implementing a new OSGI configuration.
I have added a new configuration with the primaryType is OsgiConfig, and deployed it to staging via Mavern. The Mavern build is updating both author ( 4502 ) and publisher ( 4503 ),
In the author environment, I can see this configuration when I go to preview pages, it picks up the relevant path and picks up the relevant code. However, on the dispatcher this doesn't seem to be added, when viewing the published page on a browser it is not picking up the new configuration. I have cleared the dispatcher cache, but nothing has changed.
Is there something special I need to do when implementing a new OSGI configuration to show on the published pages ?
Thank you for your time,
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Veena, Viveksachdeva, Ravindra and smacdonald2008,
Thank you all so much for your time and answers with this. I believe that I have now worked this out. I had two configurations for this setting, and they conflicted with each other. I guess that on author it read one configuration first, and then on publisher it read the other one first. In fact, when I looked at the OSGI config manager I actually saw that they were the other way around in 4502 than to 4503.
Hopefully this is now sorted, I am grateful for your responses.
Views
Replies
Total Likes
HI,
1. Is it showing on publish environment ?
If no , Please check OSGI configuration is loaded or not.
if OSGI not loaded in publish , please check run mode(osgi node) created for publish ?
ex : config.dev-publish or config.publish
2. If it showing both Author and Publish good.
Is exact page cache cleared ?
Please check page with query strings.
If not help above please share more infromation , to help your issue.
Thanks
Ravindra
Views
Replies
Total Likes
"on the dispatcher" - you mean on the Production server right?
Dispatcher is not a server - it caches pages and a load balancer.
However - on Production - make sure that you have all of the same config settings.
Views
Replies
Total Likes
Hi Ravindra and S MacDonald,
Thank you very much for your responses, and sorry if I am not using the correct wording,
I checked and when I look at the page on 4502 then I can see the changes on the form, but when I check the same page on 4503 then I can't see the configuration being picked up, although I can see other form changes ( if I add text or a component etc - to check that the page cache is refreshing ).
If I check configuration manager ( /system/console/configMgr ) on both 4502 and 4503 then I can see the configuration file there, so it does seem to have pushed to both.
Sorry, not sure how to proceed after this?
Thank you again.
Views
Replies
Total Likes
The only difference between the 2 environments is the Dispatcher is used in Prod Server? Can you try to do test - try doing this use case using a setup on a DEV server - where you have 4502 and 4503 servers running. Test this in that environment. This will tell us if issue is with your environment and Dispatcher somehow interfering.
Views
Replies
Total Likes
Configurations can sometimes go tricky. In some cases , it would need a restart for the changes to pick up. Can you try restarting your server and check if the configurations are picking up ?
Views
Replies
Total Likes
Have you tried logging the value of configurations when bundle is activated?
Views
Replies
Total Likes
Hi Veena,
Thanks for the reply. We did try and restarted the servers on staging to check, but it still only works when I preview the page on author, and it doesn't work on the publisher ( 4503 ) page.
Views
Replies
Total Likes
Hi Veena, Viveksachdeva, Ravindra and smacdonald2008,
Thank you all so much for your time and answers with this. I believe that I have now worked this out. I had two configurations for this setting, and they conflicted with each other. I guess that on author it read one configuration first, and then on publisher it read the other one first. In fact, when I looked at the OSGI config manager I actually saw that they were the other way around in 4502 than to 4503.
Hopefully this is now sorted, I am grateful for your responses.
Views
Replies
Total Likes
wer they factory configs ? Have you given unique PID for the configs to get configured properly ?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies