You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by goutamknit <go...@gmail.com> on 2019/12/07 18:48:02 UTC

Re: Building Errors

Hi 
I am trying to build ActiveMQ 5.15.10 
I too get lot of Error and warning, but at the end build is successful.
java.lang.ArrayIndexOutOfBoundsException: 18
        at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:448)
        at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:369)
        at aQute.lib.osgi.Clazz.parseClassFileWithCollector(Clazz.java:359)
        at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:349)
        at aQute.lib.osgi.Analyzer.analyzeJar(Analyzer.java:1725)
        at
aQute.lib.osgi.Analyzer.analyzeBundleClasspath(Analyzer.java:1595)
        at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:124)
        at aQute.lib.osgi.Builder.analyze(Builder.java:306)
        at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:301)
        at aQute.lib.osgi.Builder.build(Builder.java:73)
        at
org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:547)
        at
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:347)
        at
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:264)
        at
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:255)
        at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
        at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
        at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
        at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
        at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
        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:497)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
        at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

I googled it and i found issue was with maven-bundle-plugin-version - 2.3.7.
So i tried to build with maven-bundle-plugin-version 2.4.0 or higher.
But i found following status and this is due to fact that Generic JMS Pool
jar is empty.
log2.txt <http://activemq.2283324.n4.nabble.com/file/t379735/log2.txt>  

INFO] ActiveMQ ........................................... SUCCESS [  5.227
s]
[INFO] ActiveMQ :: Openwire Generator ..................... SUCCESS [  7.212
s]
[INFO] ActiveMQ :: Client ................................. SUCCESS [ 39.985
s]
[INFO] ActiveMQ :: Openwire Legacy Support ................ SUCCESS [ 14.285
s]
[INFO] ActiveMQ :: JAAS ................................... SUCCESS [  9.044
s]
[INFO] ActiveMQ :: Broker ................................. SUCCESS [ 20.703
s]
[INFO] ActiveMQ :: KahaDB Store ........................... SUCCESS [ 13.532
s]
[INFO] ActiveMQ :: STOMP Protocol ......................... SUCCESS [  8.395
s]
[INFO] ActiveMQ :: MQTT Protocol .......................... SUCCESS [  8.331
s]
[INFO] ActiveMQ :: JDBC Store ............................. SUCCESS [  6.715
s]
[INFO] ActiveMQ :: LevelDB Store .......................... SUCCESS [01:42
min]
[INFO] ActiveMQ :: Generic JMS Pool ....................... SUCCESS [  5.626
s]
[INFO] ActiveMQ :: Pool ................................... FAILURE [  1.457
s]
[INFO] ActiveMQ :: RA ..................................... SKIPPED
[INFO] ActiveMQ :: Spring ................................. SKIPPED

Please help to resolve this build error.

Thanks
Goutam Giri



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

Re: Building Errors

Posted by Arthur Naseef <ar...@amlinv.com>.
You should not see any problems with mixing versions.  With that said,
please test before rolling out to production.  In our history, we have had
a couple of unintentional version-mismatch issues arise, so they are very
rare, but not impossible.

Art


On Thu, Apr 30, 2020 at 4:04 AM goutamknit <go...@gmail.com> wrote:

> HI,
>
> We are going to upgrade activemq 5.14.5 to 5.15.5 . To understand
> compatibillity matrix between client and broker i search on documentation
> but do not found any thing.
> So can we have broker on 5.14.5 and client on 5.15.5 vice-versa, do we have
> issue with that?
>
> Any reference of documentation will be helpfull.
>
> Thanks
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>

Re: Building Errors

Posted by goutamknit <go...@gmail.com>.
HI,
 
We are going to upgrade activemq 5.14.5 to 5.15.5 . To understand
compatibillity matrix between client and broker i search on documentation
but do not found any thing.
So can we have broker on 5.14.5 and client on 5.15.5 vice-versa, do we have
issue with that?

Any reference of documentation will be helpfull.

Thanks



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

Re: Building Errors

Posted by goutamknit <go...@gmail.com>.
Hi Jean, 
Thank you for the update. Is there any time line when we can expect release
of 5.16.0.
Also if possible can you share the commit id about the fix in 5.16.0
version.

Thanks
GG



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

Re: Building Errors

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

I already fix it for 5.16.0 (it's on a local branch) upgrading to
maven-bundle-plugin 4.2.1.

I didn't upgrade on the 5.15.x branch as it requires changes on the OSGi
headers.

I will push the PR soon.

Regards
JB

On 07/12/2019 19:48, goutamknit wrote:
> Hi 
> I am trying to build ActiveMQ 5.15.10 
> I too get lot of Error and warning, but at the end build is successful.
> java.lang.ArrayIndexOutOfBoundsException: 18
>         at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:448)
>         at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:369)
>         at aQute.lib.osgi.Clazz.parseClassFileWithCollector(Clazz.java:359)
>         at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:349)
>         at aQute.lib.osgi.Analyzer.analyzeJar(Analyzer.java:1725)
>         at
> aQute.lib.osgi.Analyzer.analyzeBundleClasspath(Analyzer.java:1595)
>         at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:124)
>         at aQute.lib.osgi.Builder.analyze(Builder.java:306)
>         at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:301)
>         at aQute.lib.osgi.Builder.build(Builder.java:73)
>         at
> org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:547)
>         at
> org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:347)
>         at
> org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:264)
>         at
> org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:255)
>         at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
>         at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
>         at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
>         at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>         at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>         at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>         at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
>         at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
>         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:497)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
>         at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> 
> I googled it and i found issue was with maven-bundle-plugin-version - 2.3.7.
> So i tried to build with maven-bundle-plugin-version 2.4.0 or higher.
> But i found following status and this is due to fact that Generic JMS Pool
> jar is empty.
> log2.txt <http://activemq.2283324.n4.nabble.com/file/t379735/log2.txt>  
> 
> INFO] ActiveMQ ........................................... SUCCESS [  5.227
> s]
> [INFO] ActiveMQ :: Openwire Generator ..................... SUCCESS [  7.212
> s]
> [INFO] ActiveMQ :: Client ................................. SUCCESS [ 39.985
> s]
> [INFO] ActiveMQ :: Openwire Legacy Support ................ SUCCESS [ 14.285
> s]
> [INFO] ActiveMQ :: JAAS ................................... SUCCESS [  9.044
> s]
> [INFO] ActiveMQ :: Broker ................................. SUCCESS [ 20.703
> s]
> [INFO] ActiveMQ :: KahaDB Store ........................... SUCCESS [ 13.532
> s]
> [INFO] ActiveMQ :: STOMP Protocol ......................... SUCCESS [  8.395
> s]
> [INFO] ActiveMQ :: MQTT Protocol .......................... SUCCESS [  8.331
> s]
> [INFO] ActiveMQ :: JDBC Store ............................. SUCCESS [  6.715
> s]
> [INFO] ActiveMQ :: LevelDB Store .......................... SUCCESS [01:42
> min]
> [INFO] ActiveMQ :: Generic JMS Pool ....................... SUCCESS [  5.626
> s]
> [INFO] ActiveMQ :: Pool ................................... FAILURE [  1.457
> s]
> [INFO] ActiveMQ :: RA ..................................... SKIPPED
> [INFO] ActiveMQ :: Spring ................................. SKIPPED
> 
> Please help to resolve this build error.
> 
> Thanks
> Goutam Giri
> 
> 
> 
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> 

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com