The error "java.lang.VerifyError: Bad type on operand stack" can pop up, when all jars are not compiled from a one particular major version of the language.
As seen below, the released version of ASM has been compiled with java 6. I am not sure as to how this is the case, as the bundle seems to have been released on top of GIT. ./asm-all_4.1.0.wso2v1.jar.unzip/META-INF/MANIFEST.MF:Build-Jdk: 1.6.0_33 ESB does not use the jar, but IOT does. However, when going through the versions with which all jars have been compiled with, ASM is not the only one that has been compiled with JAVA 6. So, i am not sure as to why this particular jar is giving this problem. Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Wed, Sep 30, 2015 at 6:47 PM, Ayyoob Hamza <ayy...@wso2.com> wrote: > Hi All, > When we install DAS features to CDMF(This already have the APIM features), > found a weird fatal exception which failed to start the synapse. > > [2015-09-30 18:23:51,439] INFO > {org.wso2.carbon.mediation.initializer.ServiceBusInitializer} - Starting > ESB... > [2015-09-30 18:23:51,459] INFO > {org.wso2.carbon.mediation.initializer.ServiceBusInitializer} - > Initializing Apache Synapse... > [2015-09-30 18:23:51,474] FATAL > {org.wso2.carbon.mediation.initializer.ServiceBusInitializer} - Failed to > initialize ESB due to a fatal error > java.lang.VerifyError: Bad type on operand stack > Exception Details: > Location: > > org/apache/synapse/config/SynapseConfigUtils.getURLConnection(Ljava/net/URL;)Ljava/net/URLConnection; > @289: invokevirtual > Reason: > Type 'java/lang/Object' (current frame, stack[0]) is not assignable to > 'java/net/URLConnection' > Current Frame: > bci: @289 > flags: { } > locals: { 'java/net/URL', 'java/lang/Object', 'java/util/Properties', > 'java/lang/String', 'java/lang/String', 'java/util/List', > 'java/lang/String', 'java/lang/String', 'java/lang/String', '[B', > 'java/lang/String' } > stack: { 'java/lang/Object', 'java/lang/String', 'java/lang/String' } > Bytecode: > 0000000: 2ac7 001a b200 01b9 0020 0100 9900 0db2 > > So when digged through the cause of this exception, I was able re-produce > this error by only installing the analytics-core feature[1]. Further I was > able find that the below bundle caused this exception. > <bundleDef>org.wso2.orbit.org.ow2.asm:asm-all</bundleDef>[2] > > This can also be produced on the ESB 4.9.0 by installing the > analytics-core feature. > > The above exception was solved by deleting the above (asm-all) dependency > on the pack. > > I wonder why this dependency is causing the synapse failure ?. Any > thoughts on this would be helpful. > > [1] > https://github.com/wso2/carbon-analytics/blob/master/features/analytics-core/org.wso2.carbon.analytics.core.server.feature/pom.xml > [2] https://github.com/wso2/orbit/blob/master/asm/4.1.0.wso2v1/pom.xml > > > Thanks > *Ayyoob Hamza* > *Software Engineer* > WSO2 Inc.; http://wso2.com > email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495> > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
