Databases
StackOverflow2013
Postsdbo
POJAX-WS client causes Jetty EofException
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJAX-WS client causes Jetty EofException
    primarykey
    data
    text
    <p>I am using an embedded Jetty server to provide Web Services (using Jetty-JAXWS2-SPI to allow Jetty to serve the requests) and I am seeing the following errors when a connection terminates from my JAX-WS test client (generated by <code>wsimport</code>):</p> <pre><code>11:32:54.544 [pool-1-thread-5] DEBUG com.mycompany.SomeClass - EOF org.eclipse.jetty.io.EofException: null at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:321) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307] at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307] at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411) ~[jetty-server-7.3.1.v20110307.jar:7.3.1.v20110307] at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:526) ~[jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307] at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:41) [jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [na:1.6.0_24] </code></pre> <p>Even though these are not important errors (logged at DEBUG level) and I only see them from my test client, not from soapUI or the 'real' (.NET client), I would rather not see them at all.</p> <p>I guess the problem is caused by the socket behavior within the JAX-WS client? Is there any way to influence the socket behavior to avoid this issue?</p> <p>Other information:</p> <ul> <li>Others have reported this issue on the Jetty mailing list, also when providing Web Services using Jetty-JAXWS2-SPI.</li> <li>I am using JDK 1.6.0_24 and the JAX-WS implementation it contains.</li> <li>I am using Jetty 7.3.1-20110307</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStrojanfoe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POJAX-WS client causes Jetty EofException
      1. USA J
      1. VTFavorite
    2. VO
      singulars
      1. POJAX-WS client causes Jetty EofException
      1. This table or related slice is empty.
      1. VTUpMod
    1. COhi. do you were able to resolve this issue? im experiencing the same error with paxweb and jetty.
      singulars
      1. POJAX-WS client causes Jetty EofException
      1. USNicolas
    2. CONo - I have implemented my own Jetty Logger class which only allows debug logs from Jetty if a command line/config file option is true (default false). In other words, I ignore it.
      singulars
      1. POJAX-WS client causes Jetty EofException
      1. UStrojanfoe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload