EJB PeerGoneException Leads to "java.io.StreamCorruptedException: invalid type code: 11" When Using GridLink Data Source On WebLogic
Last updated on MAY 24, 2017
Applies to:Oracle WebLogic Server - Version 10.3.5 to 188.8.131.52.0
Information in this document applies to any platform.
The following error was observed when making an EJB call between WebLogic Server 10.3.5 and WebLogic Server 12.1.3 where the EJB bean utilized a DataSource and switching to a Gridlink Datasource:
Note that in addition to the "invalid type code: 11", also seen was "java.io.StreamCorruptedException: invalid type code: 0B"
Behavior was very unusual as the Gridlink DataSource appeared to be functioning fine and there was no discernible link between components of EJB and Gridlink.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms