-
15. Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: NPE on Undertow Server.loopupSecurePort
ctomc Feb 6, 2014 3:13 PM (in response to fcorneli)This happens when you work on 3 things at same time
attached fixed jar.
btw, any chance you can come to freenode irc #wildfly and ping me? it will be faster.
--
tomaz
-
16. Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: NPE on Undertow Server.loopupSecurePort
ctomc Feb 6, 2014 4:27 PM (in response to ctomc)Just to post also here,
we found out the solution to this problem, fix is part of Few undertow subsystem bugfixes by ctomc · Pull Request #5879 · wildfly/wildfly · GitHub I just submitted.
--
tomaz
-
17. Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: NPE on Undertow Server.loopupSecurePort
fcorneli Feb 7, 2014 5:55 AM (in response to ctomc)Tested a few of my apps against the latest WildFly tree. Everything works as expected. Maybe a small remark. For AJP configuration I use:
<ajp-listener name="ajp" socket-binding="ajp" redirect-socket="ajp-ssl"/>
with the additional socket-binding:
<socket-binding name="ajp-ssl" port="443"/>
Now, probably if you use port-offset, this will influence this ajp-ssl external port (wild guess). This should not happen I guess. The ajp-ssl port should remain fixed, despite a port-offset.
-
18. Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: NPE on Undertow Server.loopupSecurePort
ctomc Feb 7, 2014 9:59 AM (in response to fcorneli)Frank Cornelis wrote:
Now, probably if you use port-offset, this will influence this ajp-ssl external port (wild guess). This should not happen I guess. The ajp-ssl port should remain fixed, despite a port-offset.
Yes and no, in most cases port-offset is utilized in domain deployments or in cases where you have more than one server instance running on same machine.
This way you want for ports to be offset-ed as otherwise it complicates your configuration and you cannot share same subsystem config.
-
19. Re: NPE on Undertow Server.loopupSecurePort
ctomc Feb 17, 2014 9:58 AM (in response to ctomc)Just for sake of housekeeping.
This was fixed in 8.0.0.Final, it was an issue how server got ajp listeners port.
Thank you Frank for your help with debugging this issue.