Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-4314

Camel netty binding switchyard quickstart gives wierd output in fuse log

    XMLWordPrintable

Details

    • % %
    • Hide

      Follow instructions in README for Fuse.
      Try invoking mvn exec:java -Pudp for UDP and then mvn exec:java for TCP.

      Then check fuse.log file (attached) in text editor and see that for UDP is everything ok, but for TCP there is "Hello <your message> <lot of NUL's>! ....". In README is mentioned only invoking UDP connection for Fuse, but everything works except of these NUL characters in log. Can we use the TCP for Fuse ? Or it is only for EAP ?

      Show
      Follow instructions in README for Fuse. Try invoking mvn exec:java -Pudp for UDP and then mvn exec:java for TCP. Then check fuse.log file (attached) in text editor and see that for UDP is everything ok, but for TCP there is "Hello <your message> <lot of NUL's>! ...." . In README is mentioned only invoking UDP connection for Fuse, but everything works except of these NUL characters in log. Can we use the TCP for Fuse ? Or it is only for EAP ?
    • Sprint 5 - towards ER2

    Description

      There is also harmless error in fuse/eap log :

      2015-10-30 13:28:37,610 | WARN  | ttyOrderedWorker | NettyConsumer                    | 321 - org.apache.camel.camel-netty - 2.15.1.redhat-621070 | Closing channel as an exception was thrown from Netty. Caused by: [java.io.IOException - Connection reset by peer]
java.io.IOException: Connection reset by peer
	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)[:1.7.0_80]
	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)[:1.7.0_80]
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)[:1.7.0_80]
	at sun.nio.ch.IOUtil.read(IOUtil.java:192)[:1.7.0_80]
	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384)[:1.7.0_80]
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)[320:org.jboss.netty:3.9.6.Final]
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)[320:org.jboss.netty:3.9.6.Final]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_80]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_80]
	at java.lang.Thread.run(Thread.java:745)[:1.7.0_80]

      Attachments

        Activity

          People

            toigaras@redhat.com tomohisa igarashi
            llowinge@redhat.com Lukas Lowinger
            Stefan Veres Stefan Veres
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: