Re: [Dev] [BPS 350]: SchedulerTask Error

[Firzhan Naqash]

Hi,

Then this seems to be the Hazlecast OOM issue. Please report a jira for
this.


Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com 
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Mon, Oct 12, 2015 at 11:11 AM, Chathurika De Silva 
wrote:

> Hi Firzhan
>
> The cluster have the following configuration currently. The default value
> is 256m
>
> Xms512m -Xmx2048m -XX:MaxPermSize=512m
>
> Please advice with the recommended value and please note that this
> configuration is not given in the documentation
>
> On Mon, Oct 12, 2015 at 10:56 AM, Firzhan Naqash  wrote:
>
>> Hi Chathiruka,
>>
>> This seems to be the hazlecast OOM error observed with kernel 4.4.1. Can
>> you increase heap size and check this scenario again.
>>
>>
>> *TID: [-1] [] [2015-10-09 18:49:36,827] ERROR {org.apache.tomcat.util.net
>> .NioEndpoint$Poller} -
>> {org.apache.tomcat.util.net
>> .NioEndpoint$Poller}java.lang.OutOfMemoryError:
>> GC overhead limit exceeded*
>>
>> Regards,
>> Firzhan
>>
>>
>> --
>> *Firzhan Naqash*
>> Senior Software Engineer - Integration Platform Team
>> WSO2 Inc. http://wso2.com
>>
>> email: firz...@wso2.com 
>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>> blog: http://firzhanblogger.blogspot.com/
>>   *
>> *twitter: https://twitter.com/firzhan007
>>  | linked-in: 
>> **https://www.linkedin.com/in/firzhan
>> *
>>
>> On Mon, Oct 12, 2015 at 10:51 AM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi All
>>>
>>> We have configured a SchedulerTask for the BPS cluster (2 workers and
>>> manager fronted by nginx). The task runs every day 5.10 pm and deletes
>>> FAILED instances. The cluster was up and running in the weekend but was
>>> idle. Following error was observed.
>>>
>>>
>>> TID: [-1] [] [2015-10-09 18:49:23,157] ERROR
>>> {org.apache.ode.scheduler.simple.SimpleScheduler} -  Error during
>>> SchedulerTask execution {org.apache.ode.scheduler.simple.SimpleScheduler}
>>> com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast
>>> instance is not active!
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.getService(ProxyRegistry.java:65)
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.(ProxyRegistry.java:53)
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:74)
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:72)
>>> at
>>> com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:51)
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getOrCreateRegistry(ProxyServiceImpl.java:110)
>>> at
>>> com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getDistributedObject(ProxyServiceImpl.java:118)
>>> at
>>> com.hazelcast.instance.HazelcastInstanceImpl.getDistributedObject(HazelcastInstanceImpl.java:390)
>>> at
>>> com.hazelcast.instance.HazelcastInstanceImpl.getMap(HazelcastInstanceImpl.java:192)
>>> at
>>> com.hazelcast.instance.HazelcastInstanceProxy.getMap(HazelcastInstanceProxy.java:75)
>>> at
>>> org.wso2.carbon.bpel.core.ode.integration.BPELServerImpl$ODEClusterImpl.getKnownNodes(BPELServerImpl.java:1009)
>>> at
>>> org.apache.ode.scheduler.simple.SimpleScheduler.updateHeartBeatAndGetStaleNodes(SimpleScheduler.java:848)
>>> at
>>> org.apache.ode.scheduler.simple.SimpleScheduler.access$800(SimpleScheduler.java:53)
>>> at
>>> org.apache.ode.scheduler.simple.SimpleScheduler$CheckStaleNodes.run(SimpleScheduler.java:1226)
>>> at
>>> org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:810)
>>> at
>>> org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:807)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>>> {org.apache.tomcat.util.net.NioEndpoint$Poller} -
>>> {org.apache.tomcat.util.net.NioEndpoint$Poller}
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>> TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>>> 

Re: [Dev] How to set Database Properties in Carbon Datasources

[Kalpa Welivitigoda]

Hi all,

This is merged to release-4.4.2.

Madhawa is working on the PR for master branch.

On Mon, Oct 12, 2015 at 10:08 AM, Isuru Perera  wrote:

> Hi Carbon Team,
>
> I really appreciate if you can review and merge the PR before Carbon 4.4.2
> release. I also don't see any breaking changes and we should be able to
> include this in a patch release.
>
> The MB issue is blocked by this Carbon issue [2]
>
> [1] https://wso2.org/jira/browse/MB-1271
> [2] https://wso2.org/jira/browse/CARBON-15497
>
> On Fri, Oct 9, 2015 at 6:57 PM, Anjana Fernando  wrote:
>
>> It is not actually adding a new config, it is just adding a new config
>> section to an already existing configuration file. So I hope that's not a
>> problem.
>>
>> Cheers,
>> Anjana.
>>
>> On Fri, Oct 9, 2015 at 5:07 PM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi Kalpa,
>>>
>>> I didn't do any API additions in the fix. just added a config only. I
>>> think we can configs in patch releases?
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Fri, Oct 9, 2015 at 4:57 PM, Kalpa Welivitigoda 
>>> wrote:
>>>
 Hi Madhawa,

 I made some comments in [1], please have a look.

 On Fri, Oct 9, 2015 at 3:21 PM, Madhawa Gunasekara 
 wrote:

> Hi Kalpa,
>
> Can we have this improvement in 4.4.2 carbon release. I have sent a
> pull request with tests.
>
> [1] https://github.com/wso2/carbon-kernel/pull/528/files
> 
>
> Thanks,
> Madhawa
>
> On Thu, Oct 8, 2015 at 8:14 PM, Isuru Perera  wrote:
>
>> Created a JIRA: https://wso2.org/jira/browse/CARBON-15497
>>
>> On Thu, Oct 8, 2015 at 6:13 PM, Madhawa Gunasekara > > wrote:
>>
>>> Hi Anjana,
>>>
>>> Sure will do it.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Thu, Oct 8, 2015 at 6:05 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi,

 I think this functionality is not exposed from our ndatasource
 RDBMSDataSourceReader implementation. We would have to put a new 
 property
 to set these "DB properties". I think, these must be the properties 
 passed
 into when creating a new connection with this [1]. @Madhawa, shall we
 implement this for a future Kernel release, by adding a new section to 
 put
 these properties in the configuration.

 [1]
 http://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html#getConnection(java.lang.String,%20java.util.Properties)

 Cheers,
 Anjana.

 On Thu, Oct 8, 2015 at 3:33 PM, Isuru Perera 
 wrote:

> Hi,
>
> With Carbon Metrics, I need to save some "double" values in the
> database. Sometimes the Oracle JDBC Driver throws "Underflow" 
> exceptions
> [1] when trying to set a double to a prepared statement.
>
> To solve that issue, I changed the database columns to "
> BINARY_DOUBLE
> "
> [2] and I want to set the property "SetFloatAndDoubleUseBinary" to 
> true.
>
> I tested this with a standalone app with Tomcat JDBC and it works.
>
> import org.apache.tomcat.jdbc.pool.DataSource;
> import org.apache.tomcat.jdbc.pool.PoolProperties;
> ...
>
> PoolProperties p = new PoolProperties();
> p.setUrl("jdbc:oracle:thin:@localhost:1521/metrics");
> p.setDriverClassName("oracle.jdbc.OracleDriver");
> p.setUsername("USER");
> p.setPassword("PASSWD");
> 
> DataSource datasource = new DataSource();
> datasource.setPoolProperties(p);
>
>
> *Properties properties = new
> Properties();properties.setProperty("SetFloatAndDoubleUseBinary",
> "true");p.setDbProperties(properties);*
>
> I thought there is a way to set these kinds of properties in
> *-datasources.xml file. However I don't see a way to do that in
> configuration [3].
>
> I don't want to change the double values and I want to save it
> directly in the database. How do we fix this?
>
> Thanks!
>
> Best Regards,
>
> [1] https://wso2.org/jira/browse/MB-1271
> [2]
> https://docs.oracle.com/cd/E11882_01/timesten.112/e21642/types.htm#BABIGDEA
> [3]
> https://github.com/wso2/carbon-kernel/blob/v4.4.1/core/org.wso2.carbon.ndatasource.rdbms/src/main/java/org/wso2/carbon/ndatasource/rdbms/RDBMSConfiguration.java

Re: [Dev] [DEV][BPS] Clarification on bps dbscripts

[Hasitha Aravinda]

Hi Sashika,

Drop/Truncate scripts are used to recreate fresh environments.  Specially
these scripts will be useful, when you are working with restricted
environments like where you don't have privileges to create databases, etc.
Some users want these scripts specially when they do load tests.

Since you have dropped only bps database, this is expected. Since we are
creating fresh environment, we need to drop registry tables and re-create
them. AFAIK registry doesn't have drop scripts. Also we need to remove
previous deployed artifacts from file system as well.

Thanks
Hasitha.




On Mon, Oct 12, 2015 at 11:59 AM, Sashika Wijesinghe 
wrote:

> Hi Firzhan,
>
> There scripts to drop and truncate as well. Appreciate your help in
> clarifying below issues.
>
> 1. In /dbscripts/bps/bpel/drop there are scripts to drop the
> tables in BPS database.
>
> To verify the scripts, I stopped the BPS server and drop tables using the
> given 'drop scripts' and recreate the tables using given 'create scripts'.
> After restarting the server, "*[2015-10-12 11:33:14,791] ERROR
> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>  Cannot find DeploymentUnitDAO instance for package AdderProcess-1.*"
> error noted in terminal. This is because the package details are available
> in registry database.
>
> Further it is not possible to continue the work by deploying a new bpel
> process due to corrupted process. I had to undeploy the corrupted bpel
> process to continue work.
>
> Is there any recommended best practice to use the drop bps scripts? If so
> it should be documented because these scripts are bundled with the BPS
> package itself.
>
>
> Thanks
>
> On Fri, Oct 9, 2015 at 5:56 PM, Firzhan Naqash  wrote:
>
>> Hi,
>>
>> Those scripts are used to create the necessary database schema for bpel.
>> Without executing this scripts, you won't be able to start the bps server.
>>
>> As a first step, after configuring the bps-datasources.xml file, you have
>> to execute this script against your preferred database. Or else if you have
>> necessary database permissions, you can start the server with -Dsetup
>> option.
>>
>> Regards,
>> Firzhan
>>
>>
>> --
>> *Firzhan Naqash*
>> Senior Software Engineer - Integration Platform Team
>> WSO2 Inc. http://wso2.com
>>
>> email: firz...@wso2.com 
>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>> blog: http://firzhanblogger.blogspot.com/
>>   *
>> *twitter: https://twitter.com/firzhan007
>>  | linked-in: 
>> **https://www.linkedin.com/in/firzhan
>> *
>>
>> On Fri, Oct 9, 2015 at 5:51 PM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> There were bpel database scripts under /dbscripts/bps/bpel.
>>> May I know the real usecase of these scripts? Is there any specific
>>> pre-conditions that needs to follow before executing these scripts?
>>>
>>> Thanks
>>> --
>>>
>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 774537487
>>> sash...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>



-- 
--
Hasitha Aravinda,
Senior Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile : +94 718 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Single tenant concurrent application creation fails for more than 10 apps

[Aiyadurai Rajeevan]

Hi All,

I have been testing the below code for synchronizing the critical
resource(remote repo URL), But still some of the pushes are failed.

public boolean push(String remoteRepoUrl, String pushBranch, File
repoFile) throws RepositoryMgtException {
try {
Git gitRepo = getGitRepository(remoteRepoUrl, repoFile);
log.info("Remote repo URL>"+remoteRepoUrl);


Iterable pushResults = gitRepo.push()
.setRemote(remoteRepoUrl)
.setRefSpecs(new RefSpec("refs/heads/" + pushBranch))
.setCredentialsProvider(getCredentialsProvider())
.call();
// we need to verify if git push was successful. Here we can
check RemoteRefUpdate status is rejected or not.
boolean pushed = true;
int currentPushTry=1;
for (PushResult pushResult : pushResults) {
if (pushResult.getRemoteUpdates().size() > 0) {
Collection refUpdates =
pushResult.getRemoteUpdates();
if (refUpdates != null && refUpdates.size() > 0) {
log.warn("RefUpdates size==>>"+refUpdates.size());
for (RemoteRefUpdate refUpdate : refUpdates) {
if (refUpdate.getStatus() ==
RemoteRefUpdate.Status.REJECTED_OTHER_REASON ||
refUpdate.getStatus() ==
RemoteRefUpdate.Status.REJECTED_NODELETE ||
refUpdate.getStatus() ==
RemoteRefUpdate.Status.REJECTED_NONFASTFORWARD ||
refUpdate.getStatus() ==
RemoteRefUpdate.Status.REJECTED_REMOTE_CHANGED) {
log.info("Remote
name>>"+refUpdate.getRemoteName());
pushed = false;

//pushed=pushFailed(remoteRepoUrl,pushBranch,repoFile);
log.warn("Failed to push artifacts on
repo, So called pushFailed method" + remoteRepoUrl + " due to " +
refUpdate.getStatus() + "
Message " + refUpdate.getMessage()+" Application"+repoFile);
break;

}
}
}
}
}
int maxPushTryCount =
Integer.parseInt(AppFactoryUtil.getAppfactoryConfiguration().getFirstProperty(AppFactoryConstants.S2GIT_PUSH_RETRY_COUNT));
long retrySleepTime =
Long.parseLong(AppFactoryUtil.getAppfactoryConfiguration().getFirstProperty(AppFactoryConstants.S2GIT_PUSH_RETRY_SLEEP_TIME));
log.info("Max push try
count"+maxPushTryCount);
log.info("Retry sleep
time=>>>"+retrySleepTime);
synchronized (remoteRepoUrl) {
while (currentPushTry < maxPushTryCount && !pushed) {
//log.info("Thread name in Re
try:"+Thread.currentThread().getName());
Thread.sleep(retrySleepTime * currentPushTry); //Pause
for 10*retrycount seconds
pushed = pushFailed(remoteRepoUrl, pushBranch,
repoFile, currentPushTry);
currentPushTry++;
}
}
return pushed;


} catch (RepositoryMgtException e) {
String msg =
"Error while pushing  : " + pushBranch + " due to " +
e.getMessage() + " from RepositoryMgtException";
log.error(msg, e);
throw new RepositoryMgtException(msg, e);
} catch (GitAPIException e) {
String msg =
"Error while pushing : " + pushBranch + " due to " +
e.getMessage() + " from GitAPIException";
log.error(msg, e);
throw new RepositoryMgtException(msg, e);
} catch (InterruptedException e) {
String msg =
"Thread is interupted due to " +
e.getMessage();
log.error(msg, e);
return false;
} catch (AppFactoryException e) {
e.printStackTrace();
return false;
}

}
public boolean pushFailed(String remoteRepoUrl, String pushBranch,
File repoFile,int currentPushTry) throws RepositoryMgtException,
GitAPIException {
log.warn("Re trying " + currentPushTry + " time, for " + repoFile);
boolean pushed;
log.info("Lock obtained for remote repo URL: " + remoteRepoUrl);
Git gitRepo = getGitRepository(remoteRepoUrl, repoFile);


gitRepo.pull().setRebase(true).setCredentialsProvider(getCredentialsProvider()).call();
Iterable pushResults = gitRepo.push()
.setRemote(remoteRepoUrl)
.setRefSpecs(new RefSpec("refs/heads/" + pushBranch))
.setCredentialsProvider(getCredentialsProvider())
.call();
// we need to verify if git push was successful. Here we
can check RemoteRefUpdate status is rejected or not.
pushed = true;
for (PushResult 

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Isuru Wijesinghe]

Congratulations :)

On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe 
wrote:

> Congratulations Sasikala!! :)
>
> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
> kirishan...@wso2.com> wrote:
>
>> Congrats Sasikala !
>>
>> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda 
>> wrote:
>>
>>> Thanks all... :)
>>>
>>> And special thanks to the MB team for the help that I've received so
>>> far... :)
>>>
>>> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe 
>>> wrote:
>>>
 Hi Sasikala,
 Congratulations!
 It is with great pleasure that we welcome you as a WSO2 committer. Keep
 up the good work!
 regards,

 --
 Ramith Jayasinghe
 Technical Lead
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware



>>>
>>>
>>> --
>>> Sasikala Kottegoda
>>> *Software Engineer*
>>> WSO2 Inc., http://wso2.com/
>>> lean. enterprise. middleware
>>> Mobile: +94 774835928/712792401
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Kirishanthy
>> Associate Software Engineer
>> Mobile : +94 778333939
>> kirishan...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Chanaka Fernando]

Hi All,

This issue is fixed with the following PR [1]. Thanks for reporting and
helping us to figure out the issue.

[1] https://github.com/wso2/carbon-mediation/pull/467

On Fri, Oct 9, 2015 at 3:41 PM, Chanaka Fernando  wrote:

> Hi Sameera,
>
> Your judgment is correct and it helped us to find the root cause :). I'll
> fix the code from carbon-mediation side. Thanks for your input.
>
> On Fri, Oct 9, 2015 at 3:19 PM, Sameera Jayasoma  wrote:
>
>> Hi Chanaka,
>>
>> You don't need to destroy the current context. This part is handle by the
>> Kernel code. Users of the CarbonContext API do not need to worry about
>> destroying the context.
>>
>> Who has done this change? So my initial judgment is correct. :) Stack
>> cannot become empty.
>>
>> Thanks,
>> Sameera.
>>
>> On Thu, Oct 8, 2015 at 6:14 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> At last, I was able to find the root cause for this behavior. This is
>>> actually coming from carbon-mediation code. What actually happens is that
>>> when ESB starts with a tenant, it will not load the tenant until it
>>> receives the first request. When It receives the first request, it will
>>> call the MultitenantMessageReceiver.processRequest() method. Within this
>>> method, it will call the following method.
>>>
>>> PrivilegedCarbonContext.startTenantFlow();
>>>
>>>
>>> This will get the ThreadLocal variable *parentContextHolderStack *and
>>> get the stack  and push the carbonContextDataHolder object to the
>>> stack. After this, tenant loading happens and within the initialization of
>>> the carbon mediation registry we have the following code segment.
>>>
>>> *org.wso2.carbon.mediation.registry.WSO2Registry.java*
>>>
>>> /**
>>>  *  Carbon Kernel mandates to set Threadlocal before calling anything in 
>>> kernel
>>>  */
>>> private void setTenantInfo() {
>>> // Preserve user name
>>> String username = 
>>> PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername();
>>> *PrivilegedCarbonContext.destroyCurrentContext();*
>>> PrivilegedCarbonContext cc = 
>>> PrivilegedCarbonContext.getThreadLocalCarbonContext();
>>> cc.setTenantDomain(domain);
>>> cc.setTenantId(tenantId);
>>> if (username != null) { // Set back the user name
>>> 
>>> PrivilegedCarbonContext.getThreadLocalCarbonContext().setUsername(username);
>>> }
>>> }
>>>
>>> Within the above method following line causes the issue.
>>>
>>> PrivilegedCarbonContext.destroyCurrentContext();
>>>
>>> When this method is called, it will reset the *parentContextHolderStack
>>> *and the initial object push into the stack is destroyed. Then after
>>> tenant loading, within the MultitenantMessageReceiver.processRequest()
>>> method, it tries to end the tenant flow within finally block and try to pop
>>> the object which it pushes early. But right now, we have a new context
>>> stack and it will throw the emptyStackException due to that.
>>>
>>> @Sameera/KasunG: Do we really need to use the following code segment
>>> within the above method?
>>>
>>>
>>> *PrivilegedCarbonContext.destroyCurrentContext();*
>>>
>>> I saw this method called within carbon-mediation components in 3
>>> different locations. AFAIU, we don't need to destroy the current context
>>> when we are accessing the ThreadLocalContext. Please share your thoughts
>>> such that we can fix this issue. Issue is fixed when I comment out the
>>> above line :)
>>>
>>>
>>> Thanks,
>>> Chanaka
>>>
>>>
>>>
>>> On Wed, Oct 7, 2015 at 5:34 PM, Chanaka Fernando 
>>> wrote:
>>>
 Hi Sameera/KasunG,

 I have debugged the code to find the root cause for this empty stack
 exception. This is causing several other issues at the ESB layer. What
 actually happens is that inside the
 MultitenantMessageReceiver.processRequest() method, we have the following
 code segment.

 try {
 PrivilegedCarbonContext.startTenantFlow();
 PrivilegedCarbonContext privilegedCarbonContext = 
 PrivilegedCarbonContext.getThreadLocalCarbonContext();
 privilegedCarbonContext.setTenantDomain(tenantDomain, true);
 // this is to prevent non-blocking transports from sending 202
 
 mainInMsgContext.getOperationContext().setProperty(Constants.RESPONSE_WRITTEN,
  "SKIP");

 ConfigurationContext tenantConfigCtx =

 TenantAxisUtils.getTenantConfigurationContext(tenantDomain,

   mainConfigCtx);
 if (tenantConfigCtx == null) {
 // Throw AxisFault: Tenant does not exist
 handleException(mainInMsgContext, new AxisFault("Tenant " + 
 tenantDomain +
 "  not found"));
 return;
 }

 if 

Re: [Dev] [BPS 350]: SchedulerTask Error

[Chathurika De Silva]

Hi

Done [1]

[1] https://wso2.org/jira/browse/BPS-907

On Mon, Oct 12, 2015 at 11:35 AM, Firzhan Naqash  wrote:

> Hi,
>
> Then this seems to be the Hazlecast OOM issue. Please report a jira for
> this.
>
>
> Regards,
> Firzhan
>
>
> --
> *Firzhan Naqash*
> Senior Software Engineer - Integration Platform Team
> WSO2 Inc. http://wso2.com
>
> email: firz...@wso2.com 
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
>   *
> *twitter: https://twitter.com/firzhan007
>  | linked-in: 
> **https://www.linkedin.com/in/firzhan
> *
>
> On Mon, Oct 12, 2015 at 11:11 AM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi Firzhan
>>
>> The cluster have the following configuration currently. The default value
>> is 256m
>>
>> Xms512m -Xmx2048m -XX:MaxPermSize=512m
>>
>> Please advice with the recommended value and please note that this
>> configuration is not given in the documentation
>>
>> On Mon, Oct 12, 2015 at 10:56 AM, Firzhan Naqash 
>> wrote:
>>
>>> Hi Chathiruka,
>>>
>>> This seems to be the hazlecast OOM error observed with kernel 4.4.1. Can
>>> you increase heap size and check this scenario again.
>>>
>>>
>>> *TID: [-1] [] [2015-10-09 18:49:36,827] ERROR
>>> {org.apache.tomcat.util.net
>>> .NioEndpoint$Poller} -
>>> {org.apache.tomcat.util.net
>>> .NioEndpoint$Poller}java.lang.OutOfMemoryError:
>>> GC overhead limit exceeded*
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> --
>>> *Firzhan Naqash*
>>> Senior Software Engineer - Integration Platform Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: firz...@wso2.com 
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>>   *
>>> *twitter: https://twitter.com/firzhan007
>>>  | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> *
>>>
>>> On Mon, Oct 12, 2015 at 10:51 AM, Chathurika De Silva <
>>> chathuri...@wso2.com> wrote:
>>>
 Hi All

 We have configured a SchedulerTask for the BPS cluster (2 workers and
 manager fronted by nginx). The task runs every day 5.10 pm and deletes
 FAILED instances. The cluster was up and running in the weekend but was
 idle. Following error was observed.


 TID: [-1] [] [2015-10-09 18:49:23,157] ERROR
 {org.apache.ode.scheduler.simple.SimpleScheduler} -  Error during
 SchedulerTask execution {org.apache.ode.scheduler.simple.SimpleScheduler}
 com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast
 instance is not active!
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.getService(ProxyRegistry.java:65)
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyRegistry.(ProxyRegistry.java:53)
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:74)
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:72)
 at
 com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:51)
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getOrCreateRegistry(ProxyServiceImpl.java:110)
 at
 com.hazelcast.spi.impl.proxyservice.impl.ProxyServiceImpl.getDistributedObject(ProxyServiceImpl.java:118)
 at
 com.hazelcast.instance.HazelcastInstanceImpl.getDistributedObject(HazelcastInstanceImpl.java:390)
 at
 com.hazelcast.instance.HazelcastInstanceImpl.getMap(HazelcastInstanceImpl.java:192)
 at
 com.hazelcast.instance.HazelcastInstanceProxy.getMap(HazelcastInstanceProxy.java:75)
 at
 org.wso2.carbon.bpel.core.ode.integration.BPELServerImpl$ODEClusterImpl.getKnownNodes(BPELServerImpl.java:1009)
 at
 org.apache.ode.scheduler.simple.SimpleScheduler.updateHeartBeatAndGetStaleNodes(SimpleScheduler.java:848)
 at
 org.apache.ode.scheduler.simple.SimpleScheduler.access$800(SimpleScheduler.java:53)
 at
 org.apache.ode.scheduler.simple.SimpleScheduler$CheckStaleNodes.run(SimpleScheduler.java:1226)
 at
 org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:810)
 at
 org.apache.ode.scheduler.simple.SimpleScheduler$8.call(SimpleScheduler.java:807)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)

Re: [Dev] Single tenant concurrent application creation fails for more than 10 apps

[Samith Dassanayake]

This code is wrong. As you can see variables "pushed" and "currentPushTry"
are not thread safe in the first method. That might cause the errors.

On Mon, Oct 12, 2015 at 12:23 PM, Aiyadurai Rajeevan 
wrote:

> Hi All,
>
> I have been testing the below code for synchronizing the critical
> resource(remote repo URL), But still some of the pushes are failed.
>
> public boolean push(String remoteRepoUrl, String pushBranch, File repoFile) 
> throws RepositoryMgtException {
> try {
> Git gitRepo = getGitRepository(remoteRepoUrl, repoFile);
> log.info("Remote repo URL>"+remoteRepoUrl);
>
>
> Iterable pushResults = gitRepo.push()
> .setRemote(remoteRepoUrl)
> .setRefSpecs(new RefSpec("refs/heads/" + pushBranch))
> .setCredentialsProvider(getCredentialsProvider())
> .call();
> // we need to verify if git push was successful. Here we can check 
> RemoteRefUpdate status is rejected or not.
> boolean pushed = true;
> int currentPushTry=1;
> for (PushResult pushResult : pushResults) {
> if (pushResult.getRemoteUpdates().size() > 0) {
> Collection refUpdates = 
> pushResult.getRemoteUpdates();
> if (refUpdates != null && refUpdates.size() > 0) {
> log.warn("RefUpdates size==>>"+refUpdates.size());
> for (RemoteRefUpdate refUpdate : refUpdates) {
> if (refUpdate.getStatus() == 
> RemoteRefUpdate.Status.REJECTED_OTHER_REASON ||
> refUpdate.getStatus() == 
> RemoteRefUpdate.Status.REJECTED_NODELETE ||
> refUpdate.getStatus() == 
> RemoteRefUpdate.Status.REJECTED_NONFASTFORWARD ||
> refUpdate.getStatus() == 
> RemoteRefUpdate.Status.REJECTED_REMOTE_CHANGED) {
> log.info("Remote 
> name>>"+refUpdate.getRemoteName());
> pushed = false;
> 
> //pushed=pushFailed(remoteRepoUrl,pushBranch,repoFile);
> log.warn("Failed to push artifacts on repo, 
> So called pushFailed method" + remoteRepoUrl + " due to " +
> refUpdate.getStatus() + " Message " + 
> refUpdate.getMessage()+" Application"+repoFile);
> break;
>
> }
> }
> }
> }
> }
> int maxPushTryCount = 
> Integer.parseInt(AppFactoryUtil.getAppfactoryConfiguration().getFirstProperty(AppFactoryConstants.S2GIT_PUSH_RETRY_COUNT));
> long retrySleepTime = 
> Long.parseLong(AppFactoryUtil.getAppfactoryConfiguration().getFirstProperty(AppFactoryConstants.S2GIT_PUSH_RETRY_SLEEP_TIME));
> log.info("Max push try 
> count"+maxPushTryCount);
> log.info("Retry sleep 
> time=>>>"+retrySleepTime);
> synchronized (remoteRepoUrl) {
> while (currentPushTry < maxPushTryCount && !pushed) {
> //log.info("Thread name in Re 
> try:"+Thread.currentThread().getName());
> Thread.sleep(retrySleepTime * currentPushTry); //Pause for 
> 10*retrycount seconds
> pushed = pushFailed(remoteRepoUrl, pushBranch, repoFile, 
> currentPushTry);
> currentPushTry++;
> }
> }
> return pushed;
>
>
> } catch (RepositoryMgtException e) {
> String msg =
> "Error while pushing  : " + pushBranch + " due to " +
> e.getMessage() + " from RepositoryMgtException";
> log.error(msg, e);
> throw new RepositoryMgtException(msg, e);
> } catch (GitAPIException e) {
> String msg =
> "Error while pushing : " + pushBranch + " due to " +
> e.getMessage() + " from GitAPIException";
> log.error(msg, e);
> throw new RepositoryMgtException(msg, e);
> } catch (InterruptedException e) {
> String msg =
> "Thread is interupted due to " +
> e.getMessage();
> log.error(msg, e);
> return false;
> } catch (AppFactoryException e) {
> e.printStackTrace();
> return false;
> }
>
> }
> public boolean pushFailed(String remoteRepoUrl, String pushBranch, File 
> repoFile,int currentPushTry) throws RepositoryMgtException, GitAPIException {
> log.warn("Re trying " + currentPushTry + " time, for " + repoFile);
> boolean pushed;
> log.info("Lock obtained for remote repo URL: " + remoteRepoUrl);
> Git gitRepo = getGitRepository(remoteRepoUrl, repoFile);
>
> 
> 

[Dev] WSO2 GREG Promote services are not displayed in wso2 gerg-5.0.1

[Akila Nimantha [IT/EKO/LOITS]]

Hi All,

Previously I used wso2 greg-4.6.0 version and now evaluating the latest greg 
version ( 5.0.1 ).
In wso2 greg-4.6.0, promote services are displayed in 
"_system/governance/branches/testing" path successfully.
But in wso2 greg-5.0.1, promote services are not displayed in above path. And 
there is no error mentioned in log files.

Is this an issue in greg-5.0.1 or is there any workarounds for follow to 
promote the service in greg-5.0.1.



Best Regards,

Akila Rathnayake
Software Engineer



This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

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

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Nuwan Dias]

Thanks a lot Chanaka.

On Mon, Oct 12, 2015 at 11:39 AM, Chanaka Fernando 
wrote:

> Hi All,
>
> This issue is fixed with the following PR [1]. Thanks for reporting and
> helping us to figure out the issue.
>
> [1] https://github.com/wso2/carbon-mediation/pull/467
>
> On Fri, Oct 9, 2015 at 3:41 PM, Chanaka Fernando 
> wrote:
>
>> Hi Sameera,
>>
>> Your judgment is correct and it helped us to find the root cause :). I'll
>> fix the code from carbon-mediation side. Thanks for your input.
>>
>> On Fri, Oct 9, 2015 at 3:19 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Chanaka,
>>>
>>> You don't need to destroy the current context. This part is handle by
>>> the Kernel code. Users of the CarbonContext API do not need to worry about
>>> destroying the context.
>>>
>>> Who has done this change? So my initial judgment is correct. :) Stack
>>> cannot become empty.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Thu, Oct 8, 2015 at 6:14 PM, Chanaka Fernando 
>>> wrote:
>>>
 Hi All,

 At last, I was able to find the root cause for this behavior. This is
 actually coming from carbon-mediation code. What actually happens is that
 when ESB starts with a tenant, it will not load the tenant until it
 receives the first request. When It receives the first request, it will
 call the MultitenantMessageReceiver.processRequest() method. Within this
 method, it will call the following method.

 PrivilegedCarbonContext.startTenantFlow();


 This will get the ThreadLocal variable *parentContextHolderStack *and
 get the stack  and push the carbonContextDataHolder object to the
 stack. After this, tenant loading happens and within the initialization of
 the carbon mediation registry we have the following code segment.

 *org.wso2.carbon.mediation.registry.WSO2Registry.java*

 /**
  *  Carbon Kernel mandates to set Threadlocal before calling anything in 
 kernel
  */
 private void setTenantInfo() {
 // Preserve user name
 String username = 
 PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername();
 *PrivilegedCarbonContext.destroyCurrentContext();*
 PrivilegedCarbonContext cc = 
 PrivilegedCarbonContext.getThreadLocalCarbonContext();
 cc.setTenantDomain(domain);
 cc.setTenantId(tenantId);
 if (username != null) { // Set back the user name
 
 PrivilegedCarbonContext.getThreadLocalCarbonContext().setUsername(username);
 }
 }

 Within the above method following line causes the issue.

 PrivilegedCarbonContext.destroyCurrentContext();

 When this method is called, it will reset the *parentContextHolderStack
 *and the initial object push into the stack is destroyed. Then after
 tenant loading, within the MultitenantMessageReceiver.processRequest()
 method, it tries to end the tenant flow within finally block and try to pop
 the object which it pushes early. But right now, we have a new context
 stack and it will throw the emptyStackException due to that.

 @Sameera/KasunG: Do we really need to use the following code segment
 within the above method?


 *PrivilegedCarbonContext.destroyCurrentContext();*

 I saw this method called within carbon-mediation components in 3
 different locations. AFAIU, we don't need to destroy the current context
 when we are accessing the ThreadLocalContext. Please share your thoughts
 such that we can fix this issue. Issue is fixed when I comment out the
 above line :)


 Thanks,
 Chanaka



 On Wed, Oct 7, 2015 at 5:34 PM, Chanaka Fernando 
 wrote:

> Hi Sameera/KasunG,
>
> I have debugged the code to find the root cause for this empty stack
> exception. This is causing several other issues at the ESB layer. What
> actually happens is that inside the
> MultitenantMessageReceiver.processRequest() method, we have the following
> code segment.
>
> try {
> PrivilegedCarbonContext.startTenantFlow();
> PrivilegedCarbonContext privilegedCarbonContext = 
> PrivilegedCarbonContext.getThreadLocalCarbonContext();
> privilegedCarbonContext.setTenantDomain(tenantDomain, true);
> // this is to prevent non-blocking transports from sending 202
> 
> mainInMsgContext.getOperationContext().setProperty(Constants.RESPONSE_WRITTEN,
>  "SKIP");
>
> ConfigurationContext tenantConfigCtx =
>
> TenantAxisUtils.getTenantConfigurationContext(tenantDomain,
>   
>mainConfigCtx);
> if (tenantConfigCtx == null) {
> // Throw AxisFault: Tenant does not exist

Re: [Dev] [DEV][BPS] Clarification on bps dbscripts

[Sashika Wijesinghe]

Hi Firzhan,

There scripts to drop and truncate as well. Appreciate your help in
clarifying below issues.

1. In /dbscripts/bps/bpel/drop there are scripts to drop the
tables in BPS database.

To verify the scripts, I stopped the BPS server and drop tables using the
given 'drop scripts' and recreate the tables using given 'create scripts'.
After restarting the server, "*[2015-10-12 11:33:14,791] ERROR
{org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
 Cannot find DeploymentUnitDAO instance for package AdderProcess-1.*" error
noted in terminal. This is because the package details are available in
registry database.

Further it is not possible to continue the work by deploying a new bpel
process due to corrupted process. I had to undeploy the corrupted bpel
process to continue work.

Is there any recommended best practice to use the drop bps scripts? If so
it should be documented because these scripts are bundled with the BPS
package itself.


Thanks

On Fri, Oct 9, 2015 at 5:56 PM, Firzhan Naqash  wrote:

> Hi,
>
> Those scripts are used to create the necessary database schema for bpel.
> Without executing this scripts, you won't be able to start the bps server.
>
> As a first step, after configuring the bps-datasources.xml file, you have
> to execute this script against your preferred database. Or else if you have
> necessary database permissions, you can start the server with -Dsetup
> option.
>
> Regards,
> Firzhan
>
>
> --
> *Firzhan Naqash*
> Senior Software Engineer - Integration Platform Team
> WSO2 Inc. http://wso2.com
>
> email: firz...@wso2.com 
> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
> blog: http://firzhanblogger.blogspot.com/
>   *
> *twitter: https://twitter.com/firzhan007
>  | linked-in: 
> **https://www.linkedin.com/in/firzhan
> *
>
> On Fri, Oct 9, 2015 at 5:51 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> There were bpel database scripts under /dbscripts/bps/bpel. May
>> I know the real usecase of these scripts? Is there any specific
>> pre-conditions that needs to follow before executing these scripts?
>>
>> Thanks
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 3

[Kavith Lokuhewage]

Hi Devs,

Please vote for the third release candidate of WSO2 Developer Studio 3.8.0.

This release fixes following issues.
https://wso2.org/jira/issues/?filter=12450

Please download, test and vote. Vote will be open for 72 hours or as needed.

Sources, binary distribution and pre-installed eclipse distributions:
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC3/

The tag to be voted upon:
https://github.com/wso2/developer-studio/tree/v3.8.0-RC3


[+] Stable - go ahead and release
[-]  Broken - do not release (explain why)

Thanks and Regards,
DevStudio Team

-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

[Dev] How to retrieve a chain of SSL certificates from a server

[Thilini Cooray]

Hi,

I want to import a chain of certificates from a server.

Following command show me the entire certificate chain

  *openssl s_client -connect : -showcerts*

Following command only writes first certificate on the chain to a file

  *openssl s_client -showcerts -connect : /dev/null|openssl x509 -outform PEM >mycertfile.pem*

Is there a way I can save all the certificates in the chain to local files
without copy and pasting one by one ?

Thanks.
-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can I access axis2MessageContext within the script mediator?

[Amila Maha Arachchi]

Hi,

I want to set a property in axis2MessageContext from the script mediator in
ESB or API Manager. According to the doc [1], script mediator has not
exposed the axis2MessageContext to the script mediator.

$Subject?

My original requirement is to set a response code for a resource of a
prototyped api on api manager. There is a property named HTTP_SC which
needs to be set in axis2MessageContext.

[1] https://docs.wso2.com/display/ESB480/Script+Mediator

Regards,
Amila.

-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Rajith Roshan]

Congratz !!!

On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe  wrote:

> Congratulations :)
>
> On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe  > wrote:
>
>> Congratulations Sasikala!! :)
>>
>> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
>> kirishan...@wso2.com> wrote:
>>
>>> Congrats Sasikala !
>>>
>>> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda 
>>> wrote:
>>>
 Thanks all... :)

 And special thanks to the MB team for the help that I've received so
 far... :)

 On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe 
 wrote:

> Hi Sasikala,
> Congratulations!
> It is with great pleasure that we welcome you as a WSO2 committer.
> Keep up the good work!
> regards,
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
>
>


 --
 Sasikala Kottegoda
 *Software Engineer*
 WSO2 Inc., http://wso2.com/
 lean. enterprise. middleware
 Mobile: +94 774835928/712792401

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


>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Kirishanthy
>>> Associate Software Engineer
>>> Mobile : +94 778333939
>>> kirishan...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Hariprasath Thanarajah]

Congratz Sasikala !

On Mon, Oct 12, 2015 at 3:15 PM, Rajith Roshan  wrote:

> Congratz !!!
>
> On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe 
> wrote:
>
>> Congratulations :)
>>
>> On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe <
>> malint...@wso2.com> wrote:
>>
>>> Congratulations Sasikala!! :)
>>>
>>> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
>>> kirishan...@wso2.com> wrote:
>>>
 Congrats Sasikala !

 On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda  wrote:

> Thanks all... :)
>
> And special thanks to the MB team for the help that I've received so
> far... :)
>
> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe 
> wrote:
>
>> Hi Sasikala,
>> Congratulations!
>> It is with great pleasure that we welcome you as a WSO2 committer.
>> Keep up the good work!
>> regards,
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>>
>>
>
>
> --
> Sasikala Kottegoda
> *Software Engineer*
> WSO2 Inc., http://wso2.com/
> lean. enterprise. middleware
> Mobile: +94 774835928/712792401
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thanks & Regards,
 Kirishanthy
 Associate Software Engineer
 Mobile : +94 778333939
 kirishan...@wso2.com

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


>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Thank you and Regards**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Apim] Reason for endpoint suspension

[Malith Munasinghe]

Hi All,

Recently we faced an endpoint suspension from api gateway. Can I know the
possible reasons to get an endpoint suspended. Went through the gateway
logs but it doesn't provide much information of the possible cause apart
from saying the endpoint failed.

Regards,
Malith

-- 
Malith Munasinghe | Software Engineer
M: +94 (071) 9401122
E: mali...@wso2.com
W: http://wso2.com


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

Re: [Dev] [DEV][BPS] Clarification on bps dbscripts

[Sashika Wijesinghe]

Hi Hasitha,

Thanks for the information. These information is not documented in BPS
documentation, therefore raised a documentation jira. (
https://wso2.org/jira/browse/DOCUMENTATION-2529)

Regards,

On Mon, Oct 12, 2015 at 1:39 PM, Hasitha Aravinda  wrote:

> Hi Sashika,
>
> Drop/Truncate scripts are used to recreate fresh environments.  Specially
> these scripts will be useful, when you are working with restricted
> environments like where you don't have privileges to create databases, etc.
> Some users want these scripts specially when they do load tests.
>
> Since you have dropped only bps database, this is expected. Since we are
> creating fresh environment, we need to drop registry tables and re-create
> them. AFAIK registry doesn't have drop scripts. Also we need to remove
> previous deployed artifacts from file system as well.
>
> Thanks
> Hasitha.
>
>
>
>
> On Mon, Oct 12, 2015 at 11:59 AM, Sashika Wijesinghe 
> wrote:
>
>> Hi Firzhan,
>>
>> There scripts to drop and truncate as well. Appreciate your help in
>> clarifying below issues.
>>
>> 1. In /dbscripts/bps/bpel/drop there are scripts to drop the
>> tables in BPS database.
>>
>> To verify the scripts, I stopped the BPS server and drop tables using the
>> given 'drop scripts' and recreate the tables using given 'create scripts'.
>> After restarting the server, "*[2015-10-12 11:33:14,791] ERROR
>> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>>  Cannot find DeploymentUnitDAO instance for package AdderProcess-1.*"
>> error noted in terminal. This is because the package details are available
>> in registry database.
>>
>> Further it is not possible to continue the work by deploying a new bpel
>> process due to corrupted process. I had to undeploy the corrupted bpel
>> process to continue work.
>>
>> Is there any recommended best practice to use the drop bps scripts? If so
>> it should be documented because these scripts are bundled with the BPS
>> package itself.
>>
>>
>> Thanks
>>
>> On Fri, Oct 9, 2015 at 5:56 PM, Firzhan Naqash  wrote:
>>
>>> Hi,
>>>
>>> Those scripts are used to create the necessary database schema for bpel.
>>> Without executing this scripts, you won't be able to start the bps server.
>>>
>>> As a first step, after configuring the bps-datasources.xml file, you
>>> have to execute this script against your preferred database. Or else if you
>>> have necessary database permissions, you can start the server with -Dsetup
>>> option.
>>>
>>> Regards,
>>> Firzhan
>>>
>>>
>>> --
>>> *Firzhan Naqash*
>>> Senior Software Engineer - Integration Platform Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: firz...@wso2.com 
>>> mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
>>> blog: http://firzhanblogger.blogspot.com/
>>>   *
>>> *twitter: https://twitter.com/firzhan007
>>>  | linked-in: 
>>> **https://www.linkedin.com/in/firzhan
>>> *
>>>
>>> On Fri, Oct 9, 2015 at 5:51 PM, Sashika Wijesinghe 
>>> wrote:
>>>
 Hi All,

 There were bpel database scripts under /dbscripts/bps/bpel.
 May I know the real usecase of these scripts? Is there any specific
 pre-conditions that needs to follow before executing these scripts?

 Thanks
 --

 *Sashika WijesingheSoftware Engineer - QA Team*
 Mobile : +94 (0) 774537487
 sash...@wso2.com

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


>>>
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Malintha Amarasinghe]

Congratulations Sasikala!! :)

On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
kirishan...@wso2.com> wrote:

> Congrats Sasikala !
>
> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda 
> wrote:
>
>> Thanks all... :)
>>
>> And special thanks to the MB team for the help that I've received so
>> far... :)
>>
>> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe 
>> wrote:
>>
>>> Hi Sasikala,
>>> Congratulations!
>>> It is with great pleasure that we welcome you as a WSO2 committer. Keep
>>> up the good work!
>>> regards,
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>>
>>
>>
>> --
>> Sasikala Kottegoda
>> *Software Engineer*
>> WSO2 Inc., http://wso2.com/
>> lean. enterprise. middleware
>> Mobile: +94 774835928/712792401
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Kirishanthy
> Associate Software Engineer
> Mobile : +94 778333939
> kirishan...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

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

Re: [Dev] [Apim] Reason for endpoint suspension

[Malith Munasinghe]

Hi Tharindu,

Actually this is an api we are using to test the availability of api
gateway. Disabling the suspension will not be helpful in this scenario. Is
there any idea on which occurrences an endpoint suspension can occur ?

Regards,
Malith

On Mon, Oct 12, 2015 at 5:00 PM, Tharindu Dharmarathna 
wrote:

> Hi Malith,
>
> Can you check the API definition of that under synapse configuration you
> can set it to never suspended by advanced configuration in Implement section
>
> Thanks
> Tharindu
> ​
>
>
> On Mon, Oct 12, 2015 at 3:56 PM, Malith Munasinghe 
> wrote:
>
>> Hi All,
>>
>> Recently we faced an endpoint suspension from api gateway. Can I know the
>> possible reasons to get an endpoint suspended. Went through the gateway
>> logs but it doesn't provide much information of the possible cause apart
>> from saying the endpoint failed.
>>
>> Regards,
>> Malith
>>
>> --
>> Malith Munasinghe | Software Engineer
>> M: +94 (071) 9401122
>> E: mali...@wso2.com
>> W: http://wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Associate Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <%2B94779109091>*
>



-- 
Malith Munasinghe | Software Engineer
M: +94 (071) 9401122
E: mali...@wso2.com
W: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Apim] Reason for endpoint suspension

[Tharindu Dharmarathna]

Hi Malith,

Can you check the API definition of that under synapse configuration you
can set it to never suspended by advanced configuration in Implement section

Thanks
Tharindu
​


On Mon, Oct 12, 2015 at 3:56 PM, Malith Munasinghe  wrote:

> Hi All,
>
> Recently we faced an endpoint suspension from api gateway. Can I know the
> possible reasons to get an endpoint suspended. Went through the gateway
> logs but it doesn't provide much information of the possible cause apart
> from saying the endpoint failed.
>
> Regards,
> Malith
>
> --
> Malith Munasinghe | Software Engineer
> M: +94 (071) 9401122
> E: mali...@wso2.com
> W: http://wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharindu Dharmarathna*Associate Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] Can I access axis2MessageContext within the script mediator?

[Kevin Ratnasekera]

Hi Amila,
I have gone through the script mediator code/config, I dont think we might
able to access axis2MessageContext other than the SynapseMessageContext.
Can't we use either Property mediator or class mediator in this specific
use case?
Regards
Kevin

On Mon, Oct 12, 2015 at 2:23 PM, Amila Maha Arachchi 
wrote:

> Hi,
>
> I want to set a property in axis2MessageContext from the script mediator
> in ESB or API Manager. According to the doc [1], script mediator has not
> exposed the axis2MessageContext to the script mediator.
>
> $Subject?
>
> My original requirement is to set a response code for a resource of a
> prototyped api on api manager. There is a property named HTTP_SC which
> needs to be set in axis2MessageContext.
>
> [1] https://docs.wso2.com/display/ESB480/Script+Mediator
>
> Regards,
> Amila.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Chanaka Fernando]

Many congratulations Sasikala !!! Keep up the good work !!!

On Mon, Oct 12, 2015 at 5:10 PM, Viraj Senevirathne  wrote:

> Congrats Sasikala
>
> On Mon, Oct 12, 2015 at 3:20 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Congratz Sasikala !
>>
>> On Mon, Oct 12, 2015 at 3:15 PM, Rajith Roshan  wrote:
>>
>>> Congratz !!!
>>>
>>> On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe 
>>> wrote:
>>>
 Congratulations :)

 On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe <
 malint...@wso2.com> wrote:

> Congratulations Sasikala!! :)
>
> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
> kirishan...@wso2.com> wrote:
>
>> Congrats Sasikala !
>>
>> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda <
>> sasik...@wso2.com> wrote:
>>
>>> Thanks all... :)
>>>
>>> And special thanks to the MB team for the help that I've received so
>>> far... :)
>>>
>>> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe >> > wrote:
>>>
 Hi Sasikala,
 Congratulations!
 It is with great pleasure that we welcome you as a WSO2 committer.
 Keep up the good work!
 regards,

 --
 Ramith Jayasinghe
 Technical Lead
 WSO2 Inc., http://wso2.com
 lean.enterprise.middleware



>>>
>>>
>>> --
>>> Sasikala Kottegoda
>>> *Software Engineer*
>>> WSO2 Inc., http://wso2.com/
>>> lean. enterprise. middleware
>>> Mobile: +94 774835928/712792401
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Kirishanthy
>> Associate Software Engineer
>> Mobile : +94 778333939
>> kirishan...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Isuru Wijesinghe
 *Software Engineer*
 Mobile: 0710933706
 isur...@wso2.com

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


>>>
>>>
>>> --
>>> Rajith Roshan
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>>
>> *Thank you and Regards**Hariprasath Thanarajah*
>> Associate Software Engineer | WSO2
>> E: haripras...@wso2.com
>> M: +94752806528
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Viraj Senevirathne
> Software Engineer; WSO2, Inc.
>
> Mobile : +94 71 958 0269
> Email : vir...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Viraj Senevirathne]

Congrats Sasikala

On Mon, Oct 12, 2015 at 3:20 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Congratz Sasikala !
>
> On Mon, Oct 12, 2015 at 3:15 PM, Rajith Roshan  wrote:
>
>> Congratz !!!
>>
>> On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe 
>> wrote:
>>
>>> Congratulations :)
>>>
>>> On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Congratulations Sasikala!! :)

 On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
 kirishan...@wso2.com> wrote:

> Congrats Sasikala !
>
> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda <
> sasik...@wso2.com> wrote:
>
>> Thanks all... :)
>>
>> And special thanks to the MB team for the help that I've received so
>> far... :)
>>
>> On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe 
>> wrote:
>>
>>> Hi Sasikala,
>>> Congratulations!
>>> It is with great pleasure that we welcome you as a WSO2 committer.
>>> Keep up the good work!
>>> regards,
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>>
>>>
>>
>>
>> --
>> Sasikala Kottegoda
>> *Software Engineer*
>> WSO2 Inc., http://wso2.com/
>> lean. enterprise. middleware
>> Mobile: +94 774835928/712792401
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Kirishanthy
> Associate Software Engineer
> Mobile : +94 778333939
> kirishan...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Malintha Amarasinghe
 Software Engineer
 *WSO2, Inc. - lean | enterprise | middleware*
 http://wso2.com/

 Mobile : +94 712383306

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


>>>
>>>
>>> --
>>> Isuru Wijesinghe
>>> *Software Engineer*
>>> Mobile: 0710933706
>>> isur...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Roshan
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Viraj Senevirathne
Software Engineer; WSO2, Inc.

Mobile : +94 71 958 0269
Email : vir...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 4.9.0] Different ESB configs for Message Processor.

[Ajith Vitharana]

Hi Ravindra,



On Mon, Oct 12, 2015 at 1:07 AM, Ravindra Ranwala  wrote:

> Hi Ajith,
>
> This is not a bug in the MP, rather it is a configuration related issue.
> Here a getQuote request is sent which is a classical IN-OUT scenario.
> Therefore you are getting a response. If you are getting a response you
> need to define a reply sequence at the MP. Otherwise the MP has no way of
> handling the response.
>

Thank you  for the explanation. But this information is not available in
the doc [1].  Could you please document ,  then resolve the tickets ?

Reply sequence name (message.processor.reply.sequence)

The name of the sequence where the message reply should be sent.

No

[1]
https://docs.wso2.com/display/ESB490/Scheduled+Message+Forwarding+Processor

-Ajith



> Please define a simple reply sequence and point the MP to that. Also
> create a Documentation issue to include it in our documentation [1]. Also I
> guess we can resolve the jira issue [2] since it is not a bug in ESB,
> rather a documentation issue.
>
> A sample reply sequence config is given below.
>
>
> 
> http://ws.apache.org/ns/synapse; name="replySequence">
>
>   
>
>
> 
>
>
>
>
>
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
> [2] https://wso2.org/jira/browse/ESBJAVA-4263
>
>
> Thanks & Regards,
>
> On Sun, Oct 11, 2015 at 3:26 AM, Ajith Vitharana  wrote:
>
>> Hi All.
>>
>> Created JIRAs for above issues.
>>
>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2524
>> [2] https://wso2.org/jira/browse/ESBJAVA-4263
>>
>> -Ajith
>>
>> On Wed, Oct 7, 2015 at 12:48 AM, Ajith Vitharana  wrote:
>>
>>>
>>>
>>> On Wed, Oct 7, 2015 at 12:43 AM, Yasassri Ratnayake 
>>> wrote:
>>>
 According to [1]  "*The deactivate sequence that will be executed when
 the processor is deactivated automatically. Automatic deactivation occurs
 when the maximum delivery attempts is exceeded and the Drop message after
 maximum delivery attempts parameter is disabled.*"

 [1] - https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor

>>>
>>>
>>> The backed is available *BEFORE* exceed the max delivery attempts. But
>>> still message processor going to deactivate ?
>>>
>>> -Ajith
>>>

 On Wed, Oct 7, 2015 at 10:06 AM, Ajith Vitharana 
 wrote:

> Other issue is,
>
> 1. According to the sample I'm shutting down the backend-1  and send a
> request.
> 2. Now I can see the message store has one message.
> 3. Before 50 delivery attempts , start the backend-1
> 4. Now I  can see the message processor executed and message delivered
>  to backed-1
>
> But just after sending the message, the  message processor going to
> deactivate state and printing following exception.
>
> [2015-10-07 00:25:03,987]  WARN - ForwardingService Failed to send the
> message through the fault sequence. Sequence name does not Exist.
> *[2015-10-07 00:25:05,335]  WARN - ForwardingService Failed to send
> the message through the deactivate sequence. Sequence name does not 
> Exist.*
> [2015-10-07 00:25:05,340]  INFO - ScheduledMessageProcessor
> Successfully deactivated the message processor [send_pending_message]
> *[2015-10-07 00:25:05,341] ERROR - ForwardingService Failed to send
> the out message. Reply sequence does not Exist. Deactivated the message
> processor*
>
>
> 1. According to the WARN log , what is the deactivate sequence should
> define ?
> 2. Why message processor is deactivate just after sending message to
> back end ?
>
> -Ajith
>
>
> On Tue, Oct 6, 2015 at 11:39 PM, Ajith Vitharana 
> wrote:
>
>> Hi Yasassri.
>>
>> Yes. According to the carbon commits it has renamed. Then those
>> configs never tested after 2012 :)
>>
>> [1] https://wso2.org/jira/browse/CARBON-13114
>>
>> -Ajith
>>
>>
>> Author: ishan
>> Date: Fri Jun 15 02:00:53 2012
>> New Revision: 130164
>> URL: http://wso2.org/svn/browse/wso2?view=rev=130164
>>
>> Log:
>> Fixing CARBON-13114 with the patch of CharithaM.
>>
>> Modified:
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/org/wso2/carbon/message/processor/ui/i18n/
>> Resources.properties
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/index.jsp
>>carbon/platform/trunk/components/mediation/message-
>> processor/org.wso2.carbon.message.processor.ui/src/main/
>> resources/web/message_processor/manageMessageForwardingProcessor.jsp
>>
>> Modified: carbon/platform/trunk/components/mediation/message-
>> 

Re: [Dev] Error decoding authorization header while calling oAuth token endpoint

[Sachith Punchihewa]

Hi Inosh,

Try changing the curl to the format mentioned below.
curl -k -d "grant_type=password=admin=admin" -H
"Authorization:Basic xx" -H "Content-Type:
application/x-www-form-urlencoded" https://localhost:9443/oauth2/token

New IS versions doesn't support curls which has headers separated with
commas since it extract the Content type header also as a part of
Authorization header.
For more info refer the mail tread[1]

[1]. [DEV][IS] Getting an error when try to rtriw a Oauth token from IS
server.

Thanks & Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Mon, Oct 12, 2015 at 7:23 PM, Inosh Perera  wrote:

> Hi all,
>
> While calling the oAuth token endpoint to get tokens, I get the following
> error. What could be the reason for the issue?
>
> [2015-10-12 18:26:21,279] ERROR
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  Error while extracting credentials from authorization header
> org.wso2.carbon.identity.oauth.common.exception.OAuthClientException:
> Error decoding authorization header. Could not retrieve client id and
> client secret.
> at
> org.wso2.carbon.identity.oauth.endpoint.util.EndpointUtil.extractCredentialsFromAuthzHeader(EndpointUtil.java:153)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:87)
> 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:188)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
> at
> 

[Dev] Error decoding authorization header while calling oAuth token endpoint

[Inosh Perera]

Hi all,

While calling the oAuth token endpoint to get tokens, I get the following
error. What could be the reason for the issue?

[2015-10-12 18:26:21,279] ERROR
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 Error while extracting credentials from authorization header
org.wso2.carbon.identity.oauth.common.exception.OAuthClientException: Error
decoding authorization header. Could not retrieve client id and client
secret.
at
org.wso2.carbon.identity.oauth.endpoint.util.EndpointUtil.extractCredentialsFromAuthzHeader(EndpointUtil.java:153)
at
org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:87)
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:188)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationHandler.invoke(WebappAuthenticationHandler.java:43)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at

Re: [Dev] Can I access axis2MessageContext within the script mediator?

[Amila Maha Arachchi]

Thanks for the reply Kevin.

In my case, I want the axis2MessageContext to be available for the script
mediator because script mediator is the one used when creating prototype
APIs in API manager. As you have suggested, I can use the property
mediator. But, it has to be done after publishing the api (i.e. I have to
edit the api xml). Problem with this is, when we republish the api, these
changes gets vanished and I have to redo them. And, in my case, user does
not have access to the file system to edit the api xml. Thats why I was
trying to do this via the script mediator and api publisher UI.

Regards,
Amila.

On Mon, Oct 12, 2015 at 6:02 PM, Kevin Ratnasekera  wrote:

> Hi Amila,
> I have gone through the script mediator code/config, I dont think we might
> able to access axis2MessageContext other than the SynapseMessageContext.
> Can't we use either Property mediator or class mediator in this specific
> use case?
> Regards
> Kevin
>
> On Mon, Oct 12, 2015 at 2:23 PM, Amila Maha Arachchi 
> wrote:
>
>> Hi,
>>
>> I want to set a property in axis2MessageContext from the script mediator
>> in ESB or API Manager. According to the doc [1], script mediator has not
>> exposed the axis2MessageContext to the script mediator.
>>
>> $Subject?
>>
>> My original requirement is to set a response code for a resource of a
>> prototyped api on api manager. There is a property named HTTP_SC which
>> needs to be set in axis2MessageContext.
>>
>> [1] https://docs.wso2.com/display/ESB480/Script+Mediator
>>
>> Regards,
>> Amila.
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Issue in Android Enrollment

[Sachith Punchihewa]

Hi Dileesha,

The issue might be in the server.This happens when the server not returning
the full certificate chain.Try changing that.
For more information refer [1] and [2].

[1]. http://superuser.com/questions/347588/how-do-ssl-chains-work
[2].
http://stackoverflow.com/questions/13862908/ssl-certificate-is-not-trusted-on-mobile-only

Thanks & Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Mon, Oct 12, 2015 at 5:56 PM, Dileesha Rajapakse 
wrote:

> Hi,
>
> The Android Enrollment fails and produces the error below.
>
> 10-12 17:42:06.494   7068-10049/org.wso2.emm.agent E/ServerUtilities﹕
> Error occurred while sending 'Post' request due to failure of server
> connection
> 10-12 17:42:06.504   7068-10049/org.wso2.emm.agent E/DynamicClientManager﹕
> Failed to contact server
> org.wso2.emm.agent.proxy.IDPTokenManagerException: Error occurred
> while sending 'Post' request due to failure of server connection
> at
> org.wso2.emm.agent.proxy.utils.ServerUtilities.sendPostRequest(ServerUtilities.java:252)
> at
> org.wso2.emm.agent.proxy.utils.ServerUtilities.postData(ServerUtilities.java:142)
> at
> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:137)
> at
> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:125)
> at android.os.AsyncTask$2.call(AsyncTask.java:288)
> at java.util.concurrent.FutureTask.run(FutureTask.java:237)
> at
> android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
> at java.lang.Thread.run(Thread.java:818)
>  *Caused by: javax.net.ssl.SSLPeerUnverifiedException: No peer
> certificate*
> at
> com.android.org.conscrypt.SSLNullSession.getPeerCertificates(SSLNullSession.java:104)
> at
> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:93)
> at
> org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:388)
> at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:214)
> at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:167)
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)
> at
> org.apache.http.impl.client.DefaultRequestDirector.executeOriginal(DefaultRequestDirector.java:1292)
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:700)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:691)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:514)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:492)
> at
> org.wso2.emm.agent.proxy.utils.ServerUtilities.sendPostRequest(ServerUtilities.java:235)
> at
> org.wso2.emm.agent.proxy.utils.ServerUtilities.postData(ServerUtilities.java:142)
> at
> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:137)
> at
> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:125)
> at android.os.AsyncTask$2.call(AsyncTask.java:288)
> at java.util.concurrent.FutureTask.run(FutureTask.java:237)
> at
> android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
> at java.lang.Thread.run(Thread.java:818)
>
> One of the causes could be a conflict in resolving "http" and "https" at
> the back-end.
>
> Thank You
> --
> Dileesha Rajapakse
> *Intern - Engineering*
> Mobile : +94 (0) 772 555 933

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 3

[Supun Malinga]

Hi Kavith,

Can you pls mention what are the new features in 3.8.0 ?.

thanks,

On Mon, Oct 12, 2015 at 3:05 AM, Kavith Lokuhewage  wrote:

> Hi Devs,
>
> Please vote for the third release candidate of WSO2 Developer Studio 3.8.0.
>
> This release fixes following issues.
> https://wso2.org/jira/issues/?filter=12450
>
> Please download, test and vote. Vote will be open for 72 hours or as
> needed.
>
> Sources, binary distribution and pre-installed eclipse distributions:
> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC3/
>
> The tag to be voted upon:
> https://github.com/wso2/developer-studio/tree/v3.8.0-RC3
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards,
> DevStudio Team
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error when calling token endpoint

[Harshan Liyanage]

Adding to @dev,

Harshan Liyanage
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.

On Mon, Oct 12, 2015 at 7:14 PM, Sachith Punchihewa 
wrote:

> Hi Inosh,
>
> Try changing the curl to the format mentioned below.
> curl -k -d "grant_type=password=admin=admin" -H
> "Authorization:Basic xx" -H "Content-Type:
> application/x-www-form-urlencoded" https://localhost:9443/oauth2/token
>
> New IS version doesn't support curls which has headers separated with
> commas since it extract the Content type header also as a part of
> Authorization header.
> For more info refer the mail tread[1]
>
> [1]. [DEV][IS] Getting an error when try to rtriw a Oauth token from IS
> server.
>
> Thanks & Regards.
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Mon, Oct 12, 2015 at 6:49 PM, Harshan Liyanage 
> wrote:
>
>> Hi Inosh,
>>
>> Possibly you must be sending client credentials in a wrong format or
>> there's something wrong with Base64 encoding. Pls check it.
>>
>> Thanks,
>>
>> Harshan Liyanage
>> Software Engineer
>> Mobile: *+94724423048*
>> Email: hars...@wso2.com
>> Blog : http://harshanliyanage.blogspot.com/
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> On Mon, Oct 12, 2015 at 6:38 PM, Inosh Perera  wrote:
>>
>>> Hi guys,
>>>
>>> Anyone working on $subbject? Anyone getting the same result? Android
>>> guys?
>>>
>>> [2015-10-12 18:26:21,279] ERROR
>>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>>  Error while extracting credentials from authorization header
>>> org.wso2.carbon.identity.oauth.common.exception.OAuthClientException:
>>> Error decoding authorization header. Could not retrieve client id and
>>> client secret.
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.util.EndpointUtil.extractCredentialsFromAuthzHeader(EndpointUtil.java:153)
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:87)
>>> 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:188)
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>> at
>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
>>> at
>>> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
>>> at
>>> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
>>> at
>>> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
>>> at
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
>>> at
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>> at
>>> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
>>> at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>> at
>>> 

Re: [Dev] [Apim] Reason for endpoint suspension

[Harsha Kumara]

Hi Malith,

AFAIK endpoint suspension occurs when there is a fault occur upon a
endpoint. Request sent to endpoint may result in a fault either endpoint
down, timeout and etc. Resources in [1] should be helpful.
Using advanced configs which Tharindu mentioned above will be useful to
handle it.

[1] - https://docs.wso2.com/display/ESB470/Endpoint+Error+Handling

Thanks,
Harsha

On Mon, Oct 12, 2015 at 9:57 PM, Malith Munasinghe  wrote:

> Hi Tharindu,
>
> Actually this is an api we are using to test the availability of api
> gateway. Disabling the suspension will not be helpful in this scenario. Is
> there any idea on which occurrences an endpoint suspension can occur ?
>
> Regards,
> Malith
>
> On Mon, Oct 12, 2015 at 5:00 PM, Tharindu Dharmarathna  > wrote:
>
>> Hi Malith,
>>
>> Can you check the API definition of that under synapse configuration you
>> can set it to never suspended by advanced configuration in Implement section
>>
>> Thanks
>> Tharindu
>> ​
>>
>>
>> On Mon, Oct 12, 2015 at 3:56 PM, Malith Munasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> Recently we faced an endpoint suspension from api gateway. Can I know
>>> the possible reasons to get an endpoint suspended. Went through the gateway
>>> logs but it doesn't provide much information of the possible cause apart
>>> from saying the endpoint failed.
>>>
>>> Regards,
>>> Malith
>>>
>>> --
>>> Malith Munasinghe | Software Engineer
>>> M: +94 (071) 9401122
>>> E: mali...@wso2.com
>>> W: http://wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Associate Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>
>
>
> --
> Malith Munasinghe | Software Engineer
> M: +94 (071) 9401122
> E: mali...@wso2.com
> W: http://wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Apim] Reason for endpoint suspension

[Malith Munasinghe]

Hi Harsha,

Thanks for the information and resources shared. I managed to figure out
that this is occurred due to a connection failure between gateway and the
endpoint.

Regards,
Malith.

On Mon, Oct 12, 2015 at 11:20 PM, Harsha Kumara  wrote:

> Hi Malith,
>
> AFAIK endpoint suspension occurs when there is a fault occur upon a
> endpoint. Request sent to endpoint may result in a fault either endpoint
> down, timeout and etc. Resources in [1] should be helpful.
> Using advanced configs which Tharindu mentioned above will be useful to
> handle it.
>
> [1] - https://docs.wso2.com/display/ESB470/Endpoint+Error+Handling
>
> Thanks,
> Harsha
>
> On Mon, Oct 12, 2015 at 9:57 PM, Malith Munasinghe 
> wrote:
>
>> Hi Tharindu,
>>
>> Actually this is an api we are using to test the availability of api
>> gateway. Disabling the suspension will not be helpful in this scenario. Is
>> there any idea on which occurrences an endpoint suspension can occur ?
>>
>> Regards,
>> Malith
>>
>> On Mon, Oct 12, 2015 at 5:00 PM, Tharindu Dharmarathna <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Malith,
>>>
>>> Can you check the API definition of that under synapse configuration you
>>> can set it to never suspended by advanced configuration in Implement section
>>>
>>> Thanks
>>> Tharindu
>>> ​
>>>
>>>
>>> On Mon, Oct 12, 2015 at 3:56 PM, Malith Munasinghe 
>>> wrote:
>>>
 Hi All,

 Recently we faced an endpoint suspension from api gateway. Can I know
 the possible reasons to get an endpoint suspended. Went through the gateway
 logs but it doesn't provide much information of the possible cause apart
 from saying the endpoint failed.

 Regards,
 Malith

 --
 Malith Munasinghe | Software Engineer
 M: +94 (071) 9401122
 E: mali...@wso2.com
 W: http://wso2.com

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


>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Associate Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <%2B94779109091>*
>>>
>>
>>
>>
>> --
>> Malith Munasinghe | Software Engineer
>> M: +94 (071) 9401122
>> E: mali...@wso2.com
>> W: http://wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>



-- 
Malith Munasinghe | Software Engineer
M: +94 (071) 9401122
E: mali...@wso2.com
W: http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

[Milinda Perera]

Hi,

Please review and merge PR : https://github.com/wso2/orbit/pull/139

Please refer following information about the changes and upgrades:

*jsr94*

jsr94 used by BRS.
Currently jsr94 in located in SVN orrbit [1] with groupID "jsr94.wso2"
which does not match to current WSO2 orbit groupID naming convention. So
with next release of BRS we decided to move it from SVN to GIT with current
orbit naming convention

New groupId : org.wso2.orbit.jsr94
artifactId : jsr94


*janino*

janino used by BRS.
Same as jsr94 it also located in SVN orrbit [2] with groupID "janino.wso2"
which also not match with current WSO2 orbit groupID naming convention. So
with next release of BRS we decided to move it from SVN to GIT with current
orbit naming convention

New groupId : org.wso2.orbit.org.codehaus.janino
artifactId : janino

*jxl*

jxl used by BRS.
same as above it also located in SVN orbit [3] with groupID "jxl.wso2"
which also not match with current WSO2 orbit groupID naming convention. So
with next release of BRS we decided to move it from SVN to GIT with current
orbit naming convention.

And also with this there is a version upgrade of jxl from 2.6.8 to 2.6.12

New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
artifactId : jxl

*joda-time*
===
This orbit [4] also with groupID "joda-time.wso2" which also not match with
current WSO2 orbit groupID naming convention. For next release of BRS, need
version upgrade 1.6.0 to 2.8.2 with proper orbit groupID naming convention

New groupId : org.wso2.orbit.joda-time
artifactId : joda-time

*dools*

Version upgrade from 6.0.1 to 6.3.0.
GroupID also revamped to match current convention

New groupId : org.wso2.orbit.org.drools
artifactId : drools



[1] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
[2] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
[3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
[4] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time

Thanks,
Milinda

-- 
Milinda Perera
Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Issue in Android Enrollment

[Milan Perera]

Hi Dileesha,

The reason to fail Android enrollment at that stage because of the https
redirection that is enabled in the *mdm-android-agent *jax-rs.
Ex: *web.xml*



MDM-Android
/*


CONFIDENTIAL



So in order to call the APIs of this service, Android agent has to be
configured for SSL by adding a BKS file (*emm_truststore.bks*) to the
*res/raw/* folder of the *IDPProxy*
module of the agent.

Regards,

On Mon, Oct 12, 2015 at 7:40 PM, Sachith Punchihewa 
wrote:

> Hi Dileesha,
>
> The issue might be in the server.This happens when the server not
> returning the full certificate chain.Try changing that.
> For more information refer [1] and [2].
>
> [1]. http://superuser.com/questions/347588/how-do-ssl-chains-work
> [2].
> http://stackoverflow.com/questions/13862908/ssl-certificate-is-not-trusted-on-mobile-only
>
> Thanks & Regards.
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Mon, Oct 12, 2015 at 5:56 PM, Dileesha Rajapakse 
> wrote:
>
>> Hi,
>>
>> The Android Enrollment fails and produces the error below.
>>
>> 10-12 17:42:06.494   7068-10049/org.wso2.emm.agent E/ServerUtilities﹕
>> Error occurred while sending 'Post' request due to failure of server
>> connection
>> 10-12 17:42:06.504   7068-10049/org.wso2.emm.agent
>> E/DynamicClientManager﹕ Failed to contact server
>> org.wso2.emm.agent.proxy.IDPTokenManagerException: Error occurred
>> while sending 'Post' request due to failure of server connection
>> at
>> org.wso2.emm.agent.proxy.utils.ServerUtilities.sendPostRequest(ServerUtilities.java:252)
>> at
>> org.wso2.emm.agent.proxy.utils.ServerUtilities.postData(ServerUtilities.java:142)
>> at
>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:137)
>> at
>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:125)
>> at android.os.AsyncTask$2.call(AsyncTask.java:288)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:237)
>> at
>> android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
>> at java.lang.Thread.run(Thread.java:818)
>>  *Caused by: javax.net.ssl.SSLPeerUnverifiedException: No peer
>> certificate*
>> at
>> com.android.org.conscrypt.SSLNullSession.getPeerCertificates(SSLNullSession.java:104)
>> at
>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:93)
>> at
>> org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:388)
>> at
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:214)
>> at
>> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:167)
>> at
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.executeOriginal(DefaultRequestDirector.java:1292)
>> at
>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:700)
>> at
>> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:691)
>> at
>> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:514)
>> at
>> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:492)
>> at
>> org.wso2.emm.agent.proxy.utils.ServerUtilities.sendPostRequest(ServerUtilities.java:235)
>> at
>> org.wso2.emm.agent.proxy.utils.ServerUtilities.postData(ServerUtilities.java:142)
>> at
>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:137)
>> at
>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:125)
>> at 

[Dev] MSS Integration Test Errors

[Imesh Gunaratne]

Hi,

I'm seeing following errors in MSS product build:

00:23:29.916 [defaultEventExecutorGroup-5-4] ERROR
o.w.c.m.i.router.RequestRouter - Exception caught in channel processing.
org.wso2.carbon.mss.internal.router.HandlerException: Error in executing
request: GET /test/v1/NotRoutable/sree


00:23:28.247 [netty-worker-thread] DEBUG io.netty.handler.ssl.SslHandler -
[id: 0xb5ac79bd, /127.0.0.1:63758 => /127.0.0.1:63746] Swallowing a
harmless 'connection reset by peer / broken pipe' error that occurred while
writing close_notify in response to the peer's close_notify
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.8.0_60]
00:23:18.139 [defaultEventExecutorGroup-4-4] ERROR
o.w.c.m.i.router.RequestRouter - Exception caught in channel processing.
org.wso2.carbon.mss.internal.router.HandlerException: Error in executing
request: GET /test/v1/NotRoutable/sree
at
org.wso2.carbon.mss.internal.router.HttpResourceModel.handle(HttpResourceModel.java:150)
~[classes/:na]
...
Caused by: java.lang.IllegalArgumentException: Could not resolve value for
parameter userid
at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:119)
~[guava-13.0.1.jar:na]
at
org.wso2.carbon.mss.internal.router.HttpResourceModel.getPathParamValue(HttpResourceModel.java:186)
~[classes/:na]

Thanks

-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 3

[Kavith Lokuhewage]

Hi Supun,

Please find the list of new features below.

   - Applying security policies to your solution using WSO2 Developer Studio
  - WSO2 Developer Studio provides the facility to create security
  policies by using predefined security scenarios
  - enforce them on Data Services, BPEL workflows, ESB artifacts.


   - Enhanced support for WSO2 Connectors
   - Connect to WSO2 Connector Store and import preferred connectors
  directly
  - Include these connectors into the same CAR file, which wraps other
  artifacts such as sequences, proxy services, APIs etc., and deploy as one
  unit


   - Inbound Endpoint support


   - PublishEvent Mediator and ForEach Mediator support


   - Exploded WebApp Deployment Support
   - Makes it easier to make changes in the files, without requiring a
  redeployment of the complete WAR file.


   - Enhanced support for maven release plugin with new WSO2 build-helper
   Plugin
  - now supports all major scm providers
  - now supports dry run and rollback modes


   - API Manager perspective for Developer Studio
   - to perform updates, edits to your APIM sequences.


   - Basic tooling support for new artifact types of WSO2 CEP


   - Utilizes in-memory graphical meta-data instead of file based meta-data
   to improve performance


Thanks,

On Mon, Oct 12, 2015 at 8:01 PM, Supun Malinga  wrote:

> Hi Kavith,
>
> Can you pls mention what are the new features in 3.8.0 ?.
>
> thanks,
>
> On Mon, Oct 12, 2015 at 3:05 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Devs,
>>
>> Please vote for the third release candidate of WSO2 Developer Studio
>> 3.8.0.
>>
>> This release fixes following issues.
>> https://wso2.org/jira/issues/?filter=12450
>>
>> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> Sources, binary distribution and pre-installed eclipse distributions:
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC3/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC3
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> DevStudio Team
>>
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

[Madhuranga Bandara]

Congratulations Sasikala.. :)



*Madhuranga Sampath Bandara*
Software Engineer

WSO2, Inc.;http://wso2.com/

lean.enterprise.middleware
Mobile: +94722241065

On Mon, Oct 12, 2015 at 5:51 PM, Chanaka Fernando  wrote:

> Many congratulations Sasikala !!! Keep up the good work !!!
>
> On Mon, Oct 12, 2015 at 5:10 PM, Viraj Senevirathne 
> wrote:
>
>> Congrats Sasikala
>>
>> On Mon, Oct 12, 2015 at 3:20 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Congratz Sasikala !
>>>
>>> On Mon, Oct 12, 2015 at 3:15 PM, Rajith Roshan  wrote:
>>>
 Congratz !!!

 On Mon, Oct 12, 2015 at 1:47 PM, Isuru Wijesinghe 
 wrote:

> Congratulations :)
>
> On Mon, Oct 12, 2015 at 12:10 PM, Malintha Amarasinghe <
> malint...@wso2.com> wrote:
>
>> Congratulations Sasikala!! :)
>>
>> On Mon, Oct 12, 2015 at 11:28 AM, Kirishanthy Tharmalingam <
>> kirishan...@wso2.com> wrote:
>>
>>> Congrats Sasikala !
>>>
>>> On Mon, Oct 12, 2015 at 11:13 AM, Sasikala Kottegoda <
>>> sasik...@wso2.com> wrote:
>>>
 Thanks all... :)

 And special thanks to the MB team for the help that I've received
 so far... :)

 On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe <
 ram...@wso2.com> wrote:

> Hi Sasikala,
> Congratulations!
> It is with great pleasure that we welcome you as a WSO2 committer.
> Keep up the good work!
> regards,
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
>
>


 --
 Sasikala Kottegoda
 *Software Engineer*
 WSO2 Inc., http://wso2.com/
 lean. enterprise. middleware
 Mobile: +94 774835928/712792401

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


>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Kirishanthy
>>> Associate Software Engineer
>>> Mobile : +94 778333939
>>> kirishan...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> Mobile: 0710933706
> isur...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Rajith Roshan
 Software Engineer, WSO2 Inc.
 Mobile: +94-72-642-8350 <%2B94-71-554-8430>

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


>>>
>>>
>>> --
>>>
>>>
>>> *Thank you and Regards**Hariprasath Thanarajah*
>>> Associate Software Engineer | WSO2
>>> E: haripras...@wso2.com
>>> M: +94752806528
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Viraj Senevirathne
>> Software Engineer; WSO2, Inc.
>>
>> Mobile : +94 71 958 0269
>> Email : vir...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM] Issue in Android Enrollment

[Prabath Abeysekera]

I believe, HTTPS redirection needs be disabled by default to be able to
make sure "unzip and run" use-cases work smoothly. For instance, say some
user who intends to evaluate the product downloads it and tries to get a
simple device management flow running end-to-end. Enforcing an additional
step to set up certs at the server-end matching an applicable CN, and then
getting those installed into the devices would not quite make things easy,
particularly to such evaluation users, which makes it a valid case to have
HTTPs disabled by default IMO.

On the other hand, should someone put things in production, then they'd
have to enable HTTPS as part of the recommended deployment practices. We,
however, need to carefully look at this particular aspect as well, as it
might make things tedious for someone to go and manually enable this for
all plugin-based JAX-RS services one by one. Have we tried any mechanism to
probably do this in one-go at tomcat level (since it's hard to foresee
anyone wanting to access part of the services over HTTPS while the rest
exposed over HTTP)?

Cheers,
Prabath

On Monday, October 12, 2015, Milan Perera  wrote:

> Hi Dileesha,
>
> The reason to fail Android enrollment at that stage because of the https
> redirection that is enabled in the *mdm-android-agent *jax-rs.
> Ex: *web.xml*
>
> 
> 
> MDM-Android
> /*
> 
> 
> CONFIDENTIAL
> 
> 
>
> So in order to call the APIs of this service, Android agent has to be
> configured for SSL by adding a BKS file (*emm_truststore.bks*) to the
> *res/raw/* folder of the *IDPProxy*
> module of the agent.
>
> Regards,
>
> On Mon, Oct 12, 2015 at 7:40 PM, Sachith Punchihewa 
> wrote:
>
>> Hi Dileesha,
>>
>> The issue might be in the server.This happens when the server not
>> returning the full certificate chain.Try changing that.
>> For more information refer [1] and [2].
>>
>> [1]. http://superuser.com/questions/347588/how-do-ssl-chains-work
>> [2].
>> http://stackoverflow.com/questions/13862908/ssl-certificate-is-not-trusted-on-mobile-only
>>
>> Thanks & Regards.
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> On Mon, Oct 12, 2015 at 5:56 PM, Dileesha Rajapakse 
>> wrote:
>>
>>> Hi,
>>>
>>> The Android Enrollment fails and produces the error below.
>>>
>>> 10-12 17:42:06.494   7068-10049/org.wso2.emm.agent E/ServerUtilities﹕
>>> Error occurred while sending 'Post' request due to failure of server
>>> connection
>>> 10-12 17:42:06.504   7068-10049/org.wso2.emm.agent
>>> E/DynamicClientManager﹕ Failed to contact server
>>> org.wso2.emm.agent.proxy.IDPTokenManagerException: Error occurred
>>> while sending 'Post' request due to failure of server connection
>>> at
>>> org.wso2.emm.agent.proxy.utils.ServerUtilities.sendPostRequest(ServerUtilities.java:252)
>>> at
>>> org.wso2.emm.agent.proxy.utils.ServerUtilities.postData(ServerUtilities.java:142)
>>> at
>>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:137)
>>> at
>>> org.wso2.emm.agent.services.DynamicClientManager$SendRequest.doInBackground(DynamicClientManager.java:125)
>>> at android.os.AsyncTask$2.call(AsyncTask.java:288)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:237)
>>> at
>>> android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
>>> at java.lang.Thread.run(Thread.java:818)
>>>  *Caused by: javax.net.ssl.SSLPeerUnverifiedException: No peer
>>> certificate*
>>> at
>>> com.android.org.conscrypt.SSLNullSession.getPeerCertificates(SSLNullSession.java:104)
>>> at
>>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:93)
>>> at
>>> org.apache.http.conn.ssl.SSLSocketFactory.createSocket(SSLSocketFactory.java:388)
>>> at
>>> 

Re: [Dev] Error on FHIR connector integration Test case

[Elilmatha Sivanesan]

Hi Hariprasath,

As per you error log you need to include the certificate.

Thanks.

On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi All,
>
> I am working on FHIR connector. I got the following[1] error while I am
> running the integration test case of FHIR. Any suggestion on this error?
>
>
>
> [1]
> [2015-10-13 10:49:58,488] ERROR
> {org.wso2.carbon.automation.core.PlatformTestManager} -  On Test failure..
> [2015-10-13 10:49:58,488] ERROR
> {org.wso2.carbon.automation.core.PlatformTestManager} -
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> [2015-10-13 10:49:58,489]  INFO
> {org.wso2.carbon.automation.core.PlatformTestManager} -
> --Tests Failed
> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
> [2015-10-13 10:49:58,503]  INFO
> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
> [2015-10-13 10:49:58,503]  WARN - ProxyServiceAdmin No proxy service exists
> by the name : fhir
> [2015-10-13 10:49:58,525]  INFO
> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
> -  Proxy Deleted
> FAILED: readResource
> fhir {readResource} integration test.
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
> at
> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
> at
> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
> at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
> at
> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
> at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
> at
> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
> 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:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at 

Re: [Dev] Error on FHIR connector integration Test case

[Hariprasath Thanarajah]

Hi All ,

I got the response at the wire. But after that only  i am getting the above
error[1].

On Tue, Oct 13, 2015 at 11:08 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Elilmatha,
>
> I already included the certificates at client-truststore.jks as well as
> wso2carbon.jks.
>
> On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan 
> wrote:
>
>> Hi Hariprasath,
>>
>> As per you error log you need to include the certificate.
>>
>> Thanks.
>>
>> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I am working on FHIR connector. I got the following[1] error while I am
>>> running the integration test case of FHIR. Any suggestion on this error?
>>>
>>>
>>>
>>> [1]
>>> [2015-10-13 10:49:58,488] ERROR
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -  On Test failure..
>>> [2015-10-13 10:49:58,488] ERROR
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>> javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target
>>> [2015-10-13 10:49:58,489]  INFO
>>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>>> --Tests Failed
>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>>> [2015-10-13 10:49:58,503]  INFO
>>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>>> [2015-10-13 10:49:58,503]  WARN - ProxyServiceAdmin No proxy service exists
>>> by the name : fhir
>>> [2015-10-13 10:49:58,525]  INFO
>>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>>> -  Proxy Deleted
>>> FAILED: readResource
>>> fhir {readResource} integration test.
>>> javax.net.ssl.SSLHandshakeException:
>>> sun.security.validator.ValidatorException: PKIX path building failed:
>>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>>> valid certification path to requested target
>>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
>>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
>>> at
>>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
>>> at
>>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
>>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
>>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
>>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
>>> at
>>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
>>> at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
>>> at
>>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
>>> at
>>> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
>>> at
>>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
>>> at
>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
>>> at
>>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
>>> at
>>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
>>> at
>>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
>>> at
>>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
>>> 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:606)
>>> at
>>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>>> at
>>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>>> at
>>> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)

[Dev] WSO2 Committers += Chamalee De Silva

[Nuwan Dias]

Hi,

It is with great pleasure we welcome Chamalee De Silva as a WSO2 Committer.
@Chamalee, congratulations and keep up the good work!

Thanks,
NuwanD.

-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Issue in Android Enrollment

[Prabath Abeysekera]

On Tue, Oct 13, 2015 at 11:18 AM, Milan Perera  wrote:

> Hi Prabath,
>
> I believe, HTTPS redirection needs be disabled by default to be able to
>> make sure "unzip and run" use-cases work smoothly.
>>
> ​
> +1 for that.
>
> And the other thing is we can do this in one-go at tomcat level without
> editing each and every web.xmls.
> To do that ​we can add the same configuration that I mentioned above to
> the web.xml of the tomcat which resides in the *repository/conf/tomcat*
>

Great! Thanks for the confirmation.

@Shavindri, This needs to be added to the EMM configuration/deployment
guide as well. Please note.

Cheers,
Prabath


> ​Regards,​
> --
> *Milan Harindu Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] SMPP Server Installation.

[Elilmatha Sivanesan]

Hi all,

I'm working on smsotp authenticator, I have a requirement to send sms. I'm
using OZEKI NG SMS Gateway and installing SMPP server for this purpose I'm
following doc [1]. For that I need the GSM service provider information.
Can anyone suggest me how can I get the service Provider informations.
(Host ,port, username, password,phone no, etc).

Or Is there any other way I can send sms ( without vendor specific like
twillio , nexmo ...).

[1] http://www.ozekisms.com/index.php?owpn=177

Thanks.

*S.Elilmatha*
Associate  Software Engineer,

WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [EMM] Issue in Android Enrollment

[Milan Perera]

Hi Prabath,

I believe, HTTPS redirection needs be disabled by default to be able to
> make sure "unzip and run" use-cases work smoothly.
>
​
+1 for that.

And the other thing is we can do this in one-go at tomcat level without
editing each and every web.xmls.
To do that ​we can add the same configuration that I mentioned above to the
web.xml of the tomcat which resides in the *repository/conf/tomcat*

​Regards,​
-- 
*Milan Harindu Perera *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com

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

[Dev] Execute Oracle rac database script at server startup

[Maduranga Siriwardena]

Hi all,

While going through the code that is used to create the database with
-Dsetup command, I noticed that we can't do it for oracle rac script. [1]
is used to find the database type and the returned type is used to find the
script location in [2]. So the getDatabaseType method does not return a
database type as oracle_rac and hence the oracle_rac script is not picked
up.

Is there any way we can execute oracle rac script and create database at
the server startup?


[1]
https://github.com/wso2/carbon-kernel/blob/master/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/dbcreator/DatabaseCreator.java#L233
[2]
https://github.com/wso2/carbon-kernel/blob/master/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/dbcreator/DatabaseCreator.java#L344

Thanks,
-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error on FHIR connector integration Test case

[Hariprasath Thanarajah]

Hi All,

I am working on FHIR connector. I got the following[1] error while I am
running the integration test case of FHIR. Any suggestion on this error?



[1]
[2015-10-13 10:49:58,488] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} -  On Test failure..
[2015-10-13 10:49:58,488] ERROR
{org.wso2.carbon.automation.core.PlatformTestManager} -
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
[2015-10-13 10:49:58,489]  INFO
{org.wso2.carbon.automation.core.PlatformTestManager} -
--Tests Failed
org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
[2015-10-13 10:49:58,503]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2015-10-13 10:49:58,503]  WARN - ProxyServiceAdmin No proxy service exists
by the name : fhir
[2015-10-13 10:49:58,525]  INFO
{org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
-  Proxy Deleted
FAILED: readResource
fhir {readResource} integration test.
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
at
sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
at
org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
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:606)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at

Re: [Dev] [Orbit] [BRS] Upgrade jxl, dools, Joda-time and Revamp group IDs of jsr94, janino for BRS

[Aruna Karunarathna]

Hi Milinda,

I have added some comments to your PR. Can you please check them?.

Regards,
Aruna

On Tue, Oct 13, 2015 at 12:31 AM, Milinda Perera  wrote:

> Hi,
>
> Please review and merge PR : https://github.com/wso2/orbit/pull/139
>
> Please refer following information about the changes and upgrades:
>
> *jsr94*
> 
> jsr94 used by BRS.
> Currently jsr94 in located in SVN orrbit [1] with groupID "jsr94.wso2"
> which does not match to current WSO2 orbit groupID naming convention. So
> with next release of BRS we decided to move it from SVN to GIT with current
> orbit naming convention
>
> New groupId : org.wso2.orbit.jsr94
> artifactId : jsr94
>
>
> *janino*
> 
> janino used by BRS.
> Same as jsr94 it also located in SVN orrbit [2] with groupID "janino.wso2"
> which also not match with current WSO2 orbit groupID naming convention. So
> with next release of BRS we decided to move it from SVN to GIT with current
> orbit naming convention
>
> New groupId : org.wso2.orbit.org.codehaus.janino
> artifactId : janino
>
> *jxl*
> 
> jxl used by BRS.
> same as above it also located in SVN orbit [3] with groupID "jxl.wso2"
> which also not match with current WSO2 orbit groupID naming convention. So
> with next release of BRS we decided to move it from SVN to GIT with current
> orbit naming convention.
>
> And also with this there is a version upgrade of jxl from 2.6.8 to 2.6.12
>
> New groupId : org.wso2.orbit.net.sourceforge.jexcelapi
> artifactId : jxl
>
> *joda-time*
> ===
> This orbit [4] also with groupID "joda-time.wso2" which also not match
> with current WSO2 orbit groupID naming convention. For next release of BRS,
> need version upgrade 1.6.0 to 2.8.2 with proper orbit groupID naming
> convention
>
> New groupId : org.wso2.orbit.joda-time
> artifactId : joda-time
>
> *dools*
> 
> Version upgrade from 6.0.1 to 6.3.0.
> GroupID also revamped to match current convention
>
> New groupId : org.wso2.orbit.org.drools
> artifactId : drools
>
>
>
> [1] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jsr94/
> [2] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/janino
> [3] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/jxl/
> [4] https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/orbit/joda-time
>
> Thanks,
> Milinda
>
> --
> Milinda Perera
> Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error on FHIR connector integration Test case

[Hariprasath Thanarajah]

Hi Elilmatha,

I already included the certificates at client-truststore.jks as well as
wso2carbon.jks.

On Tue, Oct 13, 2015 at 11:06 AM, Elilmatha Sivanesan 
wrote:

> Hi Hariprasath,
>
> As per you error log you need to include the certificate.
>
> Thanks.
>
> On Tue, Oct 13, 2015 at 10:56 AM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am working on FHIR connector. I got the following[1] error while I am
>> running the integration test case of FHIR. Any suggestion on this error?
>>
>>
>>
>> [1]
>> [2015-10-13 10:49:58,488] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} -  On Test failure..
>> [2015-10-13 10:49:58,488] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>> valid certification path to requested target
>> [2015-10-13 10:49:58,489]  INFO
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> --Tests Failed
>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource
>> [2015-10-13 10:49:58,503]  INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2015-10-13 10:49:58,503]  WARN - ProxyServiceAdmin No proxy service exists
>> by the name : fhir
>> [2015-10-13 10:49:58,525]  INFO
>> {org.wso2.carbon.automation.api.clients.proxy.admin.ProxyServiceAdminClient}
>> -  Proxy Deleted
>> FAILED: readResource
>> fhir {readResource} integration test.
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
>> valid certification path to requested target
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1904)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273)
>> at
>> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1446)
>> at
>> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:209)
>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:901)
>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:837)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1023)
>> at
>> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
>> at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
>> at
>> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
>> at
>> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
>> at
>> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
>> at
>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
>> at
>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
>> at
>> sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.readResponse(ConnectorIntegrationTestBase.java:898)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:371)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendJsonRestRequest(ConnectorIntegrationTestBase.java:253)
>> at
>> org.wso2.carbon.connector.integration.test.fhir.fhirConnectorIntegrationTest.readResource(fhirConnectorIntegrationTest.java:69)
>> 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:606)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>> at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
>> at org.testng.TestRunner.privateRun(TestRunner.java:757)
>> at org.testng.TestRunner.run(TestRunner.java:608)
>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>> at