date:20130907

Re: [Dev] How to add new JMS parameter from Management Console?

2013-09-07 Thread Charitha Kankanamge

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 Support
cell: +94 717 129 752
http://charithaka.blogspot.com
*SOA and Testing without nonsense*


On Sun, Aug 18, 2013 at 1:22 PM, Isuru Perera  wrote:

> Hi,
>
> $subject.
>
> This is regarding SO question [1].
>
> It gives following error:
>
> [2013-08-18 09:55:24,582] ERROR - AbstractTransportService Error while
> initializing the jms listener
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.axiom.om.OMElement
> at
> org.apache.axis2.transport.jms.JMSConnectionFactory.(JMSConnectionFactory.java:79)
> at
> org.apache.axis2.transport.jms.JMSConnectionFactoryManager.loadConnectionFactoryDefinitions(JMSConnectionFactoryManager.java:58)
> at
> org.apache.axis2.transport.jms.JMSConnectionFactoryManager.(JMSConnectionFactoryManager.java:45)
> at
> org.apache.axis2.transport.jms.JMSListener.doInit(JMSListener.java:58)
> at
> org.apache.axis2.transport.base.AbstractTransportListenerEx.init(AbstractTransportListenerEx.java:62)
> at
> org.wso2.carbon.core.transports.AbstractTransportService.updateGlobalTransportParameters(AbstractTransportService.java:125)
> at
> org.wso2.carbon.transport.mgt.TransportAdmin.updateGloballyDefinedInParameters(TransportAdmin.java:448)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.transport.mgt.stub.TransportAdminStub.updateGloballyDefinedInParameters(TransportAdminStub.java:3676)
> at
> org.wso2.carbon.transport.mgt.ui.TransportAdminClient.updateGloballyDefinedInParameters(TransportAdminClient.java:276)
> at
> org.apache.jsp.transport_002dmgt.update_005ftransport_jsp._jspService(org.apache.jsp.transport_002dmgt.update_005ftransport_jsp:164)
> .
> [2013-08-18 09:55:24,586] ERROR - RPCInOnlyMessageReceiver Error while
> initializing the jms listener
> org.apache.axis2.AxisFault: Error while initializing the jms listener
> at
> org.wso2.carbon.core.transports.AbstractTransportService.updateGlobalTransportParameters(AbstractTransportService.java:131)
> at
> org.wso2.carbon.transport.mgt.TransportAdmin.updateGloballyDefinedInParameters(TransportAdmin.java:448)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at
> org.apache.axis2.transpor

Re: [Dev] Getting a Constraint Violation Exception when invoking an API in the gateway worker

2013-09-07 Thread Sumedha Rubasinghe

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, Senaka Fernando  wrote:

> 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  wrote:
>
>> Hi,
>> I'm getting the following exception when invoking an API in a distributed
>> APIM setup. In the deployment, we have two gateway nodes, one serving as a
>> manager and the other as the worker. Published APIs are first deployed on
>> the manager node and then propagated to the worker node  through the svn
>> deployment synchronizer.
>> This was only observed when invoking an API created by a tenant.
>>
>> [2013-09-06 18:41:29,653] ERROR - JDBCResourceDAO Failed to add resource
>> to path /. Referential integrity constraint violation:
>> "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE FOREIGN KEY(REG_PATH_ID,
>> REG_TENANT_ID) REFERENCES PUBLIC.REG_PATH(REG_PATH_ID, REG_TENANT_ID)"; SQL
>> statement:
>> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
>> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
>> REG_DESCRIPTION, REG_TENANT_ID, REG_UUID) VALUES (?, ?, ?, ?, ?, ?, ?, ?,
>> ?, ?) [23002-140]
>> org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation:
>> "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE FOREIGN KEY(REG_PATH_ID,
>> REG_TENANT_ID) REFERENCES PUBLIC.REG_PATH(REG_PATH_ID, REG_TENANT_ID)"; SQL
>> statement:
>> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
>> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
>> REG_DESCRIPTION, REG_TENANT_ID, REG_UUID) VALUES (?, ?, ?, ?, ?, ?, ?, ?,
>> ?, ?) [23002-140]
>>  at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
>> at org.h2.message.DbException.get(DbException.java:167)
>>  at org.h2.message.DbException.get(DbException.java:144)
>> at
>> org.h2.constraint.ConstraintReferential.checkRowOwnTable(ConstraintReferential.java:329)
>>  at
>> org.h2.constraint.ConstraintReferential.checkRow(ConstraintReferential.java:271)
>> at org.h2.table.Table.fireConstraints(Table.java:801)
>>  at org.h2.table.Table.fireAfterRow(Table.java:818)
>> at org.h2.command.dml.Insert.insertRows(Insert.java:122)
>>  at org.h2.command.dml.Insert.update(Insert.java:82)
>> at org.h2.command.CommandContainer.update(CommandContainer.java:70)
>>  at org.h2.command.Command.executeUpdate(Command.java:199)
>> at
>> org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:141)
>>  at
>> org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:127)
>> at
>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.addResourceWithoutContentId(JDBCResourceDAO.java:1391)
>>  at
>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.addRoot(JDBCResourceDAO.java:445)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:365)
>>  at
>> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
>>  at
>> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
>>  at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getConfigSystemRegistry(EmbeddedRegistryService.java:485)
>>  at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:295)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
>>  at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRequest(MultitenantMessageReceiver.java:196)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:77)
>>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:337)
>>  at
>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:378)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
>>  at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
>>  at java.util.concurrent.Thr

Re: [Dev] Error throws when pointing AS 5.2.0 and BAM 2.3.0 to the same User store

2013-09-07 Thread Deependra Ariyadewa

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 Vithanage  wrote:

> 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
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
> TID: [0] [BAM] [2013-09-06 23:43:07,005]  INFO
> {org.wso2.carbon.user.core.common.DefaultRealmService} -  Database already
> exists. Not creating a new database.
> {org.wso2.carbon.user.core.common.DefaultRealmService}
> TID: [0] [BAM] [2013-09-06 23:43:07,060] ERROR
> {org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Table
> 'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
> {org.wso2.carbon.user.core.util.DatabaseUtil}
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2002)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2624)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2127)
> at
> com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2293)
> at
> org.wso2.carbon.user.core.profile.dao.ProfileConfigDAO.loadProfileConfigs(ProfileConfigDAO.java:127)
> at
> org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder.buildProfileConfigurationFromDatabase(ProfileConfigurationBuilder.java:84)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:339)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:109)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:103)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:116)
> at
> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67)
> at
> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> TID: [0] [BAM] [2013-09-06 23:43:07,063] ERROR
> {org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder} -
> Database Error - Table 'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
> {org.wso2.ca

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

2013-09-07 Thread Vanjikumaran Sivajothy

Hi IsuruU,
I have reverted back the changes.

Best regards,
Vanji


On Sat, Sep 7, 2013 at 8:22 PM, Isuru Udana  wrote:

>
>
>
> On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando 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 revert that change
>> back as well?
>>
> Yes. This should be reverted.
>
> Vanji,
> Please revert these changes and set the synapse version only at newly
> created features, p2-profile . there itself.
>
>>
>> Also, I guess since chunk 02 is going with synapse-2.1.1-wso2v9, that
>> version should be referred directly within the chunk02 release only and not
>> in anywhere for the already released stuff as IsuruU has already pointed
>> out..
>>
>> Thanks,
>> Lasantha
>>
>>
>> On 7 September 2013 17:51, Vanjikumaran Sivajothy  wrote:
>>
>>> 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  wrote:
>>>
 Hi IsuruP,

 On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera  wrote:

> Hi,
>
> We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1
> for chunk-02 product releases.
>
> Please note that I committed version to platform parent pom.xml [1]
> with revision 184661.
>
 Parent is already released. So you can't commit to it.
 Instead of changing the synapse version in the parent pom, change the
 synapse version within relevant dependency, features, p2-profile there
 itself.

>
> Thanks!
>
> Best Regards,
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Sivajothy Vanjikumaran
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)777219209**
>>> *[image: Facebook]  [image:
>>> Twitter]  [image: 
>>> LinkedIn] 
>>> [image:
>>> Blogger]  [image: 
>>> SlideShare]
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Lasantha Fernando*
>> Software Engineer - Data Technologies Team
>> WSO2 Inc. http://wso2.com
>>
>> email: lasan...@wso2.com
>> mobile: (+94) 71 5247551
>>
>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)777219209**
*[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [QA] Please provide clear steps on how to reproduce issues

2013-09-07 Thread Senaka Fernando

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
sure as to how to report the steps, please do have a chat with a senior
person from the QA team.

When there are documentation available on how things are done, please refer
to them and report issues if they don't work as expected. In such
situations please quote the documentation that you referred to and explain
what didn't work. Please also be mindful that some configurations or
approach to make changes to configuration may change from release to
release and therefore be sure to follow the latest documentation.

Thanks,
Senaka.

-- 
* 
*
*
*
*Senaka Fernando*
Senior Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting a Constraint Violation Exception when invoking an API in the gateway worker

2013-09-07 Thread Senaka Fernando

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  wrote:

> Hi,
> I'm getting the following exception when invoking an API in a distributed
> APIM setup. In the deployment, we have two gateway nodes, one serving as a
> manager and the other as the worker. Published APIs are first deployed on
> the manager node and then propagated to the worker node  through the svn
> deployment synchronizer.
> This was only observed when invoking an API created by a tenant.
>
> [2013-09-06 18:41:29,653] ERROR - JDBCResourceDAO Failed to add resource
> to path /. Referential integrity constraint violation:
> "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE FOREIGN KEY(REG_PATH_ID,
> REG_TENANT_ID) REFERENCES PUBLIC.REG_PATH(REG_PATH_ID, REG_TENANT_ID)"; SQL
> statement:
> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
> REG_DESCRIPTION, REG_TENANT_ID, REG_UUID) VALUES (?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?) [23002-140]
> org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation:
> "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE FOREIGN KEY(REG_PATH_ID,
> REG_TENANT_ID) REFERENCES PUBLIC.REG_PATH(REG_PATH_ID, REG_TENANT_ID)"; SQL
> statement:
> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
> REG_DESCRIPTION, REG_TENANT_ID, REG_UUID) VALUES (?, ?, ?, ?, ?, ?, ?, ?,
> ?, ?) [23002-140]
>  at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
> at org.h2.message.DbException.get(DbException.java:167)
>  at org.h2.message.DbException.get(DbException.java:144)
> at
> org.h2.constraint.ConstraintReferential.checkRowOwnTable(ConstraintReferential.java:329)
>  at
> org.h2.constraint.ConstraintReferential.checkRow(ConstraintReferential.java:271)
> at org.h2.table.Table.fireConstraints(Table.java:801)
>  at org.h2.table.Table.fireAfterRow(Table.java:818)
> at org.h2.command.dml.Insert.insertRows(Insert.java:122)
>  at org.h2.command.dml.Insert.update(Insert.java:82)
> at org.h2.command.CommandContainer.update(CommandContainer.java:70)
>  at org.h2.command.Command.executeUpdate(Command.java:199)
> at
> org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:141)
>  at
> org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:127)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.addResourceWithoutContentId(JDBCResourceDAO.java:1391)
>  at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.addRoot(JDBCResourceDAO.java:445)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:365)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getConfigSystemRegistry(EmbeddedRegistryService.java:485)
>  at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:295)
> at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
>  at
> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.processRequest(MultitenantMessageReceiver.java:196)
> at
> org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive(MultitenantMessageReceiver.java:77)
>  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:337)
>  at
> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:378)
> at
> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
>  at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> [2013-09-06 18:41:29,656] FATAL - UserRegistry Failed to add the root
> collection to the coreRegistry.
> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to add
> resource to path /. Referential integrity constraint violation:
> "REG_RESOURCE_FK_BY_PATH_ID: PUBLIC.REG_RESOURCE FOREIGN KEY(REG_PATH_ID,
> REG_TENANT_

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

2013-09-07 Thread Isuru Udana

On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando  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 revert that change
> back as well?
>
Yes. This should be reverted.

Vanji,
Please revert these changes and set the synapse version only at newly
created features, p2-profile . there itself.

>
> Also, I guess since chunk 02 is going with synapse-2.1.1-wso2v9, that
> version should be referred directly within the chunk02 release only and not
> in anywhere for the already released stuff as IsuruU has already pointed
> out..
>
> Thanks,
> Lasantha
>
>
> On 7 September 2013 17:51, Vanjikumaran Sivajothy  wrote:
>
>> 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  wrote:
>>
>>> Hi IsuruP,
>>>
>>> On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera  wrote:
>>>
 Hi,

 We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1
 for chunk-02 product releases.

 Please note that I committed version to platform parent pom.xml [1]
 with revision 184661.

>>> Parent is already released. So you can't commit to it.
>>> Instead of changing the synapse version in the parent pom, change the
>>> synapse version within relevant dependency, features, p2-profile there
>>> itself.
>>>

 Thanks!

 Best Regards,

 [1]
 https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml

 --
 Isuru Perera
 Senior Software Engineer | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Isuru Udana*
>>> *
>>>  *
>>> Senior *
>>> Software Engineer
>>> *
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>> twitter: http://twitter.com/isudana
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/*
>> *Mobile:(+94)777219209**
>> *[image: Facebook]  [image:
>> Twitter]  [image: 
>> LinkedIn] 
>> [image:
>> Blogger]  [image: 
>> SlideShare]
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lasantha Fernando*
> Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 71 5247551
>



-- 
*Isuru Udana*
*
 *
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

2013-09-07 Thread Inosh Goonewardena

Thanks for the info sumedha. It worked.

On Sat, Sep 7, 2013 at 5:04 PM, Sumedha Rubasinghe  wrote:

> Cleaning axis2 jars in maven repo solved the issue.
>
>
> On Sat, Sep 7, 2013 at 4:31 PM, Sumedha Rubasinghe wrote:
>
>> Is this fixed now? I can still see this happening on r184688
>>
>>
>> On Tue, Sep 3, 2013 at 5:23 PM, Gihan Anuruddha  wrote:
>>
>>> I'm getting same. Any update ?
>>>
>>>
>>>  On Tue, Sep 3, 2013 at 4:10 PM, Inosh Goonewardena wrote:
>>>
 [INFO]

 [INFO] BUILD FAILURE
 [INFO]

 [INFO] Total time: 1:36:58.136s
 [INFO] Finished at: Tue Sep 03 15:44:55 IST 2013
 [INFO] Final Memory: 1424M/1817M
 [INFO]

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.lb.endpoint: Compilation
 failure
 [ERROR]
 /home/inosh/wso2/carbon/platform/trunk/components/load-balancer/lb-endpoint/org.wso2.carbon.lb.endpoint/src/main/java/org/wso2/carbon/lb/endpoint/endpoint/TenantAwareLoadBalanceEndpoint.java:[145,52]
 cannot find symbol
 [ERROR] symbol  : method addMember(org.apache.axis2.clustering.Member)
 [ERROR] location: interface
 org.apache.axis2.clustering.management.GroupManagementAgent
 [ERROR] -> [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn  -rf :org.wso2.carbon.lb.endpoint

 --
 Regards,

 Inosh Goonewardena
 Associate Technical Lead- WSO2 Inc.
 Mobile: +94779966317

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev

>>>
>>>
>>> --
>>> W.G. Gihan Anuruddha
>>> Senior Software Engineer | WSO2, Inc.
>>> M: +94772272595
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> /sumedha
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

2013-09-07 Thread Lasantha Fernando

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 synapse-2.1.1-wso2v9, that
version should be referred directly within the chunk02 release only and not
in anywhere for the already released stuff as IsuruU has already pointed
out..

Thanks,
Lasantha


On 7 September 2013 17:51, Vanjikumaran Sivajothy  wrote:

> 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  wrote:
>
>> Hi IsuruP,
>>
>> On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1
>>> for chunk-02 product releases.
>>>
>>> Please note that I committed version to platform parent pom.xml [1] with
>>> revision 184661.
>>>
>> Parent is already released. So you can't commit to it.
>> Instead of changing the synapse version in the parent pom, change the
>> synapse version within relevant dependency, features, p2-profile there
>> itself.
>>
>>>
>>> Thanks!
>>>
>>> Best Regards,
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> *
>>  *
>> Senior *
>> Software Engineer
>> *
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)777219209**
> *[image: Facebook]  [image:
> Twitter]  [image: 
> LinkedIn] 
> [image:
> Blogger]  [image: 
> SlideShare]
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lasantha Fernando*
Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

2013-09-07 Thread Isuru Perera

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 wrote:

> 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  wrote:
>
>> Hi IsuruP,
>>
>> On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1
>>> for chunk-02 product releases.
>>>
>>> Please note that I committed version to platform parent pom.xml [1] with
>>> revision 184661.
>>>
>> Parent is already released. So you can't commit to it.
>> Instead of changing the synapse version in the parent pom, change the
>> synapse version within relevant dependency, features, p2-profile there
>> itself.
>>
>>>
>>> Thanks!
>>>
>>> Best Regards,
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> *
>>  *
>> Senior *
>> Software Engineer
>> *
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)777219209**
> *[image: Facebook]  [image:
> Twitter]  [image: 
> LinkedIn] 
> [image:
> Blogger]  [image: 
> SlideShare]
>



-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error throws when pointing AS 5.2.0 and BAM 2.3.0 to the same User store

2013-09-07 Thread Asanka Vithanage

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
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
TID: [0] [BAM] [2013-09-06 23:43:07,005]  INFO
{org.wso2.carbon.user.core.common.DefaultRealmService} -  Database already
exists. Not creating a new database.
{org.wso2.carbon.user.core.common.DefaultRealmService}
TID: [0] [BAM] [2013-09-06 23:43:07,060] ERROR
{org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Table
'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
{org.wso2.carbon.user.core.util.DatabaseUtil}
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2002)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2624)
at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2127)
at
com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2293)
at
org.wso2.carbon.user.core.profile.dao.ProfileConfigDAO.loadProfileConfigs(ProfileConfigDAO.java:127)
at
org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder.buildProfileConfigurationFromDatabase(ProfileConfigurationBuilder.java:84)
at
org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:339)
at
org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:109)
at
org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:103)
at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:116)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
TID: [0] [BAM] [2013-09-06 23:43:07,063] ERROR
{org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder} -
Database Error - Table 'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
{org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder}
org.wso2.carbon.user.core.UserStoreException: Database Error - Table
'WSO2CARBON_DB.UM_CLAIM_BEHAVIOR' doesn't exist
at
org.wso2.carbon.user.core.profile.dao.ProfileConfigDAO.loadProfileConfigs(ProfileConfigDAO.java:152)
at
org.wso2.carbon.user.core.profile.builder.ProfileConfigurationBuilder.buildProfileConfigurationFromDatabase(ProfileConfigurationBuilder.java:84)
at
org.wso2.carbon.user.core.common.DefaultRealm.popu

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

2013-09-07 Thread Vanjikumaran Sivajothy

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  wrote:

> Hi IsuruP,
>
> On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1 for
>> chunk-02 product releases.
>>
>> Please note that I committed version to platform parent pom.xml [1] with
>> revision 184661.
>>
> Parent is already released. So you can't commit to it.
> Instead of changing the synapse version in the parent pom, change the
> synapse version within relevant dependency, features, p2-profile there
> itself.
>
>>
>> Thanks!
>>
>> Best Regards,
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)777219209**
*[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

2013-09-07 Thread Sumedha Rubasinghe

Cleaning axis2 jars in maven repo solved the issue.


On Sat, Sep 7, 2013 at 4:31 PM, Sumedha Rubasinghe  wrote:

> Is this fixed now? I can still see this happening on r184688
>
>
> On Tue, Sep 3, 2013 at 5:23 PM, Gihan Anuruddha  wrote:
>
>> I'm getting same. Any update ?
>>
>>
>>  On Tue, Sep 3, 2013 at 4:10 PM, Inosh Goonewardena wrote:
>>
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 1:36:58.136s
>>> [INFO] Finished at: Tue Sep 03 15:44:55 IST 2013
>>> [INFO] Final Memory: 1424M/1817M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>>> (default-compile) on project org.wso2.carbon.lb.endpoint: Compilation
>>> failure
>>> [ERROR]
>>> /home/inosh/wso2/carbon/platform/trunk/components/load-balancer/lb-endpoint/org.wso2.carbon.lb.endpoint/src/main/java/org/wso2/carbon/lb/endpoint/endpoint/TenantAwareLoadBalanceEndpoint.java:[145,52]
>>> cannot find symbol
>>> [ERROR] symbol  : method addMember(org.apache.axis2.clustering.Member)
>>> [ERROR] location: interface
>>> org.apache.axis2.clustering.management.GroupManagementAgent
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR]   mvn  -rf :org.wso2.carbon.lb.endpoint
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Inosh Goonewardena
>>> Associate Technical Lead- WSO2 Inc.
>>> Mobile: +94779966317
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> W.G. Gihan Anuruddha
>> Senior Software Engineer | WSO2, Inc.
>> M: +94772272595
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>



-- 
/sumedha
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

2013-09-07 Thread Sumedha Rubasinghe

Is this fixed now? I can still see this happening on r184688


On Tue, Sep 3, 2013 at 5:23 PM, Gihan Anuruddha  wrote:

> I'm getting same. Any update ?
>
>
> On Tue, Sep 3, 2013 at 4:10 PM, Inosh Goonewardena  wrote:
>
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 1:36:58.136s
>> [INFO] Finished at: Tue Sep 03 15:44:55 IST 2013
>> [INFO] Final Memory: 1424M/1817M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.lb.endpoint: Compilation
>> failure
>> [ERROR]
>> /home/inosh/wso2/carbon/platform/trunk/components/load-balancer/lb-endpoint/org.wso2.carbon.lb.endpoint/src/main/java/org/wso2/carbon/lb/endpoint/endpoint/TenantAwareLoadBalanceEndpoint.java:[145,52]
>> cannot find symbol
>> [ERROR] symbol  : method addMember(org.apache.axis2.clustering.Member)
>> [ERROR] location: interface
>> org.apache.axis2.clustering.management.GroupManagementAgent
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :org.wso2.carbon.lb.endpoint
>>
>>
>> --
>> Regards,
>>
>> Inosh Goonewardena
>> Associate Technical Lead- WSO2 Inc.
>> Mobile: +94779966317
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> W.G. Gihan Anuruddha
> Senior Software Engineer | WSO2, Inc.
> M: +94772272595
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking Token API to generate user tokens

2013-09-07 Thread Lalaji Sureshika

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 11:03 PM, Suneth Ranasinghe  wrote:

>
> Hi,
>
> I got following exception when I try to invoke Token API to generate user
> tokens from SAML2 assertions.
>
> [2013-09-06 22:38:35,325] ERROR - OAuth2Service Error when issuing the
> access token.
> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: NotOnOrAfter is
> having an expired timestamp in Conditions element
>  at
> org.wso2.carbon.identity.oauth2.token.handlers.grant.saml.SAML2BearerGrantTypeHandler.validateGrant(SAML2BearerGrantTypeHandler.java:349)
>  at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:185)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:174)
>  at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenClient.getAccessToken(OAuth2TokenClient.java:81)
>  at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:118)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
>  at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>  at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
>  at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
>  at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
>  at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>  at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
>  at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
>  at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
>  at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
>  at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>  at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>  at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>  at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>  at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>  at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>  at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>  at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>  at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>  at
> org.apache.tomcat.util.net.N

Re: [Dev] How to add new JMS parameter from Management Console?

Re: [Dev] Getting a Constraint Violation Exception when invoking an API in the gateway worker

Re: [Dev] Error throws when pointing AS 5.2.0 and BAM 2.3.0 to the same User store

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

[Dev] [QA] Please provide clear steps on how to reproduce issues

Re: [Dev] Getting a Constraint Violation Exception when invoking an API in the gateway worker

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

[Dev] Error throws when pointing AS 5.2.0 and BAM 2.3.0 to the same User store

Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

Re: [Dev] Build failure in trunk - org.wso2.carbon.lb.endpoint Compilation failure

Re: [Dev] Invoking Token API to generate user tokens

15 matches

Site Navigation

Mail list logo

Footer information