Re: [Dev] We are getting some class not found issues intermittently
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 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 < > kishant...@wso2.com> wrote: > >> 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 out related to this with : >> https://github.com/wso2/carbon4-kernel/pull/190 by Denuwanthi. >> >> We will review and merge they PR to kernel along with above new changes. >> Kernel will not have any web socket related resources, but it will have >> tomcat level support for reading SPI's using OSGi approach. This will be an >> extension for tomcat. >> >> On Tue, Mar 17, 2015 at 5:27 PM, KasunG Gajasinghe >> wrote: >> >>> Hi, >>> >>> On Tue, Mar 17, 2015 at 5:10 PM, Sagara Gunathunga >>> wrote: >>> On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga wrote: > > > On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe > 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 Tomcat websocket API. I >> think we are yet to update this sample to use the Websocket JSR. You can >> try this out by installing the latest examples.war in tomcat. >> > > Wasn't that we had same conversation in past about SPI-Fly, when > Denuwanthi/Rajkumar doing their fast track project ? > Please refer following thread[1], during a review with Azeez we decided to ship SPI-Fly with Carbon/AS. >>> Oh yes, for a mail I sent. :-) >>> >>> We can do this then! >>> >>> [1] - Shipping Aries SPI Fly in AS (was: ServletContainerInitializer for AS) Thanks ! > >> @SupunM, did you find time to merge the new websocket samples to AS? >> > > It's Ok to have samples but I think adding automation test cases for > WebSockets and custom ServletContainerInitializers should get high > priority. > >>> >>> Yep.. +1. >>> >>> >>> > Thanks ! > >> > >> >> Thanks. >> >> >> On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> 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 this, I created a separate orbit for >>> tomcat-websocket and tested on AS. No issues popped up and the web >>> socket >>> sample seems to work fine. This is by completely separating the web >>> socket >>> related packages/resources from main tomcat orbit to a separate one. >>> What >>> more should be tested with this? >>> >>> >>> >>> On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe >>> wrote: >>> 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 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 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 >>> bundle. Tomcat orbit also includes a SPI for " >>> javax.servlet.ServletContainerInitializer". I have removed that >>> from the above attached jar. Let me know the results of this with >>> IS. >>> >>> Also currently IS-5.1.0 uses kernel 4.3.0 >
Re: [Dev] We are getting some class not found issues intermittently
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 < kishant...@wso2.com> wrote: > 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 out related to this with : > https://github.com/wso2/carbon4-kernel/pull/190 by Denuwanthi. > > We will review and merge they PR to kernel along with above new changes. > Kernel will not have any web socket related resources, but it will have > tomcat level support for reading SPI's using OSGi approach. This will be an > extension for tomcat. > > On Tue, Mar 17, 2015 at 5:27 PM, KasunG Gajasinghe > wrote: > >> Hi, >> >> On Tue, Mar 17, 2015 at 5:10 PM, Sagara Gunathunga >> wrote: >> >>> >>> >>> On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga >>> wrote: >>> On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe 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 Tomcat websocket API. I > think we are yet to update this sample to use the Websocket JSR. You can > try this out by installing the latest examples.war in tomcat. > Wasn't that we had same conversation in past about SPI-Fly, when Denuwanthi/Rajkumar doing their fast track project ? >>> >>> Please refer following thread[1], during a review with Azeez we decided >>> to ship SPI-Fly with Carbon/AS. >>> >>> >> Oh yes, for a mail I sent. :-) >> >> We can do this then! >> >> >>> [1] - Shipping Aries SPI Fly in AS (was: ServletContainerInitializer for >>> AS) >>> >>> Thanks ! >>> > @SupunM, did you find time to merge the new websocket samples to AS? > It's Ok to have samples but I think adding automation test cases for WebSockets and custom ServletContainerInitializers should get high priority. >>> >> >> Yep.. +1. >> >> >> >>> Thanks ! > > > Thanks. > > > On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> 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 this, I created a separate orbit for >> tomcat-websocket and tested on AS. No issues popped up and the web socket >> sample seems to work fine. This is by completely separating the web >> socket >> related packages/resources from main tomcat orbit to a separate one. What >> more should be tested with this? >> >> >> >> On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe >> wrote: >> >>> >>> 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 need to have it within tomcat orbit itself? On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe >>> > wrote: > 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 >> bundle. Tomcat orbit also includes a SPI for " >> javax.servlet.ServletContainerInitializer". I have removed that >> from the above attached jar. Let me know the results of this with IS. >> >> Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). >> Can you test and confirm that the above issue is still there with >> kernel >> 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel >> dependency >> version of your distribution. If yes, we may need to do a tomcat >> orbit >> release. >> > > We do need this ServletContainerInitializer inside the tomcat > bundle to g
Re: [Dev] We are getting some class not found issues intermittently
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 out related to this with : https://github.com/wso2/carbon4-kernel/pull/190 by Denuwanthi. We will review and merge they PR to kernel along with above new changes. Kernel will not have any web socket related resources, but it will have tomcat level support for reading SPI's using OSGi approach. This will be an extension for tomcat. On Tue, Mar 17, 2015 at 5:27 PM, KasunG Gajasinghe wrote: > Hi, > > On Tue, Mar 17, 2015 at 5:10 PM, Sagara Gunathunga > wrote: > >> >> >> On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga >> wrote: >> >>> >>> >>> On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe >>> 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 Tomcat websocket API. I think we are yet to update this sample to use the Websocket JSR. You can try this out by installing the latest examples.war in tomcat. >>> >>> Wasn't that we had same conversation in past about SPI-Fly, when >>> Denuwanthi/Rajkumar doing their fast track project ? >>> >> >> Please refer following thread[1], during a review with Azeez we decided >> to ship SPI-Fly with Carbon/AS. >> >> > Oh yes, for a mail I sent. :-) > > We can do this then! > > >> [1] - Shipping Aries SPI Fly in AS (was: ServletContainerInitializer for >> AS) >> >> Thanks ! >> >>> @SupunM, did you find time to merge the new websocket samples to AS? >>> >>> It's Ok to have samples but I think adding automation test cases for >>> WebSockets and custom ServletContainerInitializers should get high >>> priority. >>> >> > > Yep.. +1. > > > >> >>> Thanks ! >>> >>> Thanks. On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < kishant...@wso2.com> wrote: > 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 this, I created a separate orbit for > tomcat-websocket and tested on AS. No issues popped up and the web socket > sample seems to work fine. This is by completely separating the web socket > related packages/resources from main tomcat orbit to a separate one. What > more should be tested with this? > > > > On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe > wrote: > >> >> 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 need to have it within >>> tomcat orbit itself? >>> >>> On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe >>> wrote: >>> 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 > bundle. Tomcat orbit also includes a SPI for " > javax.servlet.ServletContainerInitializer". I have removed that > from the above attached jar. Let me know the results of this with IS. > > Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). > Can you test and confirm that the above issue is still there with > kernel > 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel > dependency > version of your distribution. If yes, we may need to do a tomcat orbit > release. > We do need this ServletContainerInitializer inside the tomcat bundle to get the websocket to work. If you think the cause of the above issue is this SPI, then we have to find and fix the root cause. > > On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera > wrote: > >> 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
Re: [Dev] We are getting some class not found issues intermittently
Hi, On Tue, Mar 17, 2015 at 5:10 PM, Sagara Gunathunga wrote: > > > On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga > wrote: > >> >> >> On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe >> 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 Tomcat websocket API. I think >>> we are yet to update this sample to use the Websocket JSR. You can try this >>> out by installing the latest examples.war in tomcat. >>> >> >> Wasn't that we had same conversation in past about SPI-Fly, when >> Denuwanthi/Rajkumar doing their fast track project ? >> > > Please refer following thread[1], during a review with Azeez we decided to > ship SPI-Fly with Carbon/AS. > > Oh yes, for a mail I sent. :-) We can do this then! > [1] - Shipping Aries SPI Fly in AS (was: ServletContainerInitializer for > AS) > > Thanks ! > >> >>> @SupunM, did you find time to merge the new websocket samples to AS? >>> >> >> It's Ok to have samples but I think adding automation test cases for >> WebSockets and custom ServletContainerInitializers should get high >> priority. >> > Yep.. +1. > >> Thanks ! >> >>> >> >>> >>> Thanks. >>> >>> >>> On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < >>> kishant...@wso2.com> wrote: >>> 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 this, I created a separate orbit for tomcat-websocket and tested on AS. No issues popped up and the web socket sample seems to work fine. This is by completely separating the web socket related packages/resources from main tomcat orbit to a separate one. What more should be tested with this? On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe wrote: > > 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 need to have it within >> tomcat orbit itself? >> >> On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe >> wrote: >> >>> 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 bundle. Tomcat orbit also includes a SPI for " javax.servlet.ServletContainerInitializer". I have removed that from the above attached jar. Let me know the results of this with IS. Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can you test and confirm that the above issue is still there with kernel 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency version of your distribution. If yes, we may need to do a tomcat orbit release. >>> >>> We do need this ServletContainerInitializer inside the tomcat bundle >>> to get the websocket to work. If you think the cause of the above issue >>> is >>> this SPI, then we have to find and fix the root cause. >>> >>> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera wrote: > 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 >> 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 runtime and check. We could still see the >> same >> startup/webapp deployment error. This seems to a typical OSGi class >> loading >> issue. >> >> Need to have a another deep look and see. >> >> On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera > > wrote: >> >>> Issue cannot be observed in IS 5.0.0 with patch0009. >>> >>> Rega
Re: [Dev] We are getting some class not found issues intermittently
On Tue, Mar 17, 2015 at 5:04 PM, Sagara Gunathunga wrote: > > > On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe > 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 Tomcat websocket API. I think >> we are yet to update this sample to use the Websocket JSR. You can try this >> out by installing the latest examples.war in tomcat. >> > > Wasn't that we had same conversation in past about SPI-Fly, when > Denuwanthi/Rajkumar doing their fast track project ? > Please refer following thread[1], during a review with Azeez we decided to ship SPI-Fly with Carbon/AS. [1] - Shipping Aries SPI Fly in AS (was: ServletContainerInitializer for AS) Thanks ! > >> @SupunM, did you find time to merge the new websocket samples to AS? >> > > It's Ok to have samples but I think adding automation test cases for > WebSockets and custom ServletContainerInitializers should get high > priority. > > Thanks ! > >> > >> >> Thanks. >> >> >> On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> 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 this, I created a separate orbit for tomcat-websocket >>> and tested on AS. No issues popped up and the web socket sample seems to >>> work fine. This is by completely separating the web socket related >>> packages/resources from main tomcat orbit to a separate one. What more >>> should be tested with this? >>> >>> >>> >>> On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe >>> wrote: >>> 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 need to have it within > tomcat orbit itself? > > On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe > wrote: > >> 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 >>> bundle. Tomcat orbit also includes a SPI for " >>> javax.servlet.ServletContainerInitializer". I have removed that >>> from the above attached jar. Let me know the results of this with IS. >>> >>> Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). >>> Can you test and confirm that the above issue is still there with kernel >>> 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency >>> version of your distribution. If yes, we may need to do a tomcat orbit >>> release. >>> >> >> We do need this ServletContainerInitializer inside the tomcat bundle >> to get the websocket to work. If you think the cause of the above issue >> is >> this SPI, then we have to find and fix the root cause. >> >> >>> >>> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera >>> wrote: >>> 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 > 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 runtime and check. We could still see the > same > startup/webapp deployment error. This seems to a typical OSGi class > loading > issue. > > Need to have a another deep look and see. > > On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera > wrote: > >> 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 >>
Re: [Dev] We are getting some class not found issues intermittently
On Tue, Mar 17, 2015 at 4:45 PM, KasunG Gajasinghe 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 Tomcat websocket API. I think we > are yet to update this sample to use the Websocket JSR. You can try this > out by installing the latest examples.war in tomcat. > Wasn't that we had same conversation in past about SPI-Fly, when Denuwanthi/Rajkumar doing their fast track project ? > > @SupunM, did you find time to merge the new websocket samples to AS? > It's Ok to have samples but I think adding automation test cases for WebSockets and custom ServletContainerInitializers should get high priority. Thanks ! > > > Thanks. > > > On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> 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 this, I created a separate orbit for tomcat-websocket >> and tested on AS. No issues popped up and the web socket sample seems to >> work fine. This is by completely separating the web socket related >> packages/resources from main tomcat orbit to a separate one. What more >> should be tested with this? >> >> >> >> On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe >> wrote: >> >>> >>> 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 need to have it within tomcat orbit itself? On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe wrote: > 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 >> bundle. Tomcat orbit also includes a SPI for " >> javax.servlet.ServletContainerInitializer". I have removed that from >> the above attached jar. Let me know the results of this with IS. >> >> Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can >> you test and confirm that the above issue is still there with kernel >> 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency >> version of your distribution. If yes, we may need to do a tomcat orbit >> release. >> > > We do need this ServletContainerInitializer inside the tomcat bundle > to get the websocket to work. If you think the cause of the above issue is > this SPI, then we have to find and fix the root cause. > > >> >> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera >> wrote: >> >>> 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 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 runtime and check. We could still see the same startup/webapp deployment error. This seems to a typical OSGi class loading issue. Need to have a another deep look and see. On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera wrote: > 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 is >> applied on IS 5.0.0. >> >> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera > > wrote: >> >>> 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 >>> NElzcWg1UkcwbEdmalFuY2k3Tk
Re: [Dev] We are getting some class not found issues intermittently
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 Websocket JSR. You can try this out by installing the latest examples.war in tomcat. @SupunM, did you find time to merge the new websocket samples to AS? Thanks. On Tue, Mar 17, 2015 at 4:24 PM, Kishanthan Thangarajah wrote: > 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 this, I created a separate orbit for tomcat-websocket > and tested on AS. No issues popped up and the web socket sample seems to > work fine. This is by completely separating the web socket related > packages/resources from main tomcat orbit to a separate one. What more > should be tested with this? > > > > On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe > wrote: > >> >> 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 need to have it within >>> tomcat orbit itself? >>> >>> On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe >>> wrote: >>> 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 > bundle. Tomcat orbit also includes a SPI for " > javax.servlet.ServletContainerInitializer". I have removed that from > the above attached jar. Let me know the results of this with IS. > > Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can > you test and confirm that the above issue is still there with kernel > 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency > version of your distribution. If yes, we may need to do a tomcat orbit > release. > We do need this ServletContainerInitializer inside the tomcat bundle to get the websocket to work. If you think the cause of the above issue is this SPI, then we have to find and fix the root cause. > > On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera > wrote: > >> 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 >>> 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 runtime and check. We could still see the same >>> startup/webapp deployment error. This seems to a typical OSGi class >>> loading >>> issue. >>> >>> Need to have a another deep look and see. >>> >>> On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera >>> wrote: >>> 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 is > applied on IS 5.0.0. > > On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera > wrote: > >> 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: application/x-www-form-urlencoded;charset=UTF-8" >> -k -d >> "grant_type=password&username=admin&password=admin" >> https://localhost:9443/oauth2/token >> >> [1]. >> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip >> >> Regards, >> Prasad. >>>
Re: [Dev] We are getting some class not found issues intermittently
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 this, I created a separate orbit for tomcat-websocket and tested on AS. No issues popped up and the web socket sample seems to work fine. This is by completely separating the web socket related packages/resources from main tomcat orbit to a separate one. What more should be tested with this? On Tue, Mar 17, 2015 at 2:17 PM, KasunG Gajasinghe wrote: > > 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 need to have it within tomcat >> orbit itself? >> >> On Tue, Mar 17, 2015 at 1:52 PM, KasunG Gajasinghe >> wrote: >> >>> 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 bundle. Tomcat orbit also includes a SPI for " javax.servlet.ServletContainerInitializer". I have removed that from the above attached jar. Let me know the results of this with IS. Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can you test and confirm that the above issue is still there with kernel 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency version of your distribution. If yes, we may need to do a tomcat orbit release. >>> >>> We do need this ServletContainerInitializer inside the tomcat bundle to >>> get the websocket to work. If you think the cause of the above issue is >>> this SPI, then we have to find and fix the root cause. >>> >>> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera wrote: > 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" > wrote: > >> 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 runtime and check. We could still see the same startup/webapp >> deployment error. This seems to a typical OSGi class loading issue. >> >> Need to have a another deep look and see. >> >> On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera >> wrote: >> >>> 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 is applied on IS 5.0.0. On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote: > 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: application/x-www-form-urlencoded;charset=UTF-8" -k > -d > "grant_type=password&username=admin&password=admin" > https://localhost:9443/oauth2/token > > [1]. > https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip > > Regards, > Prasad. > > On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> Can we have IS pack with the above issue hosted somewhere, so >> that we could take a look? >> >> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby < >> joh...@wso2.com> wrote: >> >>> 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...
Re: [Dev] We are getting some class not found issues intermittently
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 wrote: > 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 > wrote: > >> 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 >>> bundle. Tomcat orbit also includes a SPI for " >>> javax.servlet.ServletContainerInitializer". I have removed that from >>> the above attached jar. Let me know the results of this with IS. >>> >>> Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can >>> you test and confirm that the above issue is still there with kernel >>> 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency >>> version of your distribution. If yes, we may need to do a tomcat orbit >>> release. >>> >> >> We do need this ServletContainerInitializer inside the tomcat bundle to >> get the websocket to work. If you think the cause of the above issue is >> this SPI, then we have to find and fix the root cause. >> >> >>> >>> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera >>> wrote: >>> 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" wrote: > 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 runtime and check. We could still see the same startup/webapp > deployment error. This seems to a typical OSGi class loading issue. > > Need to have a another deep look and see. > > On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera > wrote: > >> 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 is >>> applied on IS 5.0.0. >>> >>> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera >>> wrote: >>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d "grant_type=password&username=admin&password=admin" https://localhost:9443/oauth2/token [1]. https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip Regards, Prasad. On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < kishant...@wso2.com> wrote: > Can we have IS pack with the above issue hosted somewhere, so that > we could take a look? > > On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby < > joh...@wso2.com> wrote: > >> 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 > > wrote: >> >>> 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 should we proceed in this? Thanks. >>> >>> root cause >>> java.lang.ClassNotFoundException: >>> org.wso2.carbon.identity.oauth.cache.CacheKey >>> >>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) >>> >>> org.apache.catalina.loader.WebappClassLoader.loadClass
Re: [Dev] We are getting some class not found issues intermittently
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 wrote: > 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 >> bundle. Tomcat orbit also includes a SPI for " >> javax.servlet.ServletContainerInitializer". I have removed that from the >> above attached jar. Let me know the results of this with IS. >> >> Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can you >> test and confirm that the above issue is still there with kernel >> 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency >> version of your distribution. If yes, we may need to do a tomcat orbit >> release. >> > > We do need this ServletContainerInitializer inside the tomcat bundle to > get the websocket to work. If you think the cause of the above issue is > this SPI, then we have to find and fix the root cause. > > >> >> On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera wrote: >> >>> 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" >>> wrote: >>> 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 runtime and check. We could still see the same startup/webapp deployment error. This seems to a typical OSGi class loading issue. Need to have a another deep look and see. On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera wrote: > 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 >> is >> applied on IS 5.0.0. >> >> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera >> wrote: >> >>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d >>> "grant_type=password&username=admin&password=admin" >>> https://localhost:9443/oauth2/token >>> >>> [1]. >>> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip >>> >>> Regards, >>> Prasad. >>> >>> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < >>> kishant...@wso2.com> wrote: >>> Can we have IS pack with the above issue hosted somewhere, so that we could take a look? On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby < joh...@wso2.com> wrote: > 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 > wrote: > >> 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 should we proceed in this? Thanks. >> >> root cause >> java.lang.ClassNotFoundException: >> org.wso2.carbon.identity.oauth.cache.CacheKey >> >> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) >> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) >> java.lang.Class.getDeclaredConstructors0(Native Method) >> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) >> java.lang.Class.getConstructor0(Class.java:2708) >> java.lang.Class.getDeclaredConstructor(Class.java:1987) >
Re: [Dev] We are getting some class not found issues intermittently
Hi Kishanthan, On Tue, Mar 17, 2015 at 1:33 PM, Kishanthan Thangarajah 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 > bundle. Tomcat orbit also includes a SPI for " > javax.servlet.ServletContainerInitializer". I have removed that from the > above attached jar. Let me know the results of this with IS. > > Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can you > test and confirm that the above issue is still there with kernel > 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency > version of your distribution. If yes, we may need to do a tomcat orbit > release. > We do need this ServletContainerInitializer inside the tomcat bundle to get the websocket to work. If you think the cause of the above issue is this SPI, then we have to find and fix the root cause. > > On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera wrote: > >> 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" >> wrote: >> >>> 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 >>> runtime and check. We could still see the same startup/webapp deployment >>> error. This seems to a typical OSGi class loading issue. >>> >>> Need to have a another deep look and see. >>> >>> On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera >>> wrote: >>> 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 > is > applied on IS 5.0.0. > > On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera > wrote: > >> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d >> "grant_type=password&username=admin&password=admin" >> https://localhost:9443/oauth2/token >> >> [1]. >> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip >> >> Regards, >> Prasad. >> >> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < >> kishant...@wso2.com> wrote: >> >>> Can we have IS pack with the above issue hosted somewhere, so that >>> we could take a look? >>> >>> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby >> > wrote: >>> 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 wrote: > 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 should we proceed in this? Thanks. > > root cause > java.lang.ClassNotFoundException: > org.wso2.carbon.identity.oauth.cache.CacheKey > > org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) > java.lang.Class.getDeclaredConstructors0(Native Method) > java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) > java.lang.Class.getConstructor0(Class.java:2708) > java.lang.Class.getDeclaredConstructor(Class.java:1987) > > org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65) > > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957) > > org.springframework.beans.factory.support.AbstractAutowireCapableBeanF
Re: [Dev] We are getting some class not found issues intermittently
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 that from the above attached jar. Let me know the results of this with IS. Also currently IS-5.1.0 uses kernel 4.3.0 (tomcat_7.0.52-wso2v5). Can you test and confirm that the above issue is still there with kernel 4.4.0-SNAPSHOT (Beta1) too? You may need to update the kernel dependency version of your distribution. If yes, we may need to do a tomcat orbit release. On Tue, Mar 17, 2015 at 8:40 AM, Prasad Tissera wrote: > 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" > wrote: > >> 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 >> runtime and check. We could still see the same startup/webapp deployment >> error. This seems to a typical OSGi class loading issue. >> >> Need to have a another deep look and see. >> >> On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera wrote: >> >>> 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 is applied on IS 5.0.0. On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote: > 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d > "grant_type=password&username=admin&password=admin" > https://localhost:9443/oauth2/token > > [1]. > https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip > > Regards, > Prasad. > > On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> Can we have IS pack with the above issue hosted somewhere, so that we >> could take a look? >> >> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby >> wrote: >> >>> 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 >>> wrote: >>> 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 should we proceed in this? Thanks. root cause java.lang.ClassNotFoundException: org.wso2.carbon.identity.oauth.cache.CacheKey org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) java.lang.Class.getDeclaredConstructors0(Native Method) java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) java.lang.Class.getConstructor0(Class.java:2708) java.lang.Class.getDeclaredConstructor(Class.java:1987) org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910) [1]. https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87 [2]. https://wso2.org/jira/browse/CARBON-14864 Regards, Prasad. On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun wrote: > Hi Sameera, > > Was this change applied
Re: [Dev] We are getting some class not found issues intermittently
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" wrote: > 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 > runtime and check. We could still see the same startup/webapp deployment > error. This seems to a typical OSGi class loading issue. > > Need to have a another deep look and see. > > On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera wrote: > >> 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 is >>> applied on IS 5.0.0. >>> >>> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera >>> wrote: >>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d "grant_type=password&username=admin&password=admin" https://localhost:9443/oauth2/token [1]. https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip Regards, Prasad. On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < kishant...@wso2.com> wrote: > Can we have IS pack with the above issue hosted somewhere, so that we > could take a look? > > On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby > wrote: > >> 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 >> wrote: >> >>> 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 should we proceed in this? Thanks. >>> >>> root cause >>> java.lang.ClassNotFoundException: >>> org.wso2.carbon.identity.oauth.cache.CacheKey >>> >>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) >>> >>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) >>> java.lang.Class.getDeclaredConstructors0(Native Method) >>> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) >>> java.lang.Class.getConstructor0(Class.java:2708) >>> java.lang.Class.getDeclaredConstructor(Class.java:1987) >>> >>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65) >>> >>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957) >>> >>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910) >>> >>> [1]. >>> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87 >>> [2]. https://wso2.org/jira/browse/CARBON-14864 >>> >>> Regards, >>> Prasad. >>> >>> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun >>> wrote: >>> Hi Sameera, Was this change applied to the 4.3.0 branch on git?. we are getting a similar random server not starting up issue. seems it is the same reason. If this is not already allied can we get this added to 4.3.0 branch. We are trying to fix integration test in greg and this random server hangup is causing a lot of time to be wasted. Regards, Pulasthi On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma >>> > wrote: > Done. > > > > > On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe > wrote: > >> Hi kernel team, >> >> Please commit the patch at [1] for this issue. >> >> [1] https://wso2.org/jira/browse/CARBON-14864 >> >> Thanks,
Re: [Dev] We are getting some class not found issues intermittently
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 runtime and check. We could still see the same startup/webapp deployment error. This seems to a typical OSGi class loading issue. Need to have a another deep look and see. On Mon, Mar 16, 2015 at 3:06 PM, Prasad Tissera wrote: > 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 is >> applied on IS 5.0.0. >> >> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote: >> >>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d >>> "grant_type=password&username=admin&password=admin" >>> https://localhost:9443/oauth2/token >>> >>> [1]. >>> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip >>> >>> Regards, >>> Prasad. >>> >>> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < >>> kishant...@wso2.com> wrote: >>> Can we have IS pack with the above issue hosted somewhere, so that we could take a look? On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby wrote: > 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 > wrote: > >> 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 should we proceed in this? Thanks. >> >> root cause java.lang.ClassNotFoundException: >> org.wso2.carbon.identity.oauth.cache.CacheKey >> >> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) >> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) >> java.lang.Class.getDeclaredConstructors0(Native Method) >> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) >> java.lang.Class.getConstructor0(Class.java:2708) >> java.lang.Class.getDeclaredConstructor(Class.java:1987) >> >> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65) >> >> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957) >> >> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910) >> >> [1]. >> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87 >> [2]. https://wso2.org/jira/browse/CARBON-14864 >> >> Regards, >> Prasad. >> >> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun >> wrote: >> >>> Hi Sameera, >>> >>> Was this change applied to the 4.3.0 branch on git?. we are getting >>> a similar random server not starting up issue. seems it is the same >>> reason. >>> If this is not already allied can we get this added to 4.3.0 branch. We >>> are >>> trying to fix integration test in greg and this random server hangup is >>> causing a lot of time to be wasted. >>> >>> Regards, >>> Pulasthi >>> >>> >>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma >>> wrote: >>> Done. On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe wrote: > Hi kernel team, > > Please commit the patch at [1] for this issue. > > [1] https://wso2.org/jira/browse/CARBON-14864 > > Thanks, > KasunG > > > On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam < > rat...@wso2.com> wrote: > >> tried with kasun's modified spring lib, looks like it is working.. >> >> >> On 14 July 2014 16:54, Vijayaratha Vijayas
Re: [Dev] We are getting some class not found issues intermittently
Issue cannot be observed in IS 5.0.0 with patch0009.
Regards,
Prasad.
On Mon, Mar 16, 2015 at 2:48 PM, Kishanthan Thangarajah 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 on IS 5.0.0.
>
> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote:
>
>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d
>> "grant_type=password&username=admin&password=admin"
>> https://localhost:9443/oauth2/token
>>
>> [1].
>> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip
>>
>> Regards,
>> Prasad.
>>
>> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Can we have IS pack with the above issue hosted somewhere, so that we
>>> could take a look?
>>>
>>> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby
>>> wrote:
>>>
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
wrote:
> 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 should we proceed in this? Thanks.
>
> root cause java.lang.ClassNotFoundException:
> org.wso2.carbon.identity.oauth.cache.CacheKey
>
> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
> java.lang.Class.getDeclaredConstructors0(Native Method)
> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
> java.lang.Class.getConstructor0(Class.java:2708)
> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>
> [1].
> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
> [2]. https://wso2.org/jira/browse/CARBON-14864
>
> Regards,
> Prasad.
>
> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
> wrote:
>
>> Hi Sameera,
>>
>> Was this change applied to the 4.3.0 branch on git?. we are getting a
>> similar random server not starting up issue. seems it is the same reason.
>> If this is not already allied can we get this added to 4.3.0 branch. We
>> are
>> trying to fix integration test in greg and this random server hangup is
>> causing a lot of time to be wasted.
>>
>> Regards,
>> Pulasthi
>>
>>
>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
>> wrote:
>>
>>> Done.
>>>
>>>
>>>
>>>
>>> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
>>> wrote:
>>>
Hi kernel team,
Please commit the patch at [1] for this issue.
[1] https://wso2.org/jira/browse/CARBON-14864
Thanks,
KasunG
On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
rat...@wso2.com> wrote:
> tried with kasun's modified spring lib, looks like it is working..
>
>
> On 14 July 2014 16:54, Vijayaratha Vijayasingam
> wrote:
>
>> 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 without encountering any issues.
>>
>> Could not start:
>> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
>> It's
>> state is uninstalled.
>>
>> log4j:ERROR Could not instantiate class
>
Re: [Dev] We are getting some class not found issues intermittently
sorry wrong thread. Please ignore my last reply. thanks, On Mon, Mar 16, 2015 at 2:57 PM, Supun Malinga wrote: > Hi Manoj, > > Can you commit this pls ?. > > thanks, > > On Mon, Mar 16, 2015 at 2:49 PM, Prasad Tissera wrote: > >> 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 on IS 5.0.0. >>> >>> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera >>> wrote: >>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d "grant_type=password&username=admin&password=admin" https://localhost:9443/oauth2/token [1]. https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip Regards, Prasad. On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah < kishant...@wso2.com> wrote: > Can we have IS pack with the above issue hosted somewhere, so that we > could take a look? > > On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby > wrote: > >> 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 >> wrote: >> >>> 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 should we proceed in this? Thanks. >>> >>> root cause >>> java.lang.ClassNotFoundException: >>> org.wso2.carbon.identity.oauth.cache.CacheKey >>> >>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154) >>> >>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569) >>> java.lang.Class.getDeclaredConstructors0(Native Method) >>> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398) >>> java.lang.Class.getConstructor0(Class.java:2708) >>> java.lang.Class.getDeclaredConstructor(Class.java:1987) >>> >>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65) >>> >>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957) >>> >>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910) >>> >>> [1]. >>> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87 >>> [2]. https://wso2.org/jira/browse/CARBON-14864 >>> >>> Regards, >>> Prasad. >>> >>> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun >>> wrote: >>> Hi Sameera, Was this change applied to the 4.3.0 branch on git?. we are getting a similar random server not starting up issue. seems it is the same reason. If this is not already allied can we get this added to 4.3.0 branch. We are trying to fix integration test in greg and this random server hangup is causing a lot of time to be wasted. Regards, Pulasthi On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma >>> > wrote: > Done. > > > > > On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe > wrote: > >> Hi kernel team, >> >> Please commit the patch at [1] for this issue. >> >> [1] https://wso2.org/jira/browse/CARBON-14864 >> >> Thanks, >> KasunG >> >> >> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam < >> rat...@wso2.com> wrote: >> >>> tried with kasun's modified spring lib, looks like it is >>> working.. >>> >>> >>> On 14 July 2014 16:54, Vijayaratha Vijayasingam >> > wrote: >>> kasun , as you said i tried..after that i get some spring class loading issue..May be the
Re: [Dev] We are getting some class not found issues intermittently
Hi Manoj,
Can you commit this pls ?.
thanks,
On Mon, Mar 16, 2015 at 2:49 PM, Prasad Tissera wrote:
> 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 on IS 5.0.0.
>>
>> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote:
>>
>>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d
>>> "grant_type=password&username=admin&password=admin"
>>> https://localhost:9443/oauth2/token
>>>
>>> [1].
>>> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip
>>>
>>> Regards,
>>> Prasad.
>>>
>>> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
Can we have IS pack with the above issue hosted somewhere, so that we
could take a look?
On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby
wrote:
> 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
> wrote:
>
>> 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 should we proceed in this? Thanks.
>>
>> root cause java.lang.ClassNotFoundException:
>> org.wso2.carbon.identity.oauth.cache.CacheKey
>>
>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>>
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
>> java.lang.Class.getDeclaredConstructors0(Native Method)
>> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
>> java.lang.Class.getConstructor0(Class.java:2708)
>> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>>
>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>>
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>>
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>>
>> [1].
>> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
>> [2]. https://wso2.org/jira/browse/CARBON-14864
>>
>> Regards,
>> Prasad.
>>
>> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> Was this change applied to the 4.3.0 branch on git?. we are getting
>>> a similar random server not starting up issue. seems it is the same
>>> reason.
>>> If this is not already allied can we get this added to 4.3.0 branch. We
>>> are
>>> trying to fix integration test in greg and this random server hangup is
>>> causing a lot of time to be wasted.
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
>>> wrote:
>>>
Done.
On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
wrote:
> Hi kernel team,
>
> Please commit the patch at [1] for this issue.
>
> [1] https://wso2.org/jira/browse/CARBON-14864
>
> Thanks,
> KasunG
>
>
> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
> rat...@wso2.com> wrote:
>
>> tried with kasun's modified spring lib, looks like it is working..
>>
>>
>> On 14 July 2014 16:54, Vijayaratha Vijayasingam
>> wrote:
>>
>>> 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 wit
Re: [Dev] We are getting some class not found issues intermittently
I'll check and let you know ASAP. Thanks.
Regards,
Prasad.
On Mon, Mar 16, 2015 at 2:48 PM, Kishanthan Thangarajah 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 on IS 5.0.0.
>
> On Mon, Mar 16, 2015 at 9:36 AM, Prasad Tissera wrote:
>
>> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d
>> "grant_type=password&username=admin&password=admin"
>> https://localhost:9443/oauth2/token
>>
>> [1].
>> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip
>>
>> Regards,
>> Prasad.
>>
>> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Can we have IS pack with the above issue hosted somewhere, so that we
>>> could take a look?
>>>
>>> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby
>>> wrote:
>>>
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
wrote:
> 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 should we proceed in this? Thanks.
>
> root cause java.lang.ClassNotFoundException:
> org.wso2.carbon.identity.oauth.cache.CacheKey
>
> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
> java.lang.Class.getDeclaredConstructors0(Native Method)
> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
> java.lang.Class.getConstructor0(Class.java:2708)
> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>
> [1].
> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
> [2]. https://wso2.org/jira/browse/CARBON-14864
>
> Regards,
> Prasad.
>
> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
> wrote:
>
>> Hi Sameera,
>>
>> Was this change applied to the 4.3.0 branch on git?. we are getting a
>> similar random server not starting up issue. seems it is the same reason.
>> If this is not already allied can we get this added to 4.3.0 branch. We
>> are
>> trying to fix integration test in greg and this random server hangup is
>> causing a lot of time to be wasted.
>>
>> Regards,
>> Pulasthi
>>
>>
>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
>> wrote:
>>
>>> Done.
>>>
>>>
>>>
>>>
>>> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
>>> wrote:
>>>
Hi kernel team,
Please commit the patch at [1] for this issue.
[1] https://wso2.org/jira/browse/CARBON-14864
Thanks,
KasunG
On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
rat...@wso2.com> wrote:
> tried with kasun's modified spring lib, looks like it is working..
>
>
> On 14 July 2014 16:54, Vijayaratha Vijayasingam
> wrote:
>
>> 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 without encountering any issues.
>>
>> Could not start:
>> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
>> It's
>> state is uninstalled.
>>
>> log4j:ERROR Could not instantiate class
>> [
Re: [Dev] We are getting some class not found issues intermittently
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 wrote:
> 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: application/x-www-form-urlencoded;charset=UTF-8" -k -d
> "grant_type=password&username=admin&password=admin"
> https://localhost:9443/oauth2/token
>
> [1].
> https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip
>
> Regards,
> Prasad.
>
> On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Can we have IS pack with the above issue hosted somewhere, so that we
>> could take a look?
>>
>> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby
>> wrote:
>>
>>> 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
>>> wrote:
>>>
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 should we proceed in this? Thanks.
root cause java.lang.ClassNotFoundException:
org.wso2.carbon.identity.oauth.cache.CacheKey
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
java.lang.Class.getDeclaredConstructors0(Native Method)
java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
java.lang.Class.getConstructor0(Class.java:2708)
java.lang.Class.getDeclaredConstructor(Class.java:1987)
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
[1].
https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
[2]. https://wso2.org/jira/browse/CARBON-14864
Regards,
Prasad.
On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
wrote:
> Hi Sameera,
>
> Was this change applied to the 4.3.0 branch on git?. we are getting a
> similar random server not starting up issue. seems it is the same reason.
> If this is not already allied can we get this added to 4.3.0 branch. We
> are
> trying to fix integration test in greg and this random server hangup is
> causing a lot of time to be wasted.
>
> Regards,
> Pulasthi
>
>
> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
> wrote:
>
>> Done.
>>
>>
>>
>>
>> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
>> wrote:
>>
>>> Hi kernel team,
>>>
>>> Please commit the patch at [1] for this issue.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-14864
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
>>> rat...@wso2.com> wrote:
>>>
tried with kasun's modified spring lib, looks like it is working..
On 14 July 2014 16:54, Vijayaratha Vijayasingam
wrote:
> 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 without encountering any issues.
>
> Could not start:
> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
> It's
> state is uninstalled.
>
> log4j:ERROR Could not instantiate class
> [org.wso2.carbon.logging.appender.CarbonMemoryAppender].
>
> java.lang.ClassNotFoundException:
> org.wso2.carbon.logging.appender.CarbonMemoryAppender
>
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bund
Re: [Dev] We are getting some class not found issues intermittently
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: application/x-www-form-urlencoded;charset=UTF-8" -k -d
"grant_type=password&username=admin&password=admin"
https://localhost:9443/oauth2/token
[1].
https://wso2.org/jenkins/view/product-builds/job/product-is/org.wso2.is$wso2is/lastSuccessfulBuild/artifact/org.wso2.is/wso2is/5.1.0-SNAPSHOT/wso2is-5.1.0-SNAPSHOT.zip
Regards,
Prasad.
On Mon, Mar 16, 2015 at 9:15 AM, Kishanthan Thangarajah wrote:
> Can we have IS pack with the above issue hosted somewhere, so that we
> could take a look?
>
> On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby
> wrote:
>
>> 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 wrote:
>>
>>> 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 should we proceed in this? Thanks.
>>>
>>> root cause java.lang.ClassNotFoundException:
>>> org.wso2.carbon.identity.oauth.cache.CacheKey
>>>
>>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>>>
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
>>> java.lang.Class.getDeclaredConstructors0(Native Method)
>>> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
>>> java.lang.Class.getConstructor0(Class.java:2708)
>>> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>>>
>>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>>>
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>>>
>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>>>
>>> [1].
>>> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
>>> [2]. https://wso2.org/jira/browse/CARBON-14864
>>>
>>> Regards,
>>> Prasad.
>>>
>>> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
>>> wrote:
>>>
Hi Sameera,
Was this change applied to the 4.3.0 branch on git?. we are getting a
similar random server not starting up issue. seems it is the same reason.
If this is not already allied can we get this added to 4.3.0 branch. We are
trying to fix integration test in greg and this random server hangup is
causing a lot of time to be wasted.
Regards,
Pulasthi
On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
wrote:
> Done.
>
>
>
>
> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
> wrote:
>
>> Hi kernel team,
>>
>> Please commit the patch at [1] for this issue.
>>
>> [1] https://wso2.org/jira/browse/CARBON-14864
>>
>> Thanks,
>> KasunG
>>
>>
>> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> tried with kasun's modified spring lib, looks like it is working..
>>>
>>>
>>> On 14 July 2014 16:54, Vijayaratha Vijayasingam
>>> wrote:
>>>
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 without encountering any issues.
Could not start:
null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
It's
state is uninstalled.
log4j:ERROR Could not instantiate class
[org.wso2.carbon.logging.appender.CarbonMemoryAppender].
java.lang.ClassNotFoundException:
org.wso2.carbon.logging.appender.CarbonMemoryAppender
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.Cla
Re: [Dev] We are getting some class not found issues intermittently
Can we have IS pack with the above issue hosted somewhere, so that we could
take a look?
On Sun, Mar 15, 2015 at 1:21 PM, Johann Nallathamby wrote:
> 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 wrote:
>
>> 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 should we
>> proceed in this? Thanks.
>>
>> root cause java.lang.ClassNotFoundException:
>> org.wso2.carbon.identity.oauth.cache.CacheKey
>>
>> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>>
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
>> java.lang.Class.getDeclaredConstructors0(Native Method)
>> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
>> java.lang.Class.getConstructor0(Class.java:2708)
>> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>>
>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>>
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>>
>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>>
>> [1].
>> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
>> [2]. https://wso2.org/jira/browse/CARBON-14864
>>
>> Regards,
>> Prasad.
>>
>> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun
>> wrote:
>>
>>> Hi Sameera,
>>>
>>> Was this change applied to the 4.3.0 branch on git?. we are getting a
>>> similar random server not starting up issue. seems it is the same reason.
>>> If this is not already allied can we get this added to 4.3.0 branch. We are
>>> trying to fix integration test in greg and this random server hangup is
>>> causing a lot of time to be wasted.
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
>>> wrote:
>>>
Done.
On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
wrote:
> Hi kernel team,
>
> Please commit the patch at [1] for this issue.
>
> [1] https://wso2.org/jira/browse/CARBON-14864
>
> Thanks,
> KasunG
>
>
> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
> rat...@wso2.com> wrote:
>
>> tried with kasun's modified spring lib, looks like it is working..
>>
>>
>> On 14 July 2014 16:54, Vijayaratha Vijayasingam
>> wrote:
>>
>>> 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 without encountering any issues.
>>>
>>> Could not start:
>>> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
>>> It's
>>> state is uninstalled.
>>>
>>> log4j:ERROR Could not instantiate class
>>> [org.wso2.carbon.logging.appender.CarbonMemoryAppender].
>>>
>>> java.lang.ClassNotFoundException:
>>> org.wso2.carbon.logging.appender.CarbonMemoryAppender
>>>
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>
>>> at
>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>
>>> at
>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>>
>>> at java.lang.Class.forName0(Native Method)
>>>
>>> at java.lang.Class.forName(Class.java:171)
>>>
>>> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
>>>
>>> at
>>> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
>>>
>>> at
>>> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
>>>
>>> at
>>> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:629)
>>>
>>> at
>>> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
>>>
>>> at
>>> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.jav
Re: [Dev] We are getting some class not found issues intermittently
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 wrote:
> 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 should we
> proceed in this? Thanks.
>
> root cause java.lang.ClassNotFoundException:
> org.wso2.carbon.identity.oauth.cache.CacheKey
>
> org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
>
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
> java.lang.Class.getDeclaredConstructors0(Native Method)
> java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
> java.lang.Class.getConstructor0(Class.java:2708)
> java.lang.Class.getDeclaredConstructor(Class.java:1987)
>
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
>
> [1].
> https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
> [2]. https://wso2.org/jira/browse/CARBON-14864
>
> Regards,
> Prasad.
>
> On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun wrote:
>
>> Hi Sameera,
>>
>> Was this change applied to the 4.3.0 branch on git?. we are getting a
>> similar random server not starting up issue. seems it is the same reason.
>> If this is not already allied can we get this added to 4.3.0 branch. We are
>> trying to fix integration test in greg and this random server hangup is
>> causing a lot of time to be wasted.
>>
>> Regards,
>> Pulasthi
>>
>>
>> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
>> wrote:
>>
>>> Done.
>>>
>>>
>>>
>>>
>>> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
>>> wrote:
>>>
Hi kernel team,
Please commit the patch at [1] for this issue.
[1] https://wso2.org/jira/browse/CARBON-14864
Thanks,
KasunG
On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
rat...@wso2.com> wrote:
> tried with kasun's modified spring lib, looks like it is working..
>
>
> On 14 July 2014 16:54, Vijayaratha Vijayasingam
> wrote:
>
>> 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 without encountering any issues.
>>
>> Could not start:
>> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
>> It's
>> state is uninstalled.
>>
>> log4j:ERROR Could not instantiate class
>> [org.wso2.carbon.logging.appender.CarbonMemoryAppender].
>>
>> java.lang.ClassNotFoundException:
>> org.wso2.carbon.logging.appender.CarbonMemoryAppender
>>
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>>
>> at java.lang.Class.forName0(Native Method)
>>
>> at java.lang.Class.forName(Class.java:171)
>>
>> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
>>
>> at
>> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
>>
>> at
>> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
>>
>> at
>> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:629)
>>
>> at
>> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
>>
>> at
>> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
>>
>> at
>> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
>>
>> at
>> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
>>
>> at
>> org.apache.log4j.helpers.OptionConverter.selectAndConfig
Re: [Dev] We are getting some class not found issues intermittently
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 should we
proceed in this? Thanks.
root cause java.lang.ClassNotFoundException:
org.wso2.carbon.identity.oauth.cache.CacheKey
org.wso2.carbon.webapp.mgt.loader.CarbonWebappClassLoader.loadClass(CarbonWebappClassLoader.java:154)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1569)
java.lang.Class.getDeclaredConstructors0(Native Method)
java.lang.Class.privateGetDeclaredConstructors(Class.java:2398)
java.lang.Class.getConstructor0(Class.java:2708)
java.lang.Class.getDeclaredConstructor(Class.java:1987)
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:65)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:957)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:910)
[1].
https://github.com/wso2/orbit/commit/d947214c470b257a9fe3083d8c4c7baf49d46f87
[2]. https://wso2.org/jira/browse/CARBON-14864
Regards,
Prasad.
On Fri, Jul 18, 2014 at 9:52 AM, Pulasthi Supun wrote:
> Hi Sameera,
>
> Was this change applied to the 4.3.0 branch on git?. we are getting a
> similar random server not starting up issue. seems it is the same reason.
> If this is not already allied can we get this added to 4.3.0 branch. We are
> trying to fix integration test in greg and this random server hangup is
> causing a lot of time to be wasted.
>
> Regards,
> Pulasthi
>
>
> On Mon, Jul 14, 2014 at 8:56 PM, Sameera Jayasoma
> wrote:
>
>> Done.
>>
>>
>>
>>
>> On Mon, Jul 14, 2014 at 6:54 PM, Kasun Gajasinghe
>> wrote:
>>
>>> Hi kernel team,
>>>
>>> Please commit the patch at [1] for this issue.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-14864
>>>
>>> Thanks,
>>> KasunG
>>>
>>>
>>> On Mon, Jul 14, 2014 at 5:15 PM, Vijayaratha Vijayasingam <
>>> rat...@wso2.com> wrote:
>>>
tried with kasun's modified spring lib, looks like it is working..
On 14 July 2014 16:54, Vijayaratha Vijayasingam
wrote:
> 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 without encountering any issues.
>
> Could not start:
> null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482).
> It's
> state is uninstalled.
>
> log4j:ERROR Could not instantiate class
> [org.wso2.carbon.logging.appender.CarbonMemoryAppender].
>
> java.lang.ClassNotFoundException:
> org.wso2.carbon.logging.appender.CarbonMemoryAppender
>
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>
> at java.lang.Class.forName0(Native Method)
>
> at java.lang.Class.forName(Class.java:171)
>
> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
>
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
>
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
>
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:629)
>
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
>
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
>
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
>
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
>
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
>
> at org.apache.log4j.LogManager.(LogManager.java:122)
>
> at org.apache.log4j.Logger.getLogger(Logger.java:104)
>
> at
> org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:289)
>
> at
> org.apache.commons.logging.impl.Log4JLogger.(Log4JLogger.java:109)
>
> at sun.reflect.Native
Re: [Dev] We are getting some class not found issues intermittently
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 without encountering any issues.
Could not start:
null(reference:file:../plugins/spring.framework_3.1.0.wso2v1.jar:482). It's
state is uninstalled.
log4j:ERROR Could not instantiate class
[org.wso2.carbon.logging.appender.CarbonMemoryAppender].
java.lang.ClassNotFoundException:
org.wso2.carbon.logging.appender.CarbonMemoryAppender
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:171)
at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178)
at
org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317)
at
org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:629)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
at org.apache.log4j.LogManager.(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:104)
at
org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:289)
at org.apache.commons.logging.impl.Log4JLogger.(Log4JLogger.java:109)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1116)
at
org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:914)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:310)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
at org.wso2.carbon.axis2.internal.Activator.(Activator.java:32)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.refle
On 14 July 2014 14:33, Vijayaratha Vijayasingam wrote:
> thanks sameera..
>
>
> On 14 July 2014 14:07, Sameera Jayasoma 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 patch0001 to patch0009 to a Carbon kernel instance. But when I start
>> the kernel I got a Spring related class loading issue. Then I removed
>> patch0009 from the AM pack, but I couldn't reproduce the error. From these
>> steps I got a good observations to believe that patch0009 contains the root
>> cause of this issue.
>>
>> Since I got a spring related error earlier, I removed the spring bundle
>> from patch0009 and tested in kernel instance as well as in an AM instance.
>> I couldn't reproduce the error.
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Mon, Jul 14, 2014 at 12:31 PM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> 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 wrote:
>>>
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 *core.util module* which causes
> this issue?
>
>
> osgi> ls 454
> Components in bundle org.wso2.carb
Re: [Dev] We are getting some class not found issues intermittently
thanks sameera..
On 14 July 2014 14:07, Sameera Jayasoma 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 patch0001 to patch0009 to a Carbon kernel instance. But when I start
> the kernel I got a Spring related class loading issue. Then I removed
> patch0009 from the AM pack, but I couldn't reproduce the error. From these
> steps I got a good observations to believe that patch0009 contains the root
> cause of this issue.
>
> Since I got a spring related error earlier, I removed the spring bundle
> from patch0009 and tested in kernel instance as well as in an AM instance.
> I couldn't reproduce the error.
>
> Thanks,
> Sameera.
>
>
> On Mon, Jul 14, 2014 at 12:31 PM, Vijayaratha Vijayasingam <
> rat...@wso2.com> wrote:
>
>> 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 wrote:
>>
>>> 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 *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
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
org.wso2.carbon.utils(bid=454)
156 Active
org.wso2.carbon.context.internal.CarbonContextServiceComponent
org.wso2.carbon.utils(bid=454)
157 Unsatisfied
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
org.wso2.carbon.utils(bid=454)
osgi> comp 157
Component[
name =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
state = Unsatisfied
properties =
{service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
serviceFactory = false
serviceInterface = null
references = {
Reference[name = configuration.context.service,
interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
dynamic, cardi
nality = 1..1, target = null, bind = setConfigurationContextService,
unbind = unsetConfigurationContextService]
}
located in bundle = org.wso2.carbon.utils_4.2.0 [454]
]
Dynamic information :
*The component is NOT satisfied
The following references are not satisfied:
Reference[name = configuration.context.service, interface =
org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
cardinality = 1..
1, target = null, bind = setConfigurationContextService, unbind =
unsetConfigurationContextService]
Component configurations :
Configuration properties:
service.pid =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.name =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.id = 156
Instances:
On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
> 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 tomcat extensions
> such as tomcat valves,etc
> Bundle-DocURL = http://wso2.com
> Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
> Bundle-ManifestVersion = 2
> Bundle-Name = org.wso2.carbon.tomcat.ext
> Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
> Bundle-Vendor = WSO2 Inc
> Bundle-Version = 4.2.0
> Created-By = Apache Maven Bundle Plugin
>
> Export-Package =
>
> org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
>
> rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
>
> rg.eclipse.os
Re: [Dev] We are getting some class not found issues intermittently
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 related class loading issue. Then I removed
patch0009 from the AM pack, but I couldn't reproduce the error. From these
steps I got a good observations to believe that patch0009 contains the root
cause of this issue.
Since I got a spring related error earlier, I removed the spring bundle
from patch0009 and tested in kernel instance as well as in an AM instance.
I couldn't reproduce the error.
Thanks,
Sameera.
On Mon, Jul 14, 2014 at 12:31 PM, Vijayaratha Vijayasingam
wrote:
> 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 wrote:
>
>> 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 > > wrote:
>>
>>> 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
>>> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 156 Active
>>> org.wso2.carbon.context.internal.CarbonContextServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 157 Unsatisfied
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> osgi> comp 157
>>>
>>> Component[
>>> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> factory = null
>>> autoenable = true
>>> immediate = true
>>> implementation =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> state = Unsatisfied
>>> properties =
>>> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
>>> serviceFactory = false
>>> serviceInterface = null
>>> references = {
>>> Reference[name = configuration.context.service,
>>> interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
>>> dynamic, cardi
>>> nality = 1..1, target = null, bind = setConfigurationContextService,
>>> unbind = unsetConfigurationContextService]
>>> }
>>> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
>>> ]
>>> Dynamic information :
>>> *The component is NOT satisfied
>>> The following references are not satisfied:
>>> Reference[name = configuration.context.service, interface =
>>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
>>> cardinality = 1..
>>> 1, target = null, bind = setConfigurationContextService, unbind =
>>> unsetConfigurationContextService]
>>> Component configurations :
>>> Configuration properties:
>>> service.pid =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.name =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.id = 156
>>> Instances:
>>>
>>>
>>> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>>>
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 tomcat extensions
such as tomcat valves,etc
Bundle-DocURL = http://wso2.com
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
Bundle-ManifestVersion = 2
Bundle-Name = org.wso2.carbon.tomcat.ext
Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
Bundle-Vendor = WSO2 Inc
Bundle-Version = 4.2.0
Created-By = Apache Maven Bundle Plugin
Export-Package =
org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.
Re: [Dev] We are getting some class not found issues intermittently
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
framework bundle, and tested in the AM pack provided by Ratha. I couldn't
re-produce it so far. I have added this file and several other config files
(META-INF/{spring.schemas, spring.handlers} etc.) to spring framework in
patch0009 to fix some issues in AS.
Since you need to provide packs to QA, I will remove this particular file
from spring framework bundle. @Ratha, it would be great if you can test
this out. You will have to do following step.
1. Remove the file
"META-INF/services/javax.servlet.ServletContainerInitializer" from
spring-framework bundle in patch0009
2. Restart the server
Thanks,
KasunG
On Mon, Jul 14, 2014 at 12:31 PM, Vijayaratha Vijayasingam
wrote:
> 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 wrote:
>
>> 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 > > wrote:
>>
>>> 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
>>> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 156 Active
>>> org.wso2.carbon.context.internal.CarbonContextServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 157 Unsatisfied
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> osgi> comp 157
>>>
>>> Component[
>>> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> factory = null
>>> autoenable = true
>>> immediate = true
>>> implementation =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> state = Unsatisfied
>>> properties =
>>> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
>>> serviceFactory = false
>>> serviceInterface = null
>>> references = {
>>> Reference[name = configuration.context.service,
>>> interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
>>> dynamic, cardi
>>> nality = 1..1, target = null, bind = setConfigurationContextService,
>>> unbind = unsetConfigurationContextService]
>>> }
>>> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
>>> ]
>>> Dynamic information :
>>> *The component is NOT satisfied
>>> The following references are not satisfied:
>>> Reference[name = configuration.context.service, interface =
>>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
>>> cardinality = 1..
>>> 1, target = null, bind = setConfigurationContextService, unbind =
>>> unsetConfigurationContextService]
>>> Component configurations :
>>> Configuration properties:
>>> service.pid =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.name =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.id = 156
>>> Instances:
>>>
>>>
>>> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>>>
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 tomcat extensions
such as tomcat valves,etc
Bundle-DocURL = http://wso2.com
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
Bundle-ManifestVersion = 2
Bundle-Name = org.wso2.carbon.tomcat.ext
Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
Bundle-Vendor = WSO2 Inc
Bundle-Version = 4.2.0
Created-By = Apache Maven Bundle Plugin
Export-Package =
org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",o
Re: [Dev] We are getting some class not found issues intermittently
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
wrote:
> 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 wrote:
>
>> 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 > > wrote:
>>
>>> 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
>>> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 156 Active
>>> org.wso2.carbon.context.internal.CarbonContextServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 157 Unsatisfied
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> osgi> comp 157
>>>
>>> Component[
>>> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> factory = null
>>> autoenable = true
>>> immediate = true
>>> implementation =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> state = Unsatisfied
>>> properties =
>>> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
>>> serviceFactory = false
>>> serviceInterface = null
>>> references = {
>>> Reference[name = configuration.context.service,
>>> interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
>>> dynamic, cardi
>>> nality = 1..1, target = null, bind = setConfigurationContextService,
>>> unbind = unsetConfigurationContextService]
>>> }
>>> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
>>> ]
>>> Dynamic information :
>>> *The component is NOT satisfied
>>> The following references are not satisfied:
>>> Reference[name = configuration.context.service, interface =
>>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
>>> cardinality = 1..
>>> 1, target = null, bind = setConfigurationContextService, unbind =
>>> unsetConfigurationContextService]
>>> Component configurations :
>>> Configuration properties:
>>> service.pid =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.name =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.id = 156
>>> Instances:
>>>
>>>
>>> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>>>
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 tomcat extensions
such as tomcat valves,etc
Bundle-DocURL = http://wso2.com
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
Bundle-ManifestVersion = 2
Bundle-Name = org.wso2.carbon.tomcat.ext
Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
Bundle-Vendor = WSO2 Inc
Bundle-Version = 4.2.0
Created-By = Apache Maven Bundle Plugin
Export-Package =
org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.carbon.user.core.service,org.apache.catalina,
org.wso2.carbon.to
mcat.ext.utils,javax.servlet.http,org.apache.juli.logging,org.apache.tomcat.util.res,org.wso2.carbon.core.session,org.apache.catalina.ha,
org.apache.ax
is2.clustering,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.tomcat.ext.realms,org.wso2.carbon.user.core.tenant,org.apache.coyote,
org.wso2.carbon.ba
>>>
Re: [Dev] We are getting some class not found issues intermittently
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 wrote:
> 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
> wrote:
>
>> 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
>> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
>> org.wso2.carbon.utils(bid=454)
>> 156 Active
>> org.wso2.carbon.context.internal.CarbonContextServiceComponent
>> org.wso2.carbon.utils(bid=454)
>> 157 Unsatisfied
>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>> org.wso2.carbon.utils(bid=454)
>> osgi> comp 157
>>
>> Component[
>> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>> factory = null
>> autoenable = true
>> immediate = true
>> implementation =
>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>> state = Unsatisfied
>> properties =
>> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
>> serviceFactory = false
>> serviceInterface = null
>> references = {
>> Reference[name = configuration.context.service, interface
>> = org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic, cardi
>> nality = 1..1, target = null, bind = setConfigurationContextService,
>> unbind = unsetConfigurationContextService]
>> }
>> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
>> ]
>> Dynamic information :
>> *The component is NOT satisfied
>> The following references are not satisfied:
>> Reference[name = configuration.context.service, interface =
>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
>> cardinality = 1..
>> 1, target = null, bind = setConfigurationContextService, unbind =
>> unsetConfigurationContextService]
>> Component configurations :
>> Configuration properties:
>> service.pid =
>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>> component.name =
>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>> component.id = 156
>> Instances:
>>
>>
>> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>>
>>> 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 tomcat extensions such
>>> as tomcat valves,etc
>>> Bundle-DocURL = http://wso2.com
>>> Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
>>> Bundle-ManifestVersion = 2
>>> Bundle-Name = org.wso2.carbon.tomcat.ext
>>> Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
>>> Bundle-Vendor = WSO2 Inc
>>> Bundle-Version = 4.2.0
>>> Created-By = Apache Maven Bundle Plugin
>>>
>>> Export-Package =
>>>
>>> org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
>>>
>>> rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
>>>
>>> rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
>>>
>>> service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
>>>
>>> wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.carbon.user.core.service,org.apache.catalina,
>>> org.wso2.carbon.to
>>>
>>> mcat.ext.utils,javax.servlet.http,org.apache.juli.logging,org.apache.tomcat.util.res,org.wso2.carbon.core.session,org.apache.catalina.ha,
>>> org.apache.ax
>>>
>>> is2.clustering,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.tomcat.ext.realms,org.wso2.carbon.user.core.tenant,org.apache.coyote,
>>> org.wso2.carbon.ba
>>>
>>> se";version="4.2.0",org.wso2.carbon.tomcat.ext.saas;version="4.2.0",org.wso2.carbon.tomcat.ext.utils;version="4.2.0",org.wso2.carbon.tomcat.ext.filter
>>>
>>> ;uses:="javax.servlet";version="4.2.0",org.wso2.carbon.tomcat.ext.realms;uses:="org.apache.catalina.realm,org.apache.commons.logging,org.wso2.carbon.u
>>>
>>> ser.core.service,org.wso2.carbon.user.api,org.wso
Re: [Dev] We are getting some class not found issues intermittently
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
wrote:
> 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
> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
> org.wso2.carbon.utils(bid=454)
> 156 Active
> org.wso2.carbon.context.internal.CarbonContextServiceComponent
> org.wso2.carbon.utils(bid=454)
> 157 Unsatisfied
> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
> org.wso2.carbon.utils(bid=454)
> osgi> comp 157
>
> Component[
> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
> factory = null
> autoenable = true
> immediate = true
> implementation =
> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
> state = Unsatisfied
> properties =
> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
> serviceFactory = false
> serviceInterface = null
> references = {
> Reference[name = configuration.context.service, interface
> = org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic, cardi
> nality = 1..1, target = null, bind = setConfigurationContextService,
> unbind = unsetConfigurationContextService]
> }
> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
> ]
> Dynamic information :
> *The component is NOT satisfied
> The following references are not satisfied:
> Reference[name = configuration.context.service, interface =
> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
> cardinality = 1..
> 1, target = null, bind = setConfigurationContextService, unbind =
> unsetConfigurationContextService]
> Component configurations :
> Configuration properties:
> service.pid =
> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
> component.name =
> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
> component.id = 156
> Instances:
>
>
> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>
>> 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 tomcat extensions such
>> as tomcat valves,etc
>> Bundle-DocURL = http://wso2.com
>> Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
>> Bundle-ManifestVersion = 2
>> Bundle-Name = org.wso2.carbon.tomcat.ext
>> Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
>> Bundle-Vendor = WSO2 Inc
>> Bundle-Version = 4.2.0
>> Created-By = Apache Maven Bundle Plugin
>>
>> Export-Package =
>>
>> org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
>>
>> rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
>>
>> rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
>>
>> service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
>>
>> wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.carbon.user.core.service,org.apache.catalina,
>> org.wso2.carbon.to
>>
>> mcat.ext.utils,javax.servlet.http,org.apache.juli.logging,org.apache.tomcat.util.res,org.wso2.carbon.core.session,org.apache.catalina.ha,
>> org.apache.ax
>>
>> is2.clustering,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.tomcat.ext.realms,org.wso2.carbon.user.core.tenant,org.apache.coyote,
>> org.wso2.carbon.ba
>>
>> se";version="4.2.0",org.wso2.carbon.tomcat.ext.saas;version="4.2.0",org.wso2.carbon.tomcat.ext.utils;version="4.2.0",org.wso2.carbon.tomcat.ext.filter
>>
>> ;uses:="javax.servlet";version="4.2.0",org.wso2.carbon.tomcat.ext.realms;uses:="org.apache.catalina.realm,org.apache.commons.logging,org.wso2.carbon.u
>>
>> ser.core.service,org.wso2.carbon.user.api,org.wso2.carbon.utils.multitenancy,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.context";version="4.2.0",
>>
>> org.wso2.carbon.tomcat.ext.transport;uses:="org.wso2.carbon.tomcat.api,org.apache.commons.logging,org.wso2.carbon.base.api,org.wso2.carbon.core";versi
>>
>> on="4.2.0",org.wso2.carbon.tomcat.ext.servlet;uses:="javax.servlet,org.apache.commons.logging,org.wso2.carbon.utils,org.eclipse.equinox.http.s
Re: [Dev] We are getting some class not found issues intermittently
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 wrote:
> 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 please check, what causes the *"java.lang.*
> *ClassNotFoundException: org.wso2.carbon.tomcat.ext.*
> *servlet.DelegationServlet*" issue..
>
>
> Thanks.
>
>
>
>
> On 10 July 2014 12:10, Shameera Rathnayaka wrote:
>
>> Hi Sameera,
>>
>> On Thu, Jul 10, 2014 at 11:32 AM, Sameera Jayasoma
>> wrote:
>>
>>> Shameera/Pubudu
>>>
>>> Can you guys have a look at this issue?
>>>
>>
>> Start working on.
>>
>> Thanks,
>> Shameera.
>>
>>
>>>
>>>
>>> On Thu, Jul 10, 2014 at 11:28 AM, Vijayaratha Vijayasingam <
>>> rat...@wso2.com> wrote:
>>>
Carbon-core team, please check this issue..This currently blocks the
chunk-13 product releases..
-- Forwarded message --
From: Vijayaratha Vijayasingam
Date: 9 July 2014 18:49
Subject: Re: We are getting some class not found issues intermittently
To: WSO2 Developers' List , Sameera Jayasoma <
same...@wso2.com>, Kasun Gajasinghe , Kishanthan
Thangarajah
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
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
org.wso2.carbon.utils(bid=454)
156 Active
org.wso2.carbon.context.internal.CarbonContextServiceComponent
org.wso2.carbon.utils(bid=454)
157 Unsatisfied
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
org.wso2.carbon.utils(bid=454)
osgi> comp 157
Component[
name =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
state = Unsatisfied
properties =
{service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
serviceFactory = false
serviceInterface = null
references = {
Reference[name = configuration.context.service,
interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
dynamic, cardi
nality = 1..1, target = null, bind = setConfigurationContextService,
unbind = unsetConfigurationContextService]
}
located in bundle = org.wso2.carbon.utils_4.2.0 [454]
]
Dynamic information :
*The component is NOT satisfied
The following references are not satisfied:
Reference[name = configuration.context.service, interface =
org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
cardinality = 1..
1, target = null, bind = setConfigurationContextService, unbind =
unsetConfigurationContextService]
Component configurations :
Configuration properties:
service.pid =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.name =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.id = 156
Instances:
On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
> 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 tomcat extensions
> such as tomcat valves,etc
> Bundle-DocURL = http://wso2.com
> Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
> Bundle-ManifestVersion = 2
> Bundle-Name = org.wso2.carbon.tomcat.ext
> Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
> Bundle-Vendor = WSO2 Inc
> Bundle-Version = 4.2.0
> Created-By = Apache Maven Bundle Plugin
>
> Export-Package =
>
> org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
>
> rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
>
> rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.s
Re: [Dev] We are getting some class not found issues intermittently
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 please check, what causes the *"java.lang.*
*ClassNotFoundException: org.wso2.carbon.tomcat.ext.*
*servlet.DelegationServlet*" issue..
Thanks.
On 10 July 2014 12:10, Shameera Rathnayaka wrote:
> Hi Sameera,
>
> On Thu, Jul 10, 2014 at 11:32 AM, Sameera Jayasoma
> wrote:
>
>> Shameera/Pubudu
>>
>> Can you guys have a look at this issue?
>>
>
> Start working on.
>
> Thanks,
> Shameera.
>
>
>>
>>
>> On Thu, Jul 10, 2014 at 11:28 AM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Carbon-core team, please check this issue..This currently blocks the
>>> chunk-13 product releases..
>>>
>>>
>>> -- Forwarded message --
>>> From: Vijayaratha Vijayasingam
>>> Date: 9 July 2014 18:49
>>> Subject: Re: We are getting some class not found issues intermittently
>>> To: WSO2 Developers' List , Sameera Jayasoma <
>>> same...@wso2.com>, Kasun Gajasinghe , Kishanthan
>>> Thangarajah
>>>
>>>
>>> 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
>>> org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 156 Active
>>> org.wso2.carbon.context.internal.CarbonContextServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> 157 Unsatisfied
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> org.wso2.carbon.utils(bid=454)
>>> osgi> comp 157
>>>
>>> Component[
>>> name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> factory = null
>>> autoenable = true
>>> immediate = true
>>> implementation =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> state = Unsatisfied
>>> properties =
>>> {service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
>>> serviceFactory = false
>>> serviceInterface = null
>>> references = {
>>> Reference[name = configuration.context.service,
>>> interface = org.wso2.carbon.utils.ConfigurationContextService, policy =
>>> dynamic, cardi
>>> nality = 1..1, target = null, bind = setConfigurationContextService,
>>> unbind = unsetConfigurationContextService]
>>> }
>>> located in bundle = org.wso2.carbon.utils_4.2.0 [454]
>>> ]
>>> Dynamic information :
>>> *The component is NOT satisfied
>>> The following references are not satisfied:
>>> Reference[name = configuration.context.service, interface =
>>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
>>> cardinality = 1..
>>> 1, target = null, bind = setConfigurationContextService, unbind =
>>> unsetConfigurationContextService]
>>> Component configurations :
>>> Configuration properties:
>>> service.pid =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.name =
>>> org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
>>> component.id = 156
>>> Instances:
>>>
>>>
>>> On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
>>>
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 tomcat extensions
such as tomcat valves,etc
Bundle-DocURL = http://wso2.com
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
Bundle-ManifestVersion = 2
Bundle-Name = org.wso2.carbon.tomcat.ext
Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
Bundle-Vendor = WSO2 Inc
Bundle-Version = 4.2.0
Created-By = Apache Maven Bundle Plugin
Export-Package =
org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.
Re: [Dev] We are getting some class not found issues intermittently
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
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
org.wso2.carbon.utils(bid=454)
156 Active
org.wso2.carbon.context.internal.CarbonContextServiceComponent
org.wso2.carbon.utils(bid=454)
157 Unsatisfied
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
org.wso2.carbon.utils(bid=454)
osgi> comp 157
Component[
name = org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
state = Unsatisfied
properties =
{service.pid=org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent}
serviceFactory = false
serviceInterface = null
references = {
Reference[name = configuration.context.service, interface =
org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic, cardi
nality = 1..1, target = null, bind = setConfigurationContextService, unbind
= unsetConfigurationContextService]
}
located in bundle = org.wso2.carbon.utils_4.2.0 [454]
]
Dynamic information :
*The component is NOT satisfied
The following references are not satisfied:
Reference[name = configuration.context.service, interface =
org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic,
cardinality = 1..
1, target = null, bind = setConfigurationContextService, unbind =
unsetConfigurationContextService]
Component configurations :
Configuration properties:
service.pid =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.name =
org.wso2.carbon.utils.internal.CarbonUtilsServiceComponent
component.id = 156
Instances:
On 9 July 2014 18:28, Vijayaratha Vijayasingam wrote:
> 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 tomcat extensions such
> as tomcat valves,etc
> Bundle-DocURL = http://wso2.com
> Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
> Bundle-ManifestVersion = 2
> Bundle-Name = org.wso2.carbon.tomcat.ext
> Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
> Bundle-Vendor = WSO2 Inc
> Bundle-Version = 4.2.0
> Created-By = Apache Maven Bundle Plugin
>
> Export-Package =
>
> org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
>
> rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
>
> rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
>
> service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
>
> wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.carbon.user.core.service,org.apache.catalina,
> org.wso2.carbon.to
>
> mcat.ext.utils,javax.servlet.http,org.apache.juli.logging,org.apache.tomcat.util.res,org.wso2.carbon.core.session,org.apache.catalina.ha,
> org.apache.ax
>
> is2.clustering,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.tomcat.ext.realms,org.wso2.carbon.user.core.tenant,org.apache.coyote,
> org.wso2.carbon.ba
>
> se";version="4.2.0",org.wso2.carbon.tomcat.ext.saas;version="4.2.0",org.wso2.carbon.tomcat.ext.utils;version="4.2.0",org.wso2.carbon.tomcat.ext.filter
>
> ;uses:="javax.servlet";version="4.2.0",org.wso2.carbon.tomcat.ext.realms;uses:="org.apache.catalina.realm,org.apache.commons.logging,org.wso2.carbon.u
>
> ser.core.service,org.wso2.carbon.user.api,org.wso2.carbon.utils.multitenancy,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.context";version="4.2.0",
>
> org.wso2.carbon.tomcat.ext.transport;uses:="org.wso2.carbon.tomcat.api,org.apache.commons.logging,org.wso2.carbon.base.api,org.wso2.carbon.core";versi
>
> on="4.2.0",org.wso2.carbon.tomcat.ext.servlet;uses:="javax.servlet,org.apache.commons.logging,org.wso2.carbon.utils,org.eclipse.equinox.http.servlet,j
>
> avax.servlet.http,org.wso2.carbon.base";version="4.2.0",org.wso2.carbon.tomcat.ext.transport.statistics;uses:="org.apache.commons.logging,org.wso2.car
> bon.tomcat.ext.utils";version="4.2.0"
>
>
> *osgi> ss 454*
>
>
>
>
> *"Framework is launched."id State Bundle*
> *osgi> diag 454*
> reference:file:../plugins/org.wso2.carbon.utils_4.2.0.jar [454]
> Direct constraints which are
Re: [Dev] We are getting some class not found issues intermittently
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 tomcat extensions such as
tomcat valves,etc
Bundle-DocURL = http://wso2.com
Bundle-License = http://www.apache.org/licenses/LICENSE-2.0
Bundle-ManifestVersion = 2
Bundle-Name = org.wso2.carbon.tomcat.ext
Bundle-SymbolicName = org.wso2.carbon.tomcat.ext
Bundle-Vendor = WSO2 Inc
Bundle-Version = 4.2.0
Created-By = Apache Maven Bundle Plugin
Export-Package =
org.wso2.carbon.tomcat.ext.service;uses:="org.apache.commons.logging,org.apache.catalina,org.apache.catalina.core";version="4.2.0",o
rg.wso2.carbon.tomcat.ext.scan;uses:="javax.servlet,org.apache.tomcat,org.apache.tomcat.util.res,org.apache.tomcat.util.file,org.apache.juli.logging,o
rg.eclipse.osgi.framework.adaptor,org.apache.tomcat.util.scan";version="4.2.0",org.wso2.carbon.tomcat.ext.valves;uses:="org.wso2.carbon.registry.core.
service,org.apache.catalina.connector,org.apache.commons.logging,org.apache.catalina.valves,org.wso2.carbon.user.api,org.wso2.carbon.registry.api,org.
wso2.carbon.registry.core.ghostregistry,org.wso2.carbon.context,javax.servlet,org.wso2.carbon.user.core.service,org.apache.catalina,
org.wso2.carbon.to
mcat.ext.utils,javax.servlet.http,org.apache.juli.logging,org.apache.tomcat.util.res,org.wso2.carbon.core.session,org.apache.catalina.ha,
org.apache.ax
is2.clustering,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.tomcat.ext.realms,org.wso2.carbon.user.core.tenant,org.apache.coyote,
org.wso2.carbon.ba
se";version="4.2.0",org.wso2.carbon.tomcat.ext.saas;version="4.2.0",org.wso2.carbon.tomcat.ext.utils;version="4.2.0",org.wso2.carbon.tomcat.ext.filter
;uses:="javax.servlet";version="4.2.0",org.wso2.carbon.tomcat.ext.realms;uses:="org.apache.catalina.realm,org.apache.commons.logging,org.wso2.carbon.u
ser.core.service,org.wso2.carbon.user.api,org.wso2.carbon.utils.multitenancy,org.wso2.carbon.tomcat.ext.saas,org.wso2.carbon.context";version="4.2.0",
org.wso2.carbon.tomcat.ext.transport;uses:="org.wso2.carbon.tomcat.api,org.apache.commons.logging,org.wso2.carbon.base.api,org.wso2.carbon.core";versi
on="4.2.0",org.wso2.carbon.tomcat.ext.servlet;uses:="javax.servlet,org.apache.commons.logging,org.wso2.carbon.utils,org.eclipse.equinox.http.servlet,j
avax.servlet.http,org.wso2.carbon.base";version="4.2.0",org.wso2.carbon.tomcat.ext.transport.statistics;uses:="org.apache.commons.logging,org.wso2.car
bon.tomcat.ext.utils";version="4.2.0"
*osgi> ss 454*
*"Framework is launched."id State Bundle*
*osgi> diag 454*
reference:file:../plugins/org.wso2.carbon.utils_4.2.0.jar [454]
Direct constraints which are unresolved:
Missing optionally imported package javax.activation_[1.1.0,2.0.0).
Missing optionally imported package org.jivesoftware.smackx.muc_0.0.0.
osgi> ls -c 454
Components in bundle org.wso2.carbon.utils:
ID Component details
155 Component[
name =
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
state = Unsatisfied
properties =
{service.pid=org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent}
serviceFactory = false
serviceInterface = null
references = {
Reference[name = discoveryService, interface =
org.wso2.carbon.base.DiscoveryService, policy = dynamic, cardinality =
0..1, target = n
ull, bind = setDiscoveryService, unbind = unsetDiscoveryService]
}
located in bundle = org.wso2.carbon.utils_4.2.0 [454]
]
Dynamic information :
The component is satisfied
The following references are not satisfied:
Reference[name = discoveryService, interface =
org.wso2.carbon.base.DiscoveryService, policy = dynamic, cardinality =
0..1, target = null, bind =
setDiscoveryService, unbind = unsetDiscoveryService]
Component configurations :
Configuration properties:
service.pid =
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
component.name =
org.wso2.carbon.context.internal.CarbonContextDiscoveryServiceComponent
component.id = 154
Instances:
org.eclipse.equinox.internal.ds.impl.ComponentInstanceImpl@52d15077
156 Component[
name =
org.wso2.carbon.context.internal.CarbonContextServiceComponent
factory = null
autoenable = true
immediate = true
implementation =
org.wso2.carbon.context.internal.CarbonContextServiceComponent
state = Unsatisfied
properties =
{service.pid=org.wso2.carbon.context.internal.CarbonContextServiceComponent}
serviceFactory = false
serviceInterface = null
reference
