Log Plugin: implementing onModule by the type is not of Module type – How To Solve Related Issues


Log Plugin: implementing onModule by the type is not of Module type – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Plugin: implementing onModule by the type is not of Module type ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log context

Log “Plugin: {} implementing onModule by the type is not of Module type {}” classname is PluginsService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     logger.warn("Plugin: {} implementing onModule with no parameters or more than one parameter"; plugin.name());
                    continue;
                }
                Class moduleClass = method.getParameterTypes()[0];
                if (!Module.class.isAssignableFrom(moduleClass)) {
                    logger.warn("Plugin: {} implementing onModule by the type is not of Module type {}"; plugin.name(); moduleClass);
                    continue;
                }
                list.add(new OnModuleReference(moduleClass; method));
            }
            if (!list.isEmpty()) {




 

Optimize Elasticsearch Performance

Try The Tool