Lost Studio hot reload on upgrade to v5.5
I've upgraded my project to nuxeo CAP/DM v5.5 on my CentOS release 5.7 (Final) system. I've registered the instance and now I've lost the hot upload functionality.
Upload works when the Admin Center->Update Center->Nuxeo Studio->Update button is pushed, but I need a manual restart of nuxeo for it to take effect.
The server.log file shows none of the normal “hot update” oriented tasks are being run.
I've tried de-registering and re-registering with no change: No automatic hot reload.
Any suggestions on where to look to find out what is happening?
0 votes
0 answers
1437 views
Can you give us your OS host
Can you activate the debug into your logs. I let you check how to do that here.
I turned on logging. I can see document type being unregistered and registered along with several other components being changed.
What should I be looking for in the logs?
If you
Does I well understand ?
Sorry about logs, I give you a bad URL, here is the good one.
The production system, new since posting of this question, seems to update normally without a reboot. This is a fresh v5.5 image with a fresh database.
The development system seems to require a re-boot on only some Studio updates. I have yet to determine which changes to the configuration require a reboot of Nuxeo DB.
Sorry for the delay, I was working on other issues not related to Nuxeo.
It seem I only need to restart Nuxeo DM when I make changes to a Content View.
I worked for the most the a day on action chains and user actions and didn't need to restart when I did an update from Studio.
The first time I changed a content view and did a Studio update the changes would not take effect until I restarted.