Server error during saving the data

Hello there,
I am new to DHIS2 and therefore I have not much knowledge. So basically what is going on:

  1. Installed local server: Tomcat 9.0, Postgre 11, Java 8_251, DHIS2_2.33.4, OS: Windows 10- 1909
  2. started by creating an Organizational Unit.
  3. after pressing SAVE button server got responsive and showed up following message:
  • WARN 2020-06-24T19:40:09,372 Caught problem during data processing: tail closed (AmqpProvider.java [AmqpProvider :(5):[amqp://127.0.0.1:15672]])
    org.apache.qpid.proton.engine.TransportException: tail closed
    at org.apache.qpid.proton.engine.impl.FrameParser.tail(FrameParser.java:508) ~[proton-j-0.31.0.jar:?]
    at org.apache.qpid.proton.engine.impl.SaslImpl$SwitchingSaslTransportWrapper.tail(SaslImpl.java:802) ~[proton-j-0.31.0.jar:?]
    at org.apache.qpid.proton.engine.impl.HandshakeSniffingTransportWrapper.tail(HandshakeSniffingTransportWrapper.java:84) ~[proton-j-0.31.0.jar:?]
    at org.apache.qpid.proton.engine.impl.TransportImpl.tail(TransportImpl.java:1529) ~[proton-j-0.31.0.jar:?]
    at org.apache.qpid.jms.provider.amqp.AmqpProvider.onData(AmqpProvider.java:841) [qpid-jms-client-0.45.0.jar:?]
    at org.apache.qpid.jms.transports.netty.NettyTcpTransport$NettyTcpTransportHandler.channelRead0(NettyTcpTransport.java:542) [qpid-jms-client-0.45.0.jar:?]
    at org.apache.qpid.jms.transports.netty.NettyTcpTransport$NettyTcpTransportHandler.channelRead0(NettyTcpTransport.java:535) [qpid-jms-client-0.45.0.jar:?]
    at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:931) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:700) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:635) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:552) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1044) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-all-4.1.42.Final.jar:4.1.42.Final]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_251]

Any suggestions?

When you start the tomcat dhis instance, while the instance is starting up, could you share the log report, was there any error reported regarding Amqp, I once had somehow a similar issue it turned out the problem was that the default port assigned to Amqp was already assigned to another process which prevented the Ampq from running, I had to change the Amqp port in dhis.conf file to something else, such as:

amqp.port = 15682

and restart the tomcat instance.

Try to monitor the log while the instance is starting up it might gives you some clues to where the problem might be.

1 Like