Hi Diego,
Apologies for throwing out the post in a hurry before a deep dive.
It turned out to be my configuration issue, and I could able to resolve it now.
The reasons of my problem were;
1. I configured "aspectj" weaver JAR in my build.sbt as follows:
bashScriptExtraDefines += """addJava "-javaagent:${lib_dir}/aspectjweaver-1.8.9.jar""""
But the file name was different when I built the application bundle using universal package bin. Essentially, "-javaagnet" was pointing to a JAR which was not present in that disk location.
2. I also had Kamon akka remote dependency in my classpath:
"io.kamon" %% "kamon-akka-remote" % "0.6.0"
This classpath dependency I removed.
When I fixed the above two configuration, the exception got vanished.
Thanks a lot to you and the user group. I learned these from the past discussions you had in this forum.
Regards,
Manoj