Embedded elasticsearch on Websphere Z/OS?


(binoyaf) #1

hi,

I am trying to get elasticsearch to work in an embedded mode inside a websphere application server (V8.5.0.1) on Z/OS. After startup, it keeps logging the below error trace and the CPU spikes to 100%.

  • [ZOSB] version[1.0.0], pid[50397324], build[a46900e/2014-02-12T16:18:34Z]
  • [ZOSB] initializing ...
  • [ZOSB] loaded [], sites []
  • [ZOSB] initialized
  • [ZOSB] starting ...
  • [ZOSB] bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/10.1.99.130:9300]}
  • [ZOSB] exception caught on transport layer [[id: 0x504824fd, /10.1.99.130:25601 => /10.1.99.130:9300]], closing connection
    java.io.IOException: EDC5112I Resource temporarily unavailable. (errno2=0x05230138)
    at sun.nio.ch.FileDispatcher.preClose0(Native Method)
    at sun.nio.ch.SocketDispatcher.preClose(SocketDispatcher.java:53)
    at sun.nio.ch.SocketChannelImpl.implCloseSelectableChannel(SocketChannelImpl.java:730)
    at java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel(AbstractSelectableChannel.java:212)
    at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChannel.java:108)
    at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:353)
    at org.elasticsearch.common.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:58)
    at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:574)
    at org.elasticsearch.common.netty.channel.Channels.close(Channels.java:812)
    at org.elasticsearch.common.netty.channel.AbstractChannel.close(AbstractChannel.java:197)
    at org.elasticsearch.transport.netty.NettyTransport$NodeChannels.closeChannelsAndWait(NettyTransport.java:944)
    at org.elasticsearch.transport.netty.NettyTransport$NodeChannels.close(NettyTransport.java:934)
    at org.elasticsearch.transport.netty.NettyTransport.disconnectFromNode(NettyTransport.java:793)
    at org.elasticsearch.transport.TransportService.disconnectFromNode(TransportService.java:137)
    at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$2$1.run(UnicastZenPing.java:186)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
    at java.lang.Thread.run(Thread.java:772)

Environment details-
java version "1.6.0"
Java(TM) SE Runtime Environment (build pmz6460_26sr3-20120810_01(SR3))
IBM J9 VM (build 2.6, JRE 1.6.0 z/OS s390x-64 20120809_118944 (JIT enabled, AOT enabled)
J9VM - R26_Java626_SR3_20120809_1152_B118944
JIT - r11.b01_20120808_24925
GC - R26_Java626_SR3_20120809_1152_B118944
J9CL - 20120809_118944)
JCL - 20120713_01

Elasticsearch version: 1.0.0

At first guess, I think this has something to do with the IBM SDK version. There is a defect with a similar stack trace listed on IBM - http://www-01.ibm.com/support/docview.wss?uid=swg1IV50158. It is fixed in versions 6.0.15.1, 6.1.7.1 and 7.0.6.1. However, these versions are not available for Websphere on Z/OS currently.

I tried the same version of the SDK on Windows 64-bit and it started up fine. Do you have any pointers on what might be causing this issue?

Thanks,
Binoy


(system) #2