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.o
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,
Ru
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 mean
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 er
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 ha
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.
