We are moving an application from DEV to QA and are getting the errors below.

mohamedb over 8 years ago

We are moving an application from DEV to QA and are getting the errors below.

Problems (5):
content _a-0000dbdc-df08-8000-5454-680000680000_226622 181921 "KALI All Process Request Report": An error occurred while updating content [id=181921 uuid=_a-0000dbdc-df08-8000-5454-680000680000_226622]: java.lang.IllegalStateException: JBWEB000212: Session already invalidated (APNX-1-4071-008)
content _a-0000dbdc-df08-8000-5454-680000680000_223186 181949 "Kali Task Reassignmnet": An error occurred while updating content [id=181949 uuid=_a-0000dbdc-df08-8000-5454-680000680000_223186]: java.lang.IllegalStateException: JBWEB000212: Session already invalidated (APNX-1-4071-008)
content _a-0000dbdc-df08-8000-5454-680000680000_228587 182048 "Kali Audit Trail History": An error occurred while updating content [id=182048 uuid=_a-0000dbdc-df08-8000-5454-680000680000_228587]: java.lang.IllegalStateException: JBWEB000212: Session already invalidated (APNX-1-4071-008)
c...

Discussion posts and replies are publicly visible

0 mohamedb over 8 years ago

...ontent _a-0000dbdc-df08-8000-5454-680000680000_221767 182083 "KALI : My Tasks Report": An error occurred while updating content [id=182083 uuid=_a-0000dbdc-df08-8000-5454-680000680000_221767]: java.lang.IllegalStateException: JBWEB000212: Session already invalidated (APNX-1-4071-008)
content _a-0000dbdc-df08-8000-5454-680000680000_226581 182163 "KALI Completed Tasks": An error occurred while updating content [id=182163 uuid=_a-0000dbdc-df08-8000-5454-680000680000_226581]: java.lang.IllegalStateException: JBWEB000212: Session already invalidated (APNX-1-4071-008)

Success

-----

Any Advice?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aasuliman over 8 years ago

is the problems occurred when you import the application or export it?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mohamedb over 8 years ago

This was resolved by logging in again the following day. It seems like a user session issue! Thanks for your care!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel