Skip to main content

AKKA-actor DynamicImport-Package: * header

When OSGi modules are fabricated so that they have limited dependencies to other modules, the development process is a breeze. Changes to any single module reflect to a limited set of other modules which enables easy deployment and update of the running software. In the Karaf based project I'm working on, this is mostly the case: updating for example a bundle which is responsible for a certain UI view, only the corresponding view goes down for a couple of milliseconds and the page is automatically refreshed after that.

We started seeing exceptions to this on places where there should not have been any "core" dependencies. When upgrading for example a bundle which exports message/model classes which are part of the Akka communication between the bundles, sometimes the whole karaf seems to go down. The message classes can be used by multiple bundles including the core ones but we started seeing this behavior happening when deploying also non-core Akka message bundles. What made matters worse, it seemed to happen at random - sometimes most bundles go down, sometimes not.

We tracked the reason down to the restarts to akka-actor bundle. The whole actor system (which we have only one in the whole OSGi container) restarted. Using Karaf command bundle:tree-list we saw that the Akka bundle had become dependent on the Akkamessage bundles + some others. This was something that was not supposed to happen. Akka-actor bundle is a core bundle which other bundles should depend on, not the other way around.

After more digging into the cause, we came across an interesting line in the akka-actor bundle manifest file.  DynamicImport-Package: *. Upon further investigation we confirmed that this indeed was causing the dependencies going the wrong way around. In other words, cyclic dependencies. More on dynamic imports in this blog post http://swexplorations.blogspot.fi/2014/07/osgi-dynamic-imports.html

All messages that went through Akka actors that were on a bundles export-package list were causing akka-actor bundle to become dependent on it. First thought was that this is normal, perhaps this is how Akka works. For some reason it might need to import the actual class. But what struck odd is that also messages that were not in a bundle export package list were working fine with the actor system.

Next action was to remove the dynamic import manifest header. That caused akka-actor bundle to not find some class thus preventing the actor system going up. The solution for that was to replace the DynamicImport-Package: * with DynamicImport-Package: akka,akka.* Now actor system went up and also all messages passed through it normally. We did not find anything that was out of the ordinary. We can now also deploy bundles more safely and no core bundles go down when Akka message containing bundles are deployed.


tl;dr akka-actor bundle has DynamicImport-Package: * which causes it to become dependent on bundles exporting messages passing through the actor system.

EDIT: Found the "problem". When a message passes through akka serialization, it will get dynamically imported.

Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker

Careful with externalTrafficPolicy

On a project I am working on is hosted in an EKS cluster with the NGINX ingress controller (the one maintained by Kubernetes). It is deployed using it's official official Helm chart, which I realized, after a lengthy debugging session, was a mistake. The initial setup I aimed to improve had several flaws. Firstly, we were using the AWS Classic Load Balancer in front of the nginx ingress in the cluster, which has been deprecated for some time (years?). Continuing to use it makes little sense to us. The second issue was that we were only running one(!) nginx pod, which is quite sketchy since the exposed web services had essentially no high availability.  I switched to the Network Load Balancer (NLB), which was straightforward - I just needed to change the ingress-nginx service annotation to specify the load balancer type as NLB: service.beta.kubernetes.io/aws-load-balancer-type: nlb However, increasing the replica count turned out to be tricky. When I bumped it up to two, I began to ...