Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[websocket] Both Netty and Grizzly issues with URI without port. #111

Closed
jfarcand opened this issue May 15, 2012 · 0 comments
Closed

[websocket] Both Netty and Grizzly issues with URI without port. #111

jfarcand opened this issue May 15, 2012 · 0 comments

Comments

@jfarcand
Copy link
Contributor

The following URI

     ws://petstore-sockets-603596378.us-west-1.elb.amazonaws.com

cause, for Netty:

java.net.ConnectException: Connection refused to ws://petstore-sockets-603596378.us-west-1.elb.amazonaws.com/
    at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:100)
    at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:399)
    at org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:390)
    at org.jboss.netty.channel.DefaultChannelFuture.setFailure(DefaultChannelFuture.java:352)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:409)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:366)
    at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:282)
    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102)
    at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:680)

For Grizzly

2012-05-15 11:55:30,309 [TestNGInvoker-onOpen()] DEBUG com.ning.http.client.providers.grizzly.GrizzlyConnectionsPool - [poll] No existing queue for uri [ws://petstore-sockets-603596378.us-west-1.elb.amazonaws.com:443].
java.lang.IllegalArgumentException: Unknown protocol: ws
    at com.ning.http.client.providers.grizzly.GrizzlyAsyncHttpProvider.getPort(GrizzlyAsyncHttpProvider.java:530)
    at com.ning.http.client.providers.grizzly.GrizzlyAsyncHttpProvider$ConnectionManager.doAsyncConnect(GrizzlyAsyncHttpProvider.java:2301)
    at com.ning.http.client.providers.grizzly.GrizzlyAsyncHttpProvider$ConnectionManager.doAsyncTrackedConnection(GrizzlyAsyncHttpProvider.java:2264)
    at com.ning.http.client.providers.grizzly.GrizzlyAsyncHttpProvider.execute(GrizzlyAsyncHttpProvider.java:233)
    at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:512)
    at com.ning.http.client.AsyncHttpClient$BoundRequestBuilder.execute(AsyncHttpClient.java:230)
    at com.ning.http.client.websocket.netty.NettyTextMessageTest.onOpen(NettyTextMessageTest.java:44)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580)
    at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:36)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:680)
jfarcand added a commit that referenced this issue May 15, 2012
@jfarcand
Fix for #111 https://github.com/sonatype/async-http-client/issues/111
0fbabf0
rlubke added a commit that referenced this issue May 15, 2012
@rlubke
Fix for #111 - [websocket] Both Netty and Grizzly issues with URI wit…
c57b42f 
…hout port.
rlubke added a commit that referenced this issue May 15, 2012
@rlubke
Fix for #111 - [websocket] Both Netty and Grizzly issues with URI wit…
44fb654 
…hout port.
rlubke added a commit that referenced this issue Jun 21, 2012
@rlubke
Merge ahc-1.7.x to master.
e1232e0 
* ahc-1.7.x:
  Fix javadoc warnings.
  Integrate Grizzly 2.2.10.
  Fix for the Grizzly side of #101 : [websocket] onError must not be called when status code is != 101.
  Fix for #111 - [websocket] Both Netty and Grizzly issues with URI without port.
  Incremental fix for #101 [websocket] onError must not be called when status code is != 101. Fix Netty side
  Fix for #111 https://github.com/sonatype/async-http-client/issues/111
  Fix errror with clirr
  Port #102 tests
  Port fix for #102 [websocket] Support redirect
  Bump to the latest Netty release
@rlubke rlubke closed this as completed Jun 28, 2012
cs-workco pushed a commit to cs-workco/async-http-client that referenced this issue Apr 13, 2023
@tomerd
swift 5.1 docker setup (AsyncHttpClient#111)
d84a1da 
motivation: support swift 5.1

changes:
* add docker compose file for swift 5.1, will add CI job once merged
* update swiftformat version to 0.40.12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfarcand @rlubke