Hello Marco Strauch

Not sure this is the case here, but FYI - you are using CDI 1.2 and if you have two observers bound to the same event, there is no guarantee of observers being ordered in this or that way, hence you should not depend on it.
If you have the possibility to migrate to CDI 2.0, observer ordering via @Priority was introduced. See this chapter in the specification for more information.

It would be good to see some code, do you have a reproducer?
Do you fire the second event from within the first producer? If so, then the reverse order makes sense, as the "create action" actually completes earlier then the lock itself.