Hi can you dump the value of ClientBuilder.newClient().getClass()?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-04-14 16:17 GMT+02:00 sgjava <[email protected]>: > Using TomEE 2.0.0 SNAPSHOT and Jersey/Jackson WS client as follows: > > <dependency> > <groupId>org.glassfish.jersey.media</groupId> > <artifactId>jersey-media-json-jackson</artifactId> > <version>2.17</version> > </dependency> > <dependency> > <groupId>org.glassfish.jersey.core</groupId> > <artifactId>jersey-client</artifactId> > <version>2.17</version> > </dependency> > > /** > * JAX-RS client. > */ > private Client client; > > client = ClientBuilder.newClient().register(JacksonFeature.class). > property(ClientProperties.CONNECT_TIMEOUT, 7000). > property(ClientProperties.READ_TIMEOUT, 7000); > > The read operation only times out after 30 seconds because that's what the > service is set to. Basically I have an MDB that calls a REST service, but I > need to control the timeouts on the client side since I do not control the > service. I realize this may not be a TomEE issue, but I figure others have > run across this issue before. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/javax-ws-rs-client-Client-read-timeout-not-working-tp4674416.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
