Arkadiusz Daniluk created ACE-598:
-------------------------------------
Summary: Exported client as JAR throws exceptions
Key: ACE-598
URL: https://issues.apache.org/jira/browse/ACE-598
Project: ACE
Issue Type: Question
Components: Build
Affects Versions: 2.1.0
Reporter: Arkadiusz Daniluk
Priority: Minor
Hi,
I'm experiencing some issues with exported client and server-allinone as
executable jars (I did it via BND tool export option).
It works well when run from eclipse but exported jars throws some exceptions:
{code}
ERROR: Bundle org.apache.ace.consolelogger [31] EventDispatcher: Error during
dispatch. (java.lang.IllegalStateException: Invalid BundleContext.)
java.lang.IllegalStateException: Invalid BundleContext.
at
org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:511)
at
org.apache.felix.framework.BundleContextImpl.ungetService(BundleContextImpl.java:475)
at org.apache.felix.dm.Logger.serviceChanged(Logger.java:221)
at
org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:987)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
at
org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4560)
at org.apache.felix.framework.Felix.access$000(Felix.java:106)
at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:419)
at
org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:170)
at
org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:144)
at
org.apache.felix.framework.ServiceRegistry.unregisterServices(ServiceRegistry.java:235)
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2629)
at org.apache.felix.framework.Felix.updateBundle(Felix.java:2338)
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:995)
at aQute.launcher.Launcher.installEmbedded(Launcher.java:646)
at aQute.launcher.Launcher.update(Launcher.java:427)
at aQute.launcher.Launcher.activate(Launcher.java:381)
at aQute.launcher.Launcher.run(Launcher.java:275)
at aQute.launcher.Launcher.main(Launcher.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at aQute.launcher.pre.EmbeddedLauncher.main(EmbeddedLauncher.java:45)
{code}
and
{code}
ERROR: [main] Error processing tasks (java.lang.LinkageError: loader constraint
violation: when resolving overridden method
"org.apache.ace.webui.vaadin.VaadinServlet.init(Ljavax/servlet/ServletConfig;)V"
the class loader (instance of
org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) of the
current class, org/apache/ace/webui/vaadin/VaadinServlet, and its superclass
loader (instance of
org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5), have
different Class objects for the type javax/servlet/ServletConfig used in the
signature)
java.lang.LinkageError: loader constraint violation: when resolving overridden
method
"org.apache.ace.webui.vaadin.VaadinServlet.init(Ljavax/servlet/ServletConfig;)V"
the class loader (instance of
org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) of the
current class, org/apache/ace/webui/vaadin/VaadinServlet, and its superclass
loader (instance of
org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5), have
different Class objects for the type javax/servlet/ServletConfig used in the
signature
at java.lang.Class.getDeclaredConstructors0(Native Method)
{code}
in version 2.0.1 I did not encounter those issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
