1 Reply Latest reply: Mar 9, 2012 10:06 AM by Ramesh Reddy RSS

NoSuchMethodException from Teiid's ReflectionHelper.findBestMethodWithSignature method

Mark Addleman Expert

In our shared development environment, we occassionally get the following exception from Teiid:

java.lang.NoSuchMethodException: ping

at org.teiid.core.util.ReflectionHelper.findBestMethodWithSignature(ReflectionHelper.java:175)

at org.teiid.core.util.ReflectionHelper.findBestMethodOnTarget(ReflectionHelper.java:92)

at org.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:78)

at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232)

at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:163)

at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:152)

at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210)

at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)

at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)

at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)

at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)

at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)

at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)

at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)

at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545)

at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)

at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)

at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)

at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)

at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)

at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)

at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)

at java.lang.Thread.run(Thread.java:769)

 

I suspect this is due to someone inappropriately connecting to the Teiid admin or jdbc port and sending the text "ping" and, therefore, requires no real investigation.  Can anyone confirm this?