We are still using Carbon 4.3.0 in IS. Since carbon-commons is still in
Carbon 4.3.0, there were issue building with 4.4.0-SNAPSHOT.
Regards,
Prasad.
On Thu, Mar 19, 2015 at 12:40 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
We have added these changes to current kernel master
We have added these changes to current kernel master branch.
@IS-Team/Prasad,
Can you guys do a verification of startup CNF issues with IS pack? Please
use the current kernel version from master branch (4.4.0-SNAPSHOT).
On Thu, Mar 19, 2015 at 11:01 AM, Kishanthan Thangarajah
So the solution for this issue is to separate the web socket related
packages/resources from tomcat orbit and create a new orbit for
tomcat-websocket. This new orbit will use the SPI Fly based approach to
register its SPI for ServletContainerInitializer.
There has already been some work carried
Can't we create a separate orbit for tomcat-websocket, that includes this
ServletContainerInitializer? Or do we need to have it within tomcat orbit
itself?
On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe kas...@wso2.com wrote:
Hi Kishanthan,
On Tue, Mar 17, 2015 at 1:33 PM, Kishanthan
Can we try with the attached tomcat orbit bundle :
https://wso2.org/jira/secure/attachment/36443/tomcat_7.0.52.wso2v5.jar ? I
think the root cause for this is same as what we found with spring bundle.
Tomcat orbit also includes a SPI for
javax.servlet.ServletContainerInitializer. I have removed
Hi Kishanthan,
On Tue, Mar 17, 2015 at 1:33 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Can we try with the attached tomcat orbit bundle :
https://wso2.org/jira/secure/attachment/36443/tomcat_7.0.52.wso2v5.jar ?
I think the root cause for this is same as what we found with spring
The requirement is to have it in the same classloader as tomcat. The SPIs
do not work otherwise.
On Tue, Mar 17, 2015 at 2:10 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Can't we create a separate orbit for tomcat-websocket, that includes this
ServletContainerInitializer? Or do we
Not exactly. SPI's in OSGi environment are loaded using Thread Context
Classloader. See :
http://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html. We can
properly fix SPI's related issues with OSGi only with OSGi ServiceLoader
Mediator Specification (such as SPI Fly).
But to workaround
Yea, with the use of SPI-Fly we can provide support for this. We actually
tested it out, and it works. We haven't introduced SPI-Fly to our platform
yet, hence the thought.
The websocket sample there uses the older Tomcat websocket API. I think we
are yet to update this sample to use the
On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe kas...@wso2.com
wrote:
Yea, with the use of SPI-Fly we can provide support for this. We actually
tested it out, and it works. We haven't introduced SPI-Fly to our
Hi,
On Tue, Mar 17, 2015 at 5:10 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga sag...@wso2.com
wrote:
On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe kas...@wso2.com
wrote:
Yea, with the use of SPI-Fly we can provide support for
On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe kas...@wso2.com wrote:
Yea, with the use of SPI-Fly we can provide support for this. We actually
tested it out, and it works. We haven't introduced SPI-Fly to our platform
yet, hence the thought.
The websocket sample there uses the older
Yes, We tried after downgrading spring version but it didn't solve the
issue.
Sent from my mobile
On Mar 16, 2015 7:50 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
So I think this is not related to spring upgrade. The issue mentioned in :
https://wso2.org/jira/browse/CARBON-14864 is
Issue cannot be observed in IS 5.0.0 with patch0009.
Regards,
Prasad.
On Mon, Mar 16, 2015 at 2:48 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Can you guys check this with IS 5.0.0 also (apply patch0009)? If spring
upgrade is causing the issue, then it should occur when patch0009
So I think this is not related to spring upgrade. The issue mentioned in :
https://wso2.org/jira/browse/CARBON-14864 is actually fixed with the given
fix. This issue seems not related to spring upgrade. You can confirm this
by downgrading the version or removing the spring bundle from carbon
sorry wrong thread. Please ignore my last reply.
thanks,
On Mon, Mar 16, 2015 at 2:57 PM, Supun Malinga sup...@wso2.com wrote:
Hi Manoj,
Can you commit this pls ?.
thanks,
On Mon, Mar 16, 2015 at 2:49 PM, Prasad Tissera pras...@wso2.com wrote:
I'll check and let you know ASAP. Thanks.
Can you guys check this with IS 5.0.0 also (apply patch0009)? If spring
upgrade is causing the issue, then it should occur when patch0009 is
applied on IS 5.0.0.
On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera pras...@wso2.com wrote:
It can be observed in a fresh pack which can be downloaded
I'll check and let you know ASAP. Thanks.
Regards,
Prasad.
On Mon, Mar 16, 2015 at 2:48 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
Can you guys check this with IS 5.0.0 also (apply patch0009)? If spring
upgrade is causing the issue, then it should occur when patch0009 is
applied
Hi AS Team,
Appreciate if we can get this resolved ASAP. This is turning out to be a
blocker for IS 5.1.0 M1 release. Reopened the JIRA as well.
Thanks.
On Sun, Mar 15, 2015 at 9:08 AM, Prasad Tissera pras...@wso2.com wrote:
Hi Kasun,
This issues still seems to be there in
It can be observed in a fresh pack which can be downloaded from jenkins
[1]. Following curl can be used to reproduce the issue.
curl -v -X POST -H Authorization: Basic
NElzcWg1UkcwbEdmalFuY2k3TkNRNnBYTFJrYTo2dmdHTE1FNHdRczhraWttT1FmWWg0Z0hublVh
-H Content-Type:
Hi Kasun,
This issues still seems to be there in spring.framework_3.2.9.wso2v1 even
though the suggested fix has been applied in [1]. Class not found exception
occurred intermittently in IS 5.1.0 pack when calling OAuth endpoints. The
issue has been reported in [2] and has marked as resolved. How
Hi Ratha,
Can you try to reproduce by removing the following jar from patch0009?
repository/components/patches/patch0009/spring.framework_3.1.0.wso2v1.jar
Thanks,
Sameera.
On Wed, Jul 9, 2014 at 6:49 PM, Vijayaratha Vijayasingam rat...@wso2.com
wrote:
Is there any recent change in the
Hi sameera;
Thanks ..looks like this solved the issue..I restarted the server several
times, but haven't faced any issue..
May i know how do you find the root cause? so, we won't disturb core team
to fix these type issues?
thanks
On 14 July 2014 11:53, Sameera Jayasoma same...@wso2.com wrote:
Hi,
Although removing the jar fixed this issue, it will break the cause it was
originally added for right. Do we have a solution/workaround for that?
Thanks,
NuwanD.
On Mon, Jul 14, 2014 at 12:31 PM, Vijayaratha Vijayasingam rat...@wso2.com
wrote:
Hi sameera;
Thanks ..looks like this solved
Hi,
Good catch Sameera. It seems that this issue has occurred since the spring
framework bundle in patch0009 includes a Service-Provider-Interface for
javax.servlet.ServletContainerInitializer. So, I have removed the
META-INF/services/javax.servlet.ServletContainerInitializer from spring
Hi Ratha,
Here is how I found the culprit. :)
First I wanted to make sure that this issue occurs due to changes done to
the platform or to the kernel. To verify this I installed all the patches
from patch0001 to patch0009 to a Carbon kernel instance. But when I start
the kernel I got a Spring
thanks sameera..
On 14 July 2014 14:07, Sameera Jayasoma same...@wso2.com wrote:
Hi Ratha,
Here is how I found the culprit. :)
First I wanted to make sure that this issue occurs due to changes done to
the platform or to the kernel. To verify this I installed all the patches
from
kasun , as you said i tried..after that i get some spring class loading
issue..May be the way edited the jar is wrong..
please commit the fix..we need to build the pack
2014-07-14 16:50:42,213] INFO
{org.wso2.carbon.server.util.PatchUtils.console} - Patch verification
successfully completed
pack which causes above issues can be found here[1]
[1]https://svn.wso2.org/repos/wso2/scratch/chunk13-release/08_07_2014_new/
Thanks.
On 10 July 2014 19:00, Vijayaratha Vijayasingam rat...@wso2.com wrote:
Hi all;
It looks like webapps depend on OSGI bundles and when webapps get
deployed,
Hi all;
It looks like webapps depend on OSGI bundles and when webapps get deployed,
OSGi bundles are not active which causes webapp deployment failure
issues..These webapps currently include Oauth+jaggery webapps.
Please fix this issue at webapp deployer or in the webapps.
At the same time
when i get* java.lang.*
*ClassNotFoundException:
org.wso2.carbon.tomcat.ext.**servlet.DelegationServlet
*issue
here are the osgi out put;
*osgi headers 421*
Bundle headers:
Bnd-LastModified = 1404369790626
Build-Jdk = 1.6.0_45
Built-By = root
Bundle-Description = This bundle contains custom
Is there any recent change in the *core.util module* which causes this
issue?
osgi ls 454
Components in bundle org.wso2.carbon.utils:
ID State Component Name Located in
bundle
155 Active
Sameera/KasunG;
In AM 1.7.1 packs, we are getting[1,2]
Whenever i get the above issue, i checked the
packages/services/components..and i do not see any issue with their status..
Looks like same issue reported already(subj: G-REG 5.0.0-SNAPHOST start-up
failure in Jenkins build)
[1][2014-07-08
33 matches
Mail list logo
