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

Chandra29
Tera Contributor

@Enrique Collazo Even after checking and setting all the annoucement's 'Display style' to "Normal" facing the same issue.

 

Any other step that need to be followed here?

 

Please suggest.

did you ever figure this one out? I am seeing the same thing in our instance.

 

Thanks,

Donovan

I am experiencing this as well, in a ATF I've been running successfully for the past six months. No changes has been made between yesterday and today, yet the ATF fails today.