This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
See exception in attachmet. This seem not like an issue from the JDBC module because the exception is thrown when instantiating jdbcwizard action, the action is defined in layers, so why it is instantiated when the module is already disabled? Seems to me like race condition.
Created attachment 1766 [details] an exception
It is a race condition (AFAIK), but is not solvable with the current JDBC module code; the action is created from instance, begins to be recognized in some other thread slowly, then the module is disabled, the classloader is removed from the system class loader, then the action is initialized and tries to load its bundle from the systemClassLoader, which is not found. There is no way to solve that except by loading the bundle directly from the same class loader, which ought to be OK. In general you cannot be assured that code from your module will be loadable from the systemClassLoader unless you control when this loading happens, since it may be that your module has just been uninstalled. So JdbcWizardAction should instead of this: NbBundle.getBundle("org.netbeans.modules.jdbc.wizard.Bundle") use this: NbBundle.getBundle("...", Locale.getDefault(), JdbcWizardAction.class.getClassLoader()) or more simply, avoid using the static bundle and directly call NbBundle.getMessage(JdbcWizardAction.class, ...) which is the recommended usage anyway.
I tried the recommended fix and it worked. It will be fixed in JDBC module ASAP.
I verified the fix provided by Filip and it seems to work.
BTW this was probably duplicate of a core bug that was recently fixed. NbBundle with String args should be fine unless the module is in the process of being uninstalled, which is obscure.
Resolved for 3.4.x or earlier, no new info since then -> closing.