Upgrade San Diego "stream has already been operated upon or closed"

JG6
Kilo Guru

Hello Community,

We're getting a recurring error after the upgrade of a Quebec instance to San Diego (see under). 

It looks like some rest calls from the Servicenow UI run into trouble. They seem to hang or stop in their tracks. The web browser debug tools show an outgoing http post, which fail w/o a response. I assume therefor the exceptions are related to that issue. Unfortunately I have no clue where this comes from.

Is there anyone in here who has seen this before ? Or has a hint as to what I can try ? 

Many thanks indeed !

J

Exception while executing request: stream has already been operated upon or closed: com.glide.rest.util.RESTRuntimeException: Exception while executing request: stream has already been operated upon or closed: com.glide.rest.handler.impl.ServiceHandlerImpl.handleInvocationTargetException(ServiceHandlerImpl.java:76)
com.glide.rest.handler.impl.ServiceHandlerImpl.invokeService(ServiceHandlerImpl.java:49)
com.glide.rest.processors.RESTAPIProcessor.process(RESTAPIProcessor.java:349)
com.glide.processors.AProcessor.runProcessor(AProcessor.java:612)
com.glide.processors.AProcessor.processTransaction(AProcessor.java:274)
com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:184)
com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:172)
com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:46)
com.glide.sys.Transaction.run(Transaction.java:2468)
com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:27)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

1 ACCEPTED SOLUTION

Enrique Collazo
ServiceNow Employee
ServiceNow Employee

if this is related to the Announcements, try the following.

Please ensure that all your Announcements have a valid display value even if it is an old Announcement. I had this issue and was able to remedy it by ensuring there was a value for all the Announcements, after fixing this, the Announcements appeared in the Portal as expected. 

View solution in original post

7 REPLIES 7

Enrique Collazo
ServiceNow Employee
ServiceNow Employee

if this is related to the Announcements, try the following.

Please ensure that all your Announcements have a valid display value even if it is an old Announcement. I had this issue and was able to remedy it by ensuring there was a value for all the Announcements, after fixing this, the Announcements appeared in the Portal as expected. 

Hello, @Enrique Collazo.

I have the same problem, my announcements are not appearing on the portal.
I tried your solution but I didn't understand it very well. What do you mean by "valid display value"? I didn't find this field in the announcements

Hello @Vitor Vieira , I attached a screenshot below for you to see the field that I was mentioning in my previous comment.

 

Screen Shot 2022-10-27 at 12.36.54 PM.png

how do you know it's the Announcements?