Mule部署失败-无法分配请求的地址

Question

我已经开发了一个api，它使用使用oauth 2.0的google api。本接口在本地部署成功，配置如下: 1. 8443端口https。2.重定向url：https://localhost:8082/callback 3.本地授权url：https://localhost:8082/login

在dev server上有相同的配置，但部署失败。(用dev服务器主机名和端口替换localhost保持不变)

Caused by: org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "start" on object: org.mule.module.http.internal.request.DefaultHttpRequesterConfig@397b430b
 at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:242) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:108) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:78) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:146) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:134) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:88) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:141) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:70) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:146) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:62) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:317) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.module.launcher.application.DefaultMuleApplication.start(DefaultMuleApplication.java:139) ~[mule-module-launcher-3.8.6.jar:3.8.6]
 ... 56 more
Caused by: java.net.BindException: Cannot assign requested address
 at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_111]
 at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_111]
 at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_111]
 at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_111]
 at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[?:1.8.0_111]
 at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bindToChannelAndAddress(TCPNIOBindingHandler.java:131) ~[grizzly-framework-2.3.33.jar:2.3.33]
 at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bind(TCPNIOBindingHandler.java:88) ~[grizzly-framework-2.3.33.jar:2.3.33]
 at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:239) ~[grizzly-framework-2.3.33.jar:2.3.33]
 at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:219) ~[grizzly-framework-2.3.33.jar:2.3.33]
 at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:210) ~[grizzly-framework-2.3.33.jar:2.3.33]
 at org.mule.module.http.internal.listener.grizzly.GrizzlyServer.start(GrizzlyServer.java:41) ~[mule-module-http-3.8.6.jar:3.8.6]
 at org.mule.module.http.internal.listener.DefaultHttpListenerConfig.start(DefaultHttpListenerConfig.java:274) ~[mule-module-http-3.8.6.jar:3.8.6]
 at org.mule.module.http.internal.listener.HttpListenerConfigBuilder.build(HttpListenerConfigBuilder.java:68) ~[mule-module-http-3.8.6.jar:3.8.6]
 at org.mule.module.http.api.listener.HttpListenerBuilder.resolveListenerConfig(HttpListenerBuilder.java:276) ~[mule-module-http-3.8.6.jar:3.8.6]
 at org.mule.module.http.api.listener.HttpListenerBuilder.build(HttpListenerBuilder.java:195) ~[mule-module-http-3.8.6.jar:3.8.6]
 at org.mule.module.oauth2.internal.authorizationcode.AuthorizationRequestHandler.init(AuthorizationRequestHandler.java:99) ~[mule-module-oauth-3.8.6.jar:3.8.6]
 at org.mule.module.oauth2.internal.authorizationcode.DefaultAuthorizationCodeGrantType.start(DefaultAuthorizationCodeGrantType.java:246) ~[mule-module-oauth-3.8.6.jar:3.8.6]
 at org.mule.module.http.internal.request.DefaultHttpRequesterConfig.start(DefaultHttpRequesterConfig.java:348) ~[mule-module-http-3.8.6.jar:3.8.6]
 at sun.reflect.GeneratedMethodAccessor594.invoke(Unknown Source) ~[?:?]
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
 at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
 at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:230) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:108) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:78) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:146) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:134) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:88) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:141) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:70) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:146) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:62) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:317) ~[mule-core-3.8.6.jar:3.8.6]
 at org.mule.module.launcher.application.DefaultMuleApplication.start(DefaultMuleApplication.java:139) ~[mule-module-launcher-3.8.6.jar:3.8.6]
 ... 56 more

<http:request-config name="HTTP-GsuiteApi-Request-Configuration" protocol="HTTPS" host="www.googleapis.com" port="443" doc:name="HTTP Request Configuration" > <oauth2:authorization-code-grant-type clientId="${client_id}" clientSecret="${client_secret}" redirectionUrl="https://devserverurl:8082/callback" tlsContext-ref="TLS_Context"> <oauth2:authorization-request authorizationUrl="https://accounts.google.com/o/oauth2/auth" localAuthorizationUrl="https://devserverurl:8082/login" scopes="https://www.googleapis.com/auth/admin.directory.user"/> <oauth2:token-request tokenUrl="https://accounts.google.com/o/oauth2/token"> <oauth2:token-response accessToken="#[json:access_token]"/> </oauth2:token-request> </oauth2:authorization-code-grant-type> </http:request-config>

Answer 1

我们已经看到了同样的错误。我们试图在同一台主机上为两个不同的URL配置两个不同的监听程序。我们的原始监听程序配置为0.0.0.0，它可以工作并绑定到任何地址。将其更改为域名会导致我们看到与您相同的错误。

我们可以通过向windows主机文件(C:\Windows\System32\drivers\etc\hosts)添加一个条目，将域名映射到服务器IP地址或127.0.0.1来修复此问题

很抱歉回复得有点晚，但希望这能帮助到一些人。