Error message
[HSF-Provider] The method to be called cannot be found.This error occurs on the provider side when a consumer calls a method that the provider cannot resolve. It typically indicates a mismatch between the consumer's request and the provider's published service interface.
Possible causes
| Cause | Description |
|---|---|
| Method not published | The provider has not published the service or the specific method that the consumer is calling. |
| Version mismatch | Multiple versions of the same service coexist, and the consumer is calling the wrong version. |
| Interface type mismatch | The provider and consumer define the same method parameter with different types, such as java.lang.Double on the provider and double on the consumer. |
| Inconsistent interface classes | The provider and consumer load different versions of the interface class, even though the class name is the same. |
Troubleshooting
Work through the following causes in order.
Cause 1: Method not published
The provider has not published the service that the consumer is trying to call.
Diagnose
Log on to the EDAS console.
In the left-side navigation pane, click Application Management.
Click the name of the provider application.
On the Application Details page, click Services in the left-side navigation pane.
Verify that the target service appears in the list and is published.
Resolve
If the service is missing, publish it from the provider application. The consumer can retry the call after the service is published.
Cause 2: Version mismatch
Multiple versions of the same service coexist, and the consumer calls a version that does not contain the expected method.
Diagnose
Follow the steps in Cause 1 to open the Services page for the provider application.
Note the version number of each published service.
Compare the version numbers against the version that the consumer is configured to call.
Resolve
Update the consumer's service reference to specify the correct version.
Cause 3: Interface type mismatch
The provider and consumer define the same method parameter with different Java types. For example, the provider uses java.lang.Double (boxed type) while the consumer uses double (primitive type).
Diagnose
Compare the method signatures in the provider's interface JAR with those in the consumer's interface JAR. Make sure every parameter type matches exactly, including boxed versus primitive types.
Resolve
Align the interface definitions so that both the provider and the consumer use the same parameter types.
Cause 4: Inconsistent interface classes
The provider and consumer load different compiled versions of the same interface class. Even when the source code looks identical, a separate build can produce a different class file.
Diagnose
Compare the MD5 checksums of the interface JAR files on the provider and consumer to confirm they are identical:
# On the provider host
md5sum /path/to/provider/lib/<interface-jar-name>.jar
# On the consumer host
md5sum /path/to/consumer/lib/<interface-jar-name>.jarReplace <interface-jar-name> with the actual name of the JAR file that contains the shared service interface.
If the checksums differ, the provider and consumer are running different versions of the interface.
Resolve
Rebuild the interface JAR from a single source and deploy the same artifact to both the provider and the consumer.