Hi,
Whoever did this change broke the build. Because, integration tests not
running is breaking the build. In case I missed it, is there a mail saying
there's a platform wide axis2 version change happening, and the products
need to be checked?
We are on the verge of a release, and this wasted a lot of time. There
can't be sudden platform breaks on the 'branch'.
Anyway, adding the following fixed the tests. Is this the right fix?
<dependency>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-transport-base</artifactId>
<version>1.1.0-wso2v7</version>
<optional>true</optional>
</dependency>
fixed the issue.
On Mon, May 13, 2013 at 8:00 PM, Kishanthan Thangarajah <kishant...@wso2.com
> wrote:
>
>
>
> On Mon, May 13, 2013 at 1:43 PM, Miyuru Wanninayaka <miy...@wso2.com>wrote:
>
>> Reason is kernel 4.1.0 packs axis2-transport-jms_1.1.0.wso2v7 even kernel
>> 4.1.0 source has transport v8 code.
>>
>> So patching transport v8 codes does not have effect because v7 versions
>> of jars packs by kernel 4.1.0 distribution. We have to change version of
>> transport code in patch0001 to v7 to make patch0001 work.
>>
>
> Yes, the version has to be v7, since the kernel has been released with
> that version.
>
>
>
>>
>> BTW I can see LOTS of components patched inside patch0001 and there are
>> functionality changes, API changes in patch0001 which may become issues in
>> long run.
>>
>> On Mon, May 13, 2013 at 12:58 PM, Dushan Abeyruwan <dus...@wso2.com>wrote:
>>
>>> Guys this still broken, seems like though we applied patch it has not
>>> resloved the JMS issue, I can see the ESB instance now packed with two
>>> versions of JMS axis2-transport-jms_1.1.0.wso2v7
>>> and axis2-transport-jms_1.1.0.wso2v8 appricate a quick response ASAP
>>>
>>>
>>> On Fri, May 10, 2013 at 12:26 PM, Senaka Fernando <sen...@wso2.com>wrote:
>>>
>>>> Builds fine.
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>>
>>>> On Fri, May 10, 2013 at 12:21 PM, Kasun Gajasinghe <kas...@wso2.com>wrote:
>>>>
>>>>> Thanks for fixing the issue Kishanthan.
>>>>>
>>>>>
>>>>> On Fri, May 10, 2013 at 12:14 PM, Kishanthan Thangarajah <
>>>>> kishant...@wso2.com> wrote:
>>>>>
>>>>>> Yes, It was broken with r172001. The reason is the transport modules
>>>>>> were still referring to an old axis2 dependency. Fixed it with r
>>>>>> 172095.
>>>>>>
>>>>>> All,
>>>>>>
>>>>>> When adding new fixes to the patch, you have to built it with the *clean
>>>>>> repo*. This will make sure that the fixes you add doesn't break the
>>>>>> build of the patch and the patch builds independently without any issues.
>>>>>>
>>>>>> Thanks,
>>>>>> Kishanthan.
>>>>>>
>>>>>>
>>>>>> On Fri, May 10, 2013 at 11:56 AM, Senaka Fernando <sen...@wso2.com>wrote:
>>>>>>
>>>>>>> Hi Kasun,
>>>>>>>
>>>>>>> The build is broken with commit r172001. If you do "svn up
>>>>>>> -r172000" and build, it works fine.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Senaka.
>>>>>>>
>>>>>>>
>>>>>>> On Fri, May 10, 2013 at 9:34 AM, Dushan Abeyruwan
>>>>>>> <dus...@wso2.com>wrote:
>>>>>>>
>>>>>>>> Do I ? I am suppose to build from root pom available at patch0001
>>>>>>>> rite?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, May 10, 2013 at 9:18 AM, Kasun Gajasinghe
>>>>>>>> <kas...@wso2.com>wrote:
>>>>>>>>
>>>>>>>>> Hi Duashan,
>>>>>>>>>
>>>>>>>>> Did you build axis2-kernel dependency? It's also available under
>>>>>>>>> the patch0001.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Friday, May 10, 2013, Dushan Abeyruwan wrote:
>>>>>>>>>
>>>>>>>>>> Patch001 not building (when take latest update)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [INFO] Apache Axis2 - Clustering .........................
>>>>>>>>>> SUCCESS [1.339s]
>>>>>>>>>> [INFO] Apache Axis2 - Transport - Base ...................
>>>>>>>>>> FAILURE [1.702s]
>>>>>>>>>> [INFO] Apache Axis2 - Transport - JMS .................... SKIPPED
>>>>>>>>>> [INFO] Apache Axis2 - Transport - MSMQ ................... SKIPPED
>>>>>>>>>> [INFO] Apache Axis2 - Transport - UDP .................... SKIPPED
>>>>>>>>>> [INFO] WSO2 Carbon Kernel Kernel Patch 0001 .............. SKIPPED
>>>>>>>>>> [INFO] axis2.wso2 ........................................ SKIPPED
>>>>>>>>>> [INFO] WSO2 Carbon - Registry Kernel ..................... SKIPPED
>>>>>>>>>> [INFO] WSO2 Carbon - Kernel .............................. SKIPPED
>>>>>>>>>> [INFO] WSO2 Carbon - Application Deployer ................ SKIPPED
>>>>>>>>>> [INFO] WSO2 Carbon - UI .................................. SKIPPED
>>>>>>>>>> [INFO] Distribution-Aggregate ............................ SKIPPED
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] BUILD FAILURE
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [INFO] Total time: 14.015s
>>>>>>>>>> [INFO] Finished at: Fri May 10 06:30:29 IST 2013
>>>>>>>>>> [INFO] Final Memory: 47M/303M
>>>>>>>>>> [INFO]
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>> [ERROR] Failed to execute goal
>>>>>>>>>> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>>>>>>>>>> (default-compile) on project axis2-transport-base: Compilation
>>>>>>>>>> failure:
>>>>>>>>>> Compilation failure:
>>>>>>>>>> [ERROR]
>>>>>>>>>> /home2/dushan/wso2svn/kernal/4.1.0/patches/patch0001/dependencies/transports/modules/base/src/main/java/org/apache/axis2/transport/base/BaseUtils.java:[37,28]
>>>>>>>>>> cannot find symbol
>>>>>>>>>> [ERROR] symbol : class MessageProcessorSelector
>>>>>>>>>> [ERROR] location: package org.apache.axis2.util
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR]
>>>>>>>>>> /home2/dushan/wso2svn/kernal/4.1.0/patches/patch0001/dependencies/transports/modules/base/src/main/java/org/apache/axis2/transport/base/BaseUtils.java:[160,19]
>>>>>>>>>> cannot find symbol
>>>>>>>>>> [ERROR] symbol : variable MessageProcessorSelector
>>>>>>>>>> [ERROR] location: class org.apache.axis2.transport.base.BaseUtils
>>>>>>>>>> [ERROR] -> [Help 1]
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>>>>>>>> with the -e switch.
>>>>>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>>>>>>>> logging.
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] For more information about the errors and possible
>>>>>>>>>> solutions, please read the following articles:
>>>>>>>>>> [ERROR] [Help 1]
>>>>>>>>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>>>>>>>> [ERROR]
>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build
>>>>>>>>>> with the command
>>>>>>>>>> [ERROR] mvn <goals> -rf :axis2-transport-base
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 9, 2013 at 12:48 PM, Kishanthan Thangarajah <
>>>>>>>>>> kishant...@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Yes, since this is not an API change but rather the usage of the
>>>>>>>>>> new API is not updated, you can proceed with normal kernel patching
>>>>>>>>>> process
>>>>>>>>>> as described in [1]. Use patch0001.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Kishanthan.
>>>>>>>>>> [1]
>>>>>>>>>> https://docs.google.com/a/wso2.com/document/d/1Kz6vINXA1j74sM8vb8BE0BSIAUnYJH0BERbJxwxi2xQ/edit
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 9, 2013 at 12:11 PM, Supun Malinga
>>>>>>>>>> <sup...@wso2.com>wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Had a chat with kasung related to this. Seems we have to modify
>>>>>>>>>> the transports.
>>>>>>>>>> Kasung will provide a patch on this.
>>>>>>>>>> I believe we can include this fix into kernel patch0001?.
>>>>>>>>>> Pradeep/Kishanthan is that the recommended way?.
>>>>>>>>>>
>>>>>>>>>> thanks,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 9, 2013 at 9:56 AM, Dushan Abeyruwan <dus...@wso2.com
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>> 13-05-09 09:52:41,588] INFO - JMSListener JMS listener started
>>>>>>>>>> [2013-05-09 09:52:41,743] INFO -
>>>>>>>>>> RegistryEventingServiceComponent Successfully Initialized Eventing on
>>>>>>>>>> Registry
>>>>>>>>>> [2013-05-09 09:52:42,133] INFO - JMXServerManager JMX Service
>>>>>>>>>> URL :
>>>>>>>>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>>>>>>>>> [2013-05-09 09:52:42,134] INFO -
>>>>>>>>>> StartupFinalizerServiceComponent Server : WSO2 Enterprise
>>>>>>>>>> Service Bus-4.7.0
>>>>>>>>>> [2013-05-09 09:52:42,134] INFO -
>>>>>>>>>> StartupFinalizerServiceComponent WSO2 Carbon started in 22 sec
>>>>>>>>>> [2013-05-09 09:52:42,422] INFO - CarbonUIServiceComponent Mgt
>>>>>>>>>> Console URL : https://192.168.1.3:9443/carbon/
>>>>>>>>>> [2013-05-09 09:52:44,240] INFO - LogMediator To:
>>>>>>>>>> /services/ProxyA, WSAction: urn:getQuote, SOAPAction: urn:getQuote,
>>>>>>>>>> MessageID: urn:uuid:5b2bae8d-db37-4248-a0d3-69e8c53b5346, Direction:
>>>>>>>>>> request
>>>>>>>>>> [2013-05-09 09:52:44,245] INFO - TimeoutHandler This engine will
>>>>>>>>>> expire all callbacks after : 120 seconds, irrespective of the timeout
>>>>>>>>>> action, after the specified or optional timeout
>>>>>>>>>> *[2013-05-09 09:52:44,526] ERROR - NativeWorkerPool Uncaught
>>>>>>>>>> exception*
>>>>>>>>>> *java.lang.NoSuchMethodError:
>>>>>>>>>> org.apache.axis2.transport.TransportUtils.getMessageFormatter(Lorg/apache/axis2/context/MessageContext;)Lorg/apache/axis2/transport/MessageFormatter;
>>>>>>>>>> *
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.jms.JMSSender.createJMSMessage(JMSSender.java:350)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSender.java:172)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:154)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:112)
>>>>>>>>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>>>>>>>>> at
>>>>>>>>>> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:185)
>>>>>>>>>> at
>>>>>>>>>> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:167)
>>>>>>>>>> at
>>>>>>>>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>>>>>>>>> at
>>>>>>>>>> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:474)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> ~~--~~
>>>>>>>>> Sending this mail via my phone. Do excuse any typo or short replies
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Dushan Abeyruwan
>>>>>>>> *Senior Software Engineer*
>>>>>>>> *Integration Technologies Team*
>>>>>>>> *Member of Integration MC*
>>>>>>>> *WSO2 Inc. http://wso2.com/*
>>>>>>>> *Mobile:(+94)714408632*
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Senaka Fernando*
>>>>>>> Member - Integration Technologies Management Committee;
>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com*
>>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>>
>>>>>>> E-mail: senaka AT wso2.com
>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>>>>
>>>>>>> *Lean . Enterprise . Middleware
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Kishanthan Thangarajah*
>>>>>> Software Engineer,
>>>>>> Development Technologies Team,
>>>>>> WSO2, Inc.
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> Mobile - +94773426635
>>>>>> Blog - *http://kishanthan.wordpress.com*
>>>>>> Twitter - *http://twitter.com/kishanthan*
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Kasun Gajasinghe*
>>>>> Software Engineer;
>>>>> Development Technologies Team, WSO2 Inc.; http://wso2.com
>>>>>
>>>>> ,
>>>>> *email: **kasung AT spamfree wso2.com
>>>>>
>>>>> ** cell: **+94 (77) 678-0813*
>>>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>>>
>>>>> *
>>>>> *
>>>>> *blog: **http://kasunbg.org* <http://kasunbg.org>
>>>>>
>>>>> *
>>>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>>>>>
>>>>> *
>>>>> *
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Senaka Fernando*
>>>> Member - Integration Technologies Management Committee;
>>>> Technical Lead; WSO2 Inc.; http://wso2.com*
>>>> Member; Apache Software Foundation; http://apache.org
>>>>
>>>> E-mail: senaka AT wso2.com
>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>
>>>> *Lean . Enterprise . Middleware
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Dushan Abeyruwan
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *Member of Integration MC*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)714408632*
>>>
>>
>>
>>
>> --
>> Miyuru Wanninayaka
>> Senior Software Engineer
>> Member, Management Committee - Integration Technologies
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile : +94 77 209 9788
>> Blog : http://miyurudw.blogspot.com
>> Flickr : http://www.flickr.com/photos/miyuru_daminda
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Regards,
Tharindu Mathew
Associate Technical Lead, WSO2 BAM
Member - Data Mgmt. Committee
blog: http://tharindumathew.com/
M: +94777759908
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
