[Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
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:
000: 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.
org.wso2.orbit.org.ow2.asm:asm-all[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
Re: [Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
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 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:
> 000: 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.
> org.wso2.orbit.org.ow2.asm:asm-all[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
Re: [Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
Hi Ruwan,
"Bad type on operand stack" typically means a jar which has super type
(interface or super class) has been incompatible due to method/class
signature change. see [1] "A wrong argument is passed to a method".
Cheers,
Ruwan
On Thu, Oct 1, 2015 at 8:28 AM, Ruwan Yatawara wrote:
> 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 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:
>> 000: 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.
>> org.wso2.orbit.org.ow2.asm:asm-all[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
>
>
--
*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com
Re: [Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
Hi Ruwan
see [1] "A wrong argument is passed to a method".
[1]
http://examples.javacodegeeks.com/java-basics/exceptions/java-lang-verifyerror-how-to-solve-verifyerror/
Cheers,
Ruwan
On Thu, Oct 1, 2015 at 9:28 AM, Ruwan Abeykoon wrote:
> Hi Ruwan,
>
> "Bad type on operand stack" typically means a jar which has super type
> (interface or super class) has been incompatible due to method/class
> signature change. see [1] "A wrong argument is passed to a method".
>
> Cheers,
> Ruwan
>
> On Thu, Oct 1, 2015 at 8:28 AM, Ruwan Yatawara wrote:
>
>> 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 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:
>>> 000: 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.
>>> org.wso2.orbit.org.ow2.asm:asm-all[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
>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com
Re: [Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
Yes Ruwan, thanks for the clarification, I guess what is happening here is
that. Somewhere there is an interface mismatch, due to all dependencies
concerned not being compiled in one go. So, we need to figure out which jar
with the mis-aligned interface is the culprit then.
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 Thu, Oct 1, 2015 at 9:42 AM, Ruwan Abeykoon wrote:
> Hi Ruwan
> see [1] "A wrong argument is passed to a method".
>
> [1]
> http://examples.javacodegeeks.com/java-basics/exceptions/java-lang-verifyerror-how-to-solve-verifyerror/
>
> Cheers,
> Ruwan
>
> On Thu, Oct 1, 2015 at 9:28 AM, Ruwan Abeykoon wrote:
>
>> Hi Ruwan,
>>
>> "Bad type on operand stack" typically means a jar which has super type
>> (interface or super class) has been incompatible due to method/class
>> signature change. see [1] "A wrong argument is passed to a method".
>>
>> Cheers,
>> Ruwan
>>
>> On Thu, Oct 1, 2015 at 8:28 AM, Ruwan Yatawara wrote:
>>
>>> 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 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:
000: 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.
org.wso2.orbit.org.ow2.asm:asm-all[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
>>>
>>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Architect,*
>> *WSO2, Inc. http://wso2.com
Re: [Dev] [DEV][DAS][ESB] Failed to initialise synapse after installing DAS features
Hi All, Further analysis, revealed the asm-all jar is exported by analytics components. @DAS-team is there a fix for this? Could you please help us to get this resolved. ./org.wso2.carbon.analytics.datasource.rdbms.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.api_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.datasource_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.activitydashboard.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.stream.persistence.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.eventtable_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.messageconsole.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.messageconsole_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.spark.event_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.spark_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.core_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.core.server_1.0.4/feature.xml: ./org.wso2.carbon.analytics.core.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.api.client_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.api.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.webservice_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.activitydashboard_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.eventsink.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.datasource.cassandra.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.datasource.hbase.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.spark.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.eventsink_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 ./org.wso2.carbon.analytics.webservice.server_1.0.4/META-INF/DEPENDENCIES: - asm-all 4.1.0.wso2v1 Library (http://wso2.org) org.wso2.orbit.org.ow2.asm:asm-all:bundle:4.1.0.wso2v1 Thanks & Regards, /charithag On Thu, Oct 1, 2015 at 10:16 AM, Ruwan Yatawara wrote: > Yes Ruwan, thanks for the clarification, I guess what is happening here is > that. Somewhere there is an interface mismatch, due to all dependencies > concerned not being compiled in one go. So, we need to figure out which jar > with the mis-aligned interface is the culprit then. > > 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 Thu, Oct 1, 2015 at 9:42 AM, Ruwan Abeykoon wrote: > >> Hi Ruwan >> see [1] "A wrong argument is passed to a method". >> >> [1] >> http://examples.javacodegeeks.com/java-basics/exceptions/java-lang-verifyerror-how-to-solve-verifyerror/ >> >> Cheers, >> Ruwan >> >> On Thu, Oct 1, 2
