Hi Himasha,
i invoke this endpoint
https://xxx:8243/services/Alfresco_ObjectService_SSL_Proxy.Alfresco_ObjectService_SSL_ProxyHttpSoap12Endpoint
and this one
https://xxx:8243/services/Alfresco_ObjectService_SSL_Proxy.Alfresco_ObjectService_SSL_ProxyHttpSoap11Endpoint
and the error it´s the same :(
Hi Devs,
We are pleased to announce the release candidate of WSO2 IoT Server 3.2.0.
This is the first release candidate (RC) of the WSO2 IoT Server 3.2.0
release.
This release carries 275 issue fixes [1-12] over the last GA (3.1.0)
release.
Reported Issues:
-
Hi Thomas,
I believe this error is happening on the backend server. Then you can use
the fire and forget pattern. Try adding following property, before making
the service invocation.
Thanks,
Vinod
On Mon, Jan 29, 2018 at 8:30 PM, Thomas LEGRAND <
thomas.legr...@versusmind.eu> wrote:
> Hello,
>
[+ Irham]
On Tue, Jan 16, 2018 at 2:41 PM, Sanjeewa Malalgoda
wrote:
> Can we address this and fix it for 2.2.0?
>
> Thanks,
> sanjeewa.
>
> On Fri, Jan 12, 2018 at 4:23 PM, Kavitha Subramaniyam
> wrote:
>
>> Thanks Rajith to pointing out!
>>
>> @Harsha,
Hi,
This is regarding the issue[1]. This occurs because the json stream is not
set in the MessageContext before the call mediator in blocking mode tries
to call the JsonFormatter.
We are setting the json stream only when building the message. Is there a
specific reason for setting it only when
Can you please review and merge PR.
[1] https://github.com/wso2/wso2-axis2/pull/132
Best Regards.
Daekyung Kim.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Mon, Jan 29, 2018 at 10:46 PM, Sajith Perera wrote:
> Hi Chaminda
>
> Is this single node analytics setup? could you attach the full server log
> files?
>
Hi Sajith,
I have attached the full error logs in the initial mail.
In the product analytics and DAS deployment if
Hi Rukshan,
All you mentioned are fine with the setup. Anyway, with same puppet
configs, it didn't give this error with the apim-analytics-2.1.0 pack and
issue comes only when wum updated pack placed there in the cluster. I
flushed all the dbs and verified.
Thanks,
Chaminda
On Mon, Jan 29, 2018
Hi Chaminda,
Did you clear both Store and Processed DB from the Analytics? Most of the
time this could be due to configuration issue. Also does analytics
carbon-db is fresh DB when instance get start?
Also make sure carbon-DB is not shared and only pointed to Analytics.
Thanks and Regards
On
I also like the idea of writing the authenticated session cookie at the end
of the authentication sequence; even if it's a multi step authentication.
This will simply solve a lot of inconsistency issues we have I feel. Not
saying we can't solve it in any other way, but they might be bit more
Why this does not use Siddhi theme like other extensions?
On Thu, Jan 25, 2018 at 11:09 AM Kalaiyarasi Ganeshalingam <
kalaiyar...@wso2.com> wrote:
>
> Thanks Maheshika. I will check.
>
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
>
Hi Chaminda
Is this single node analytics setup? could you attach the full server log
files?
In the product analytics and DAS deployment if server pack is replaced and
pointing to the same database we need to mount the following file
directories as there are files will be updated during the
Hello,
I have a template where I *Call* a *Address* mediator. However, during the
runtime, I have a network problem which causes it to explode with a
graceful java.net.NoRouteToHostException. Of course, I will have to fix the
network part but, in the same time, I would like to be able to continue
So that's because we don't have a proper way of reverting it back. Hence
isn't it better to not to write cookies until a proper access of an
application takes place for this scenario ?. In multi step scenario it's
true that there is an idp session, but still the user is not properly
logged in
Thanks Riyafa, it is working fine with the curl command.
Thanks,
Keerthika.
On Mon, Jan 29, 2018 at 6:32 PM, Riyafa Abdul Hameed
wrote:
> Hi Keerthika,
>
> Are you using Postman to make the calls? If so we have noticed in a
> previous instance that it does not get cached
Multi-step authentication is a different case I think, We don't set cookies
in an intermediate state. What if we use "remember me" ? So the cookie will
be there even if we close the browswer. isn't it ?
On Mon, Jan 29, 2018 at 8:15 PM, Ishara Karunarathna
wrote:
> Hi Hasintha,
Hi Roberto,
Are you trying to invoke HTTPS endpoint in SOAPUI? Are you using the
correct port?
Thanks,
Himasha
On Thu, Jan 25, 2018 at 4:34 PM, Roberto Sanz
wrote:
> Hi,
> I´m using SOAPUI to test a secured proxy published on WSO2-EI-6.1.1. and
> i´m
> facing the
On Mon, Jan 29, 2018 at 8:40 PM, Hasintha Indrajee
wrote:
> So that's because we don't have a proper way of reverting it back. Hence
> isn't it better to not to write cookies until a proper access of an
> application takes place for this scenario ?. In multi step scenario it's
Hi Hasintha,
Same can happen in multi-step authentication where a user successfully
login wiht1st authenticator and fail in the 2nd case.
On Mon, Jan 29, 2018 at 8:04 PM, Hasintha Indrajee
wrote:
> We have the feature of enabling authorization for service provider [1].
>
HI Hsintha,
On Mon, Jan 29, 2018 at 8:19 PM, Hasintha Indrajee
wrote:
> Multi-step authentication is a different case I think, We don't set
> cookies in an intermediate state. What if we use "remember me" ? So the
> cookie will be there even if we close the browswer. isn't it
We have the feature of enabling authorization for service provider [1].
Imagine a scenario where we login to an SP for the very first time and
authorization fails due to some violation of authorization policies. Even
if authorization fails we do set commonAuthId cookie in the response which
means
Hi Samitha,
Since this a user issue, you won't be able to directly update the RXT.
However there are multiple workarounds as well. I think the best option is
using the admin console to delete the RXT first and add it again.
Regards,
Chandana
On 29 Jan. 2018 5:31 pm, "Samitha Chathuranga"
Hi Chiranga,
On Fri, Jan 26, 2018 at 12:11 PM, Imesh Gunaratne wrote:
> ...
>
> At the same time we can check with the BOSH team whether they have already
> implemented a solution for this.
>
I checked this with the PCF engineering team and according to them we may
need to
Hi Keerthika,
Are you using Postman to make the calls? If so we have noticed in a
previous instance that it does not get cached because Postman seemed to
insert unnecessary headers? Can you try using curl requests? Or RESTer is a
handy plugin for firefox.
Or you can set headersToExcludeInHash to
On Mon, Jan 29, 2018 at 6:20 PM, Chaminda Jayawardena
wrote:
> Hi All,
>
> Getting below error continuously on an apim-analytics-2.10 server instance.
> We are using latest wum updated apim-analytics2.1.0 pack with fresh
> databases.
>
> Configured the pack using puppet in an
Hi All,
Getting below error continuously on an apim-analytics-2.10 server instance.
We are using latest wum updated apim-analytics2.1.0 pack with fresh
databases.
Configured the pack using puppet in an apim cluster pattern-6[1].
The error encountered only when the wum updated pack is used.
Hi All,
I am using the cache mediator in the proxy. But the response is not getting
cached. I have tested this with EI 6.1.1-update17 and EI 6.1.1-update18.
For both, the response is fetched from the backend service not from the
cache. What could be the reason?
I am using the following
Hi Shazni,
That's the issue. To determine if it's a dataservice, again we need the
service data.
On Sat, Jan 27, 2018 at 10:56 PM, Shazni Nazeer wrote:
> Hi Tishani,
>
> Isn't there a way to determine if it's a dataservice at the time of
> deletion. If you have a way, can't we
Hi,
Your issue has been fixed and shall be included in future releases.
Thanks,
Riyafa
On Fri, Jan 19, 2018 at 1:39 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:
> Respected SirThis issue does not exist in wso2ei-6.1.1
> But is present in wso2ei-6.1.1-update7
29 matches
Mail list logo