Hi,
As per error logs[1],you have used an expired saml token to retrieve oauth
token.Try again with a saml token which is not expired.
[1] org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: NotOnOrAfter
is having an expired timestamp in Conditions element
Thanks;
On Fri, Sep 6, 2013 at
Is this fixed now? I can still see this happening on r184688
On Tue, Sep 3, 2013 at 5:23 PM, Gihan Anuruddha gi...@wso2.com wrote:
I'm getting same. Any update ?
On Tue, Sep 3, 2013 at 4:10 PM, Inosh Goonewardena in...@wso2.com wrote:
[INFO]
Cleaning axis2 jars in maven repo solved the issue.
On Sat, Sep 7, 2013 at 4:31 PM, Sumedha Rubasinghe sume...@wso2.com wrote:
Is this fixed now? I can still see this happening on r184688
On Tue, Sep 3, 2013 at 5:23 PM, Gihan Anuruddha gi...@wso2.com wrote:
I'm getting same. Any update ?
Hi IsuruP,
I have reverted it back to 2.1.1-wso2v8 using r184691.
Thank you,
Best regards,
Vanji
On Fri, Sep 6, 2013 at 11:44 PM, Isuru Udana isu...@wso2.com wrote:
Hi IsuruP,
On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera isu...@wso2.com wrote:
Hi,
We will be using synapse version
Hi All,
When trying to point BAM 2.3.0 to an UseStore (which already pointed to AS
5.2.0), Observed following exception.
TID: [0] [BAM] [2013-09-06 23:43:06,035] INFO
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} - Successfully
deployed Agent Client
Hi,
I think, we should be using Synapse 2.1.1-wso2v9 for chunk-02 products.
Anyway, we will have a quick discussion on Monday.
Thanks!
On Sat, Sep 7, 2013 at 5:51 PM, Vanjikumaran Sivajothy va...@wso2.comwrote:
Hi IsuruP,
I have reverted it back to 2.1.1-wso2v8 using r184691.
Thank you,
Hi all,
It seems the features/synapse/pom.xml synapse version has been changed to
2.1.2-wso2v1. But I think features/synapse has already being released with
version 2.1.1-wso2v8 for chunk 01 release. Shouldn't we revert that change
back as well?
Also, I guess since chunk 02 is going with
Thanks for the info sumedha. It worked.
On Sat, Sep 7, 2013 at 5:04 PM, Sumedha Rubasinghe sume...@wso2.com wrote:
Cleaning axis2 jars in maven repo solved the issue.
On Sat, Sep 7, 2013 at 4:31 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Is this fixed now? I can still see this
On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando lasan...@wso2.com wrote:
Hi all,
It seems the features/synapse/pom.xml synapse version has been changed to
2.1.2-wso2v1. But I think features/synapse has already being released with
version 2.1.1-wso2v8 for chunk 01 release. Shouldn't we
Hi Amila,
This is most probably a result of improper mounting configurations. Can you
please explain how the mounts were setup and how the registry databases
were configured?
Thanks,
Senaka.
On Sat, Sep 7, 2013 at 12:40 AM, Amila De Silva ami...@wso2.com wrote:
Hi,
I'm getting the following
Hi all,
This is gentle reminder for the newer people in the QA team. Please make
sure to provide clear steps to reproduce issues. Even though you find a
very useful issue, if the developer cannot reproduce it based on your
explanation, then it is hard or sometimes impossible to fix. If you not
Hi IsuruU,
I have reverted back the changes.
Best regards,
Vanji
On Sat, Sep 7, 2013 at 8:22 PM, Isuru Udana isu...@wso2.com wrote:
On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando lasan...@wso2.comwrote:
Hi all,
It seems the features/synapse/pom.xml synapse version has been changed
I managed to overcome start-up problem by creating UM_CLAIM_BEHAVIOR table
manually but I could not test functionality. This error occurred when I
try to integrate BAM 2.3.0 and MB 2.1.0 with a Carbon 4.2.0 based WSO2
server cluster.
Thanks,
Deependra.
On Sat, Sep 7, 2013 at 8:23 AM, Asanka
It seems there is a registry write happening during API invocation.
If this is related to erroneous mounting configuration goes away after
that, then no issue. If not, we need to check why a write operation is
happening for an API invocation.
Amila, pls note.
On Sat, Sep 7, 2013 at 10:07 PM,
I'm getting the same ClassCastException in the newly released AS-5.2.0 as
well [1].
It seems we have removed the global transport config from the UI but the
service specific config is still there with bugs.
[1]https://wso2.org/jira/browse/WSAS-1616
Charitha Kankanamge
Senior Manager, Technical
15 matches
Mail list logo