Hi Kishanthan,
Please find the requested information for [1] as a jira attchement. Please
consider that I observed this issue only when both proxy context path and
web context root is enabled as I mentioned in the JIRA.
[1] https://wso2.org/jira/browse/CARBON-15475
Thanks
Hasanthi Dissanayake
On Mon, Oct 19, 2015 at 9:32 AM, Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:
> Hi Kishanthan,
> Please find the requested information for [1] as a jira attchement. Please
> consider that I observed this issue only when both proxy context path and
> web context root is enabled as I
Hi Pandula,
AFAIK I have seen users using both of these configurations separately, but
not often together. So in that sense I don't think it should be considered
a blocker. This is just my opinion.
Thanks.
On Fri, Oct 16, 2015 at 8:34 PM, Pandula Kariyawasam
wrote:
> Hi
Hi Johann/Kishanthan,
Both issue [2][3] were observed rarely on IS510 pack received on 8th Oct
2015, which was based on kernel 4.4.1.
We didn't experience these issue up to now, on the pack received on 13th
Oct 2015, which is based on kernel 4.4.2.
So I think we can reduce the priority of these
Guys, can we please continue with the next RC quickly, since the DAS
release is waiting for this, and have some hard deadlines. We are planning
on putting an RC next Wednesday, so appreciate if the Kernel 4.4.2 be
available by then.
Cheers,
Anjana.
On Fri, Oct 16, 2015 at 2:38 PM, Kishanthan
Hi all,
We tested MB 3.0.0 with kernel 4.4.2-RC2 with the additional fixes and no
issues were identified.
Thank you
On Fri, Oct 16, 2015 at 4:03 PM, Pandula Kariyawasam
wrote:
> Hi Johann/Kishanthan,
>
> Both issue [2][3] were observed rarely on IS510 pack received on 8th
Hi Kishanthan,
On Fri, Oct 16, 2015 at 2:38 PM, Kishanthan Thangarajah wrote:
>
>
> On Fri, Oct 16, 2015 at 11:27 AM, Johann Nallathamby
> wrote:
>
>> Hi Kishanthan/Kernel Team,
>>
>> We have added the test case as well to the same PR.
>>
>
> Thanks
On Fri, Oct 16, 2015 at 11:27 AM, Johann Nallathamby
wrote:
> Hi Kishanthan/Kernel Team,
>
> We have added the test case as well to the same PR.
>
Thanks Johann.
@MB Team, could you guys verify that all your scenarios are now passing?.
We will start the next RC build once this
Or can we remove this required features section? since this will limit us
to do releases on limited version range if we are using specific kernel
version?
Thanks,
On Fri, Oct 16, 2015 at 4:35 PM, Rajith Vitharana wrote:
> [+Kishanthan]
>
> On Fri, Oct 16, 2015 at 4:35 PM,
Hi Pandula,
Thanks. But actually the JIRA in concern is
https://wso2.org/jira/browse/CARBON-15475 . Can you please provide your
feedback on this.
Thanks.
On Fri, Oct 16, 2015 at 4:03 PM, Pandula Kariyawasam
wrote:
> Hi Johann/Kishanthan,
>
> Both issue [2][3] were observed
Hi all,
We are calling this vote off due to [1] and will start a new vote for Kernel
4.4.2 RC3 release.
[1] https://wso2.org/jira/browse/CARBON-15517
Thank you
On Fri, Oct 16, 2015 at 5:31 PM, Rajith Vitharana wrote:
> Hi Kishanthan,
>
> Tested this by editing the jar file
Hi Kishanthan,
Tested this by editing the jar file manually with(version range in
"required-features.xml" file) "[4.3.0,5.0.0)" and it works fine.
Thanks,
On Fri, Oct 16, 2015 at 5:29 PM, Kishanthan Thangarajah wrote:
> I think making this as [4.3.0, 5.0.0) is the
I think making this as [4.3.0, 5.0.0) is the correct solution from kernel
side. This file ideally should not be part of kernel, but its there due to
"DefaultAppDeployer" is the one which deploys data-services and this class
is in currently in kernel code base.
@Rajith, could you quickly test this
Hi Kishanthan,
In "org.wso2.carbon.application.deployer" component's
"required-features.xml" it was mentioned "[4.4.0, 4.5.0)"
as "org.wso2.carbon.dataservices.server.feature.group" required version
range, since we(carbon-data) are still on 4.3.3-SNAPSHOT, capp deployment
fails in DSS latest, Can
[+Kishanthan]
On Fri, Oct 16, 2015 at 4:35 PM, Rajith Vitharana wrote:
> Hi Kishanthan,
>
> In "org.wso2.carbon.application.deployer" component's
> "required-features.xml" it was mentioned "[4.4.0, 4.5.0)"
> as "org.wso2.carbon.dataservices.server.feature.group" required
Hi Johann,
Still we are working on to identify the correct nginx config for this
scenario.
>From the QA perspective, we need to get this issue fixed, because if there
is a customer who will use this scenario, we will end up with a support
patch.
So, either need to get this fixed on 4.4.2 or
Hi Kishanthan/Kernel Team,
We are in the process writing the test case for the issue. Should be able
to send it before end of day.
[1] has been reported in another thread. This issue in particular looks
critical to me, because AFAIK there are many users using proxyContextPath.
Not sure about
Hi Kishanthan/Kernel Team,
We have added the test case as well to the same PR.
Also can we get CARBON-15505 merged? The PR for master is a very old PR
which we have missed to review and merge. This mainly contains some
reordering of fields in the UI to make it more consistent and reorder
Hi,
This issue is fixed in [1].
Thanks
isura
[1] https://wso2.org/jira/browse/CARBON-15517
On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby
wrote:
> Hi Isura,
>
> Can you look into this issue urgently. I remember you fixing an issue
> related to this.
>
> Thanks.
>
>
Can we also have test case for this fix please?
On Wed, Oct 14, 2015 at 6:13 PM, Isura Karunaratne wrote:
> Hi,
>
> This issue is fixed in [1].
>
>
> Thanks
> isura
>
>
> [1] https://wso2.org/jira/browse/CARBON-15517
>
>
> On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby
Hi,
There is also a minor issue in user core as well, which is related to mysql
server version. Created a public jira for that in [1]
[1] - https://wso2.org/jira/browse/CARBON-15514
Thanks,
On Wed, Oct 14, 2015 at 10:32 AM, Sasikala Kottegoda
wrote:
> Hi Kishanthan,
>
>
Hi Isura,
Can you look into this issue urgently. I remember you fixing an issue
related to this.
Thanks.
On Wed, Oct 14, 2015 at 7:16 AM, Indika Sampath wrote:
> Hi All,
>
> I debug code of our and found issue. It seems implementation of some API
> changed in user-core. Let
Hi Kishanthan,
Yes, it is present in 4.4.2 RC1 as well. But not in 4.4.1.
Thank you.
On Tue, Oct 13, 2015 at 5:22 PM, Kishanthan Thangarajah wrote:
> Was this issue found in 4.4.2 RC1 too?
>
> On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda
>
Hi,
We have tested Basic scenarios + installing DSS features in ESB 4.9.0 and
those are successful (there were some integration test failiers due to
configuration changes which needs some fixes in test cases in DSS)
+1 to release
Thanks,
On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda
Hi Manuri,
We tested MB 3.0.0 with this release and our scenario of queue creation
fails after giving a permission denied error. The scenario is as follows:
1. Create a user "user1" with a role assigned with permission to create
queues.
2. Login from "user1" and try to create a queue, we get a
could we hold the release until permission related issue is fixed?
On Tue, Oct 13, 2015 at 5:10 PM, Ramith Jayasinghe wrote:
> could we hold the release until permission related issue?
>
> On Tue, Oct 13, 2015 at 5:06 PM, Rajith Vitharana
> wrote:
>
>> Hi,
>>
Was this issue found in 4.4.2 RC1 too?
On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda
wrote:
> Hi Manuri,
>
> We tested MB 3.0.0 with this release and our scenario of queue creation
> fails after giving a permission denied error. The scenario is as follows:
>
> 1. Create
could we hold the release until permission related issue?
On Tue, Oct 13, 2015 at 5:06 PM, Rajith Vitharana wrote:
> Hi,
>
> We have tested Basic scenarios + installing DSS features in ESB 4.9.0 and
> those are successful (there were some integration test failiers due to
>
Hi All,
I debug code of our and found issue. It seems implementation of some API
changed in user-core. Let me explain the flow.
Our queue/topic creation has two call.
1. We create internal role when adding queue and assign "changePermission",
"publish", "consume" permissions to it. Which means
29 matches
Mail list logo