This week's giveaway is in the Java/Jakarta EE forum.
We're giving away four copies of Java EE 8 High Performance and have Romain Manni-Bucau on-line!
See Stream is closed exception. The service is up as I could hit the endpoint wsdl url in the browser.

One thing which I have noticed is that when i build the Eclipse product from my local machine, the webservice works fine.

But the product taken from the subversion does'nt. Although both the products are built from same version of code.

The launcher jar in the plugins folder for the product which i built from the workspace is org.eclipse.equinox.launcher_1.0.200.v20090520.jar

and that of the product from the subversion is org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar

Can it be something with the JRE/Eclipse version.
JRE version is 1.6.0_21.
Eclipse for RCP/Plug-in Developers1.2.0.20090617-1252

Please help me in debugging the issue.

Stack trace of the exception is as follows Stream is closed
at Unknown S
adRequest(Unknown Source)
at oke(Unkno
wn Source)
at uest(Unkn
own Source)
at Source)
at Source)
at Source)
at Source)
at$2.process(Unkn own Sourc
at$HttpToolk it.handle
(Unknown Source)
at known Sou
at handleExc
hange(Unknown Source)
at handle(Un
known Source)
at$Chain.doFilter(Unknown Source)
at Source)
at$Chain.doFilter(Unknown Source)
at$Exchange$LinkHandler.handle(Un known Sou
at$Chain.doFilter(Unknown Source)
at$ Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)
Caused by: Stream is closed
at Source)
at Source)
at Source)
at Source)
at onImpl$1.
close(Unknown Source)
... 22 more


Haroon Subair
Posts: 2
posted 6 years ago
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
The issue surfaced for all the OneWay services. The issue was with JAX-WS version of the JRE referenced by the Eclipse to build the product.
Eclipse was referring JRE1.6.0_7. The issue is fixed in JAXWS version 2.1.3.
I have updated the JRE to 1.6.0_22 which solved the issue.

It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!