Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Received 409 (Conflict) for saving changes in AEM workspace crx.default

Avatar

Employee

When i creat a new jsp file and save the file  , i get the following error on CRXDE lite  :

 

Could not save changes. Received 409 (Conflict) for saving changes in workspace crx.default. This node already exists: /content/TrainingSite/contentpage.jsp

 

Can anybody please suggest the cause of the problem and the meaning of the code.

 

 

Thanks

1 Accepted Solution

Avatar

Correct answer by
Employee

Well that usually means that there is already a file/node with the same name so you can't create a new one at the same place. Are you sure there isn't already a node with that name? Perhaps created by someone else?

 

Also it would be unusual to create a JSP under /content - normally all JSPs would be created under /apps/<myapp>/components/somecomponent/contentpage.jsp. Are you creating you JSP in the right place?

View solution in original post

4 Replies

Avatar

Level 1

Do and check the following to fix the problem:

 

1. Did you earlier create and then delete some nodes under the folders you are working on?

2. Did you make too many changes without saving after each change?

3. Close the browser. open a new window. Clear the cache to be sure.
 Redo the changes (you could choose different node names) and save each time after every change. Doing this seems to solve the issue in most of the cases

You should be able to save now.

Avatar

Correct answer by
Employee

Well that usually means that there is already a file/node with the same name so you can't create a new one at the same place. Are you sure there isn't already a node with that name? Perhaps created by someone else?

 

Also it would be unusual to create a JSP under /content - normally all JSPs would be created under /apps/<myapp>/components/somecomponent/contentpage.jsp. Are you creating you JSP in the right place?

Avatar

Employee

Besides what is already explained about the conflict, restarting the instance worked for me. And yes, you have to be careful while renaming and saving components.

Avatar

Level 1

I got the same problem due to session expiry, I just re-login into the CRX lite console and issue got fixed.