Running Wisdom Application on OpenShift

[Clement Escoffier]

Hi,

You can easily run your Wisdom application on OpenShift. Here is how:

https://github.com/cescoffier/openshift-wisdom-welcome/tree/master

The app is there: http://welcome-wisdomframework.rhcloud.com/ (just the generated application).

Have fun !

Cheers,

Clement

[Antoine Mischler]

Hi Clement,

I'm trying to run a simple wisdom application on OpenShift.

The application is started using the following start hook :

export JVM_ARGS="-Dhttp.port=$OPENSHIFT_DIY_PORT -Dhttp.address=$OPENSHIFT_DIY_IP"

cd $OPENSHIFT_REPO_DIR/diy/

sh ./chameleon.sh

The application starts fine but the vert.x is unable to connect to the $OPENSHIFT_DIY_PORT (8080 in my case). Any idea where this could come from?

I'm using wisdom 0.9.1.

[INFO] o.w.f.v.WisdomVertxServer {[iPOJO] pool-1-thread-1} - Starting the vert.x server 

[INFO] o.w.f.v.WisdomVertxServer {[iPOJO] pool-1-thread-1} - Configuring default HTTP Server 

[INFO] server-default-http {[iPOJO] pool-1-thread-1} - Starting server default-http 

[ERROR] server-default-http {vert.x-eventloop-thread-0} - Cannot bind on port 8080 (port already used probably) 

java.net.SocketException: Permission denied

at sun.nio.ch.Net.bind0(Native Method) ~[na:1.7.0_91]

at sun.nio.ch.Net.bind(Net.java:463) ~[na:1.7.0_91]

at sun.nio.ch.Net.bind(Net.java:455) ~[na:1.7.0_91]

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.7.0_91]

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.7.0_91]

at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125) ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485) ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1081) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:502) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:487) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:904) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:357) [netty-common-4.0.27.Final.jar:4.0.27.Final]

at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) [netty-transport-4.0.27.Final.jar:4.0.27.Final]

at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111) [netty-common-4.0.27.Final.jar:4.0.27.Final]

at java.lang.Thread.run(Thread.java:745) [na:1.7.0_91]

-- 

Antoine

[Antoine Mischler]

Note: le problème n'apparait pas avec wisdom 0.6.5 qui est la version utilisée dans l'exemple openshift-wisdom-welcome.

La configuration doit elle être adaptée pour les versions plus récentes de wisdom?

-- 

Antoine

Le vendredi 21 novembre 2014 15:25:20 UTC+1, clement escoffier a écrit :

[Clement Escoffier]

Hi,

The permission denied is thrown because you try to connect to the wrong address:port. As the port looks good (8080 is the right internal port for openshift), I guess it’s an interface issue. I will have a look.

Clement

--
You received this message because you are subscribed to the Google Groups "wisdom-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wisdom-discus...@googlegroups.com.
Visit this group at https://groups.google.com/group/wisdom-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/wisdom-discuss/1573275f-c6c7-441a-bbac-da70ee16fc31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.