[Dev] API-M: How is Consumer Key & Secret used

[Afkham Azeez]

Can somebody take the Twitter search sample & explain how the Consumer Key
& Secret are used.

[image: Inline image 1]


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
<>___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API-M: Make sure all samples are covered by integration tests

[Afkham Azeez]

In late 2011 & early 2012, we put in a lot of effort to develop an
integration test framework which will allow you to, among other things,
fully automate sample deployment & testing. Now it is a pre-requisite for
all WSO2 products. Please make sure this is done for API-M.

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deploying a CXF web app within API Manager

[Supun Malinga]

Hi Johan,


On Fri, Mar 29, 2013 at 6:33 AM, Johann Nallathamby  wrote:

> Hi,
>
> On Tue, Mar 26, 2013 at 8:24 PM, Nuwan Dias  wrote:
>
>>
>> On Tue, Mar 26, 2013 at 7:09 PM, Sagara Gunathunga wrote:
>>
>>> If it's a only one application isn't it easy to package all required
>>> jars inside WAR/lib directory without creating CXF runtime ( without
>>> placing Jars in lib/runtimes/cxf directory) ?
>>>
>>
>> Yes, it would be easy. However, this webapp comes from a separate
>> component (identity.oauth.endpoint.token) and hence might be reused within
>> other products (IS). If we're having the jars within the WAR/lib, can it
>> cause any problems if the webapp is deployed on some other server (ex:
>> older version of IS)?
>>
>
> IS goes with 2 jax webapps. oauth2endpoints.war for OAuth and wso2.war
> which is for SCIM. Therefore I don't think bundling the libs inside the war
> is a good idea since it is duplicating the jars.
>

So you can add the default cxf runtime profile to IS. I guess you can add
only the required jars from IS into this. Since IS doesn't support hosting
3rd party apps this should be OK. So you can keep the product size minimum.
Please see AS 5.1.0 distribution module how this was done.

thanks,

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


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usability improvement for API-M subscription

[Sumedha Rubasinghe]

On Fri, Mar 29, 2013 at 7:36 AM, Samisa Abeysinghe  wrote:

>
>
> On Fri, Mar 29, 2013 at 7:31 AM, Sumedha Rubasinghe wrote:
>
>> Chanaka,
>> Can we have a mock done? We had a discussion within team on one possible
>> way of doing this.
>>
>
> How?
>

Shall we see a mock up version first? Find it bit difficult to explain
verbally.
In a nut shell it resolves around several aspects:
- Treating API browsing & Subscription as two separate flows performed by
users of API Store  (image this as a shopping portal & a shopping cart.
Difference is there is only one shopping cart vs multiple applications)
- Fixing creating applications & adding APIs disconnection (also highlight
in another thread by Azeez at el)
- More easier way of subscription from the first page of the store itself

These need feedback from a broader team & once agreed these need to go into
generic store impl as well. But lets discuss around mock UIs first.


>
>
>  Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>


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

Re: [Dev] Usability improvement for API-M subscription

[Samisa Abeysinghe]

On Fri, Mar 29, 2013 at 7:31 AM, Sumedha Rubasinghe wrote:

> Chanaka,
> Can we have a mock done? We had a discussion within team on one possible
> way of doing this.
>

How?

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usability improvement for API-M subscription

[Sumedha Rubasinghe]

Chanaka,
Can we have a mock done? We had a discussion within team on one possible
way of doing this. Just want to see how it will look.


On Thu, Mar 28, 2013 at 5:54 PM, Chanaka Jayasena  wrote:

> It's better to have an Application centered view along with the API
> centered view. I think there are lot of usability improvements that we can
> do along with that. We can do some mock-up base discussions and do these
> improvements. I am not sure when and which version we should target.
>
> thanks,
> Chanaka
>
>
> On Thu, Mar 28, 2013 at 3:58 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Thu, Mar 28, 2013 at 3:23 PM, Lalaji Sureshika wrote:
>>
>>> Hi,
>>>
>>> On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez  wrote:
>>>


 On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez  wrote:

>
>
> On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika wrote:
>
>> Hi,
>>
>> On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias  wrote:
>>>
 On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez wrote:

>
>
> On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe <
> sume...@wso2.com> wrote:
>
>> On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez wrote:
>>
>>> Right now you have to navigate to an API, and then associate it
>>> with an Application. Edit Application only allows you to change the 
>>> name &
>>> tier. IMO, it is more natural to create an application, and then 
>>> add APIs
>>> to that application, rather than navigating to the API & then 
>>> adding it to
>>> the app.
>>
>>
>> Azeez,
>> Your suggesting a UI enhancement. right?
>> This means with in application view, we should provide some means
>> of searching for APIs, then select version.
>>
>
>
> Yes, UI enhancement.
>

 I'm guessing it would be something like this.

 List My Applications -> Choose an Application and click "Add APIs"
 -> Search for APIs and select the ones to be added to the App -> 
 Commit.

>>>
>>> Yes, that is correct. My concern is, once you create an Application,
>>> you are lost because the flow is broken. You have to start a new flow by
>>> going to APIs, and then associate an app with the APIs.
>>>
>>
>>I guess,if there's a link available in Applications page pointing
>> to APIs page with some indication similar to to 'select APIs from browse
>> APIs page' will be sufficient..As APIs page already providing
>>  browse/search/subscribe to APIs..
>>
>
> No it is not sufficient. Once you add an application, it appears on
> the list at the bottom part of the page. Add application should be a
> wizard.
>
> Step 1: Define application name
> Step 2: Select tier - this page needs to contain briefly what each
> tier provides, features/limitations etc.
> Step 3: Add APIs to Application
> Step 4: Generate keys
>
> The user experience should be smooth & unbroken. This is not just a
> problem with API-M UIs, but may of our other UIs as well. We need to make
> an effort to improve these aspects, and such small improvements will go a
> long way.
>

>>>  Should this be added as a work item for a future release/current
>>> release?
>>>
>>> With the above your suggested way,for Step 3 and Step4,are you
>>> suggesting to redirect to existing browse API and subscriptions pages or
>>> introducing new popup UIs.
>>>
>>
>> New UIs.
>>
>>
>>> Please pardon,but still I believe,once an application created,if there's
>>> a link available in the created application row to redirect into APIs
>>> page,it'll support your flow from the step 3 and continue.But with that
>>> way,the current limitation is,you cannot subscribe to multiple APIs at one
>>> time.
>>>
>>
>> that is not a natural flow because once you are in the API-first view,
>> you have to select the application again from the dropdown, and you have to
>> repeat the same for each & every API you want to add to the application
>>
>>
>>>
>>> Anyhow,if we are going to implement above,I believe it has to be done in
>>> a future release[ Not the next release 1.4.0],as we have to come up with a
>>> proper UI design.
>>>
>>> Thanks;
>>>


>
>
>>
>> Thanks;
>>
>> Thanks;
>>
>>>
>>>

 Thanks,
 NuwanD.

>
>
>>
>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **h

Re: [Dev] Deploying a CXF web app within API Manager

[Johann Nallathamby]

Hi,

On Tue, Mar 26, 2013 at 8:24 PM, Nuwan Dias  wrote:

>
> On Tue, Mar 26, 2013 at 7:09 PM, Sagara Gunathunga wrote:
>
>> If it's a only one application isn't it easy to package all required jars
>> inside WAR/lib directory without creating CXF runtime ( without placing
>> Jars in lib/runtimes/cxf directory) ?
>>
>
> Yes, it would be easy. However, this webapp comes from a separate
> component (identity.oauth.endpoint.token) and hence might be reused within
> other products (IS). If we're having the jars within the WAR/lib, can it
> cause any problems if the webapp is deployed on some other server (ex:
> older version of IS)?
>

IS goes with 2 jax webapps. oauth2endpoints.war for OAuth and wso2.war
which is for SCIM. Therefore I don't think bundling the libs inside the war
is a good idea since it is duplicating the jars.

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

[Dev] Verification Failure With BAM 2.2.0 Public Certificate

[Isuru Haththotuwa]

Hi,

I'm getting SSL verification error with the BAM 2.2.0 public certificate
when I'm trying to publish data to the BAM using a C++ app. I exported the
BAM public cert from the browser, and when I verify the certificate with
openssl verify command, I get the following error:

wso2carbon.crt: C = US, ST = CA, L = Mountain View, O = WSO2, CN = localhost
error 20 at 0 depth lookup:unable to get local issuer certificate

Hence the SSL communication is unsuccessful between the BAM and the client.
Any idea on what the issue here is?

-- 
Thanks and Regards,

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

Re: [Dev] ESB return no response from the GET service failing with NPE

[Vladimir Klevko]

Hello,

I've configured a proxy service to run some XSBRL validation stuff that
accepts a get request and return XML validation results. Here's proxy
service configuration:

http://ws.apache.org/ns/synapse";
name="XBRLValidationRESTService" transports="https,http"
statistics="disable" trace="disable" startOnLoad="true">
 
   
  
  
  
  
 
http://localhost:1/rest/xbrl";
 format="pox"/>
 
  
  
   
  
  
   


 

In the log file I can see that the underlying service responds with expected
response, however the client receives nothing back and ESB fails with NPE
for some reason.

Request used from localhost:
curl -k  https://localhost:9443/services/XBRLValidationRESTService

Full log: http://pastebin.com/A5jB9wMF

What is the potential reason for that and how that could be fixed.

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

Re: [Dev] API Manager Load Testing (Store Feature)

[Lalaji Sureshika]

Hi Ruwan,

On Thu, Mar 28, 2013 at 8:33 PM, Sanjeewa Malalgoda wrote:

>
>
> On Thu, Mar 28, 2013 at 8:49 PM, Ruwan Yatawara  wrote:
>
>>
>> Hi All,
>>
>> We executed a load test on the latest multi-tenancy enabled API Manager
>> pack with with the Use of Jmeter Scripts.
>>
>> Following features of the API Store, were tested.
>>
>>1. Get All APIs
>>2. Get All Tags
>>3. Get All recently added APIs
>>
>> Please find below, results of the tests.
>>
>>   *Test : Get All APIs*
>>  *
>> *
>>  *
>> *
>>  *10 Tenants 100 APIs each (1000 APIs)*
>>  User Count Average Time (ms)  Single User 3169  10 Users 43230
>>
>>  *100 Tenants 10 Apis each (1000 APIs)*
>>  User Count Average Time (ms)  Single User 6119  10 Users 63402  100
>> Users 185196
>>
>>
>>
>>  *100 Tenants 20 APIs each (2000 APIs)*
>>  User Count Average Time (ms)  Single User 14974  10 Users 172514  100
>> Users 182466  300 Users * 328453
>>
>>  * With 10.37% of the requests getting timed out
>>
>>
>>  *100 Tenants 100 APIs each (1 APIs)*
>>  User Count Average Time (ms)  Single User Fails after 210200
>>
>>
>>
>>
>>
>>  *Test : Get Recently Published APIs*
>>  *
>> *
>>
>>
>>  *100 Tenants 20 APIs each (2000 APIs)*
>>  User Count Average Time (ms)  Single User 487  10 Users 3051  100 Users
>> 37852  1000 Users * 328291
>>
>>  * With 6% of the requests getting timed out
>>
>>
>>   *Test : Get Tags*
>>  *
>> *
>>
>>
>>  *100 Tenants 20 APIs each (2000 APIs)*
>>  User Count Average Time (ms)  Single User 682  10 Users 5617  100 Users
>> 85346  1000 Users * 359779
>>
>>  * With 16.7% of the requests getting timed out
>>
>
>>
>> Please note that, these tests were carried out on my local machine.
>>
> Good work ruwan, These results should be much better than this if we ran
> in developer environment. Lets try same thing on developer environment by
> using today pack. Also API invocation/subscription and login should take
> into account next cycles of tests.
>

   Thanks  Ruwan for carrying the above and sharing stats. Main focus on
above load tests is to check,how efficient the API retrieving methods of
APIStore after did multi-tenant related improvements [eg: iterating through
each tenant registry space to retrieve APIs to show in global Store mode..]
.It would be great,if you can share the carbon log file also to get idea on
failing points.. Meantime I will profile and check the code again,with
using your improved jmeter script..

Thanks;


>
> Thanks.
> Sanjeewa.
>
>>
>>
>> Thanks and Regards,
>> Ruwan Yatawara
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +14084122175 | +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lalaji Sureshika
Software Engineer; Development Technologies Team;WSO2, Inc.;
http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stratos 2 ELB : NoSuchMethodError: HttpProtocolParams.getMalformedInputAction

[Isuru Wimalasundera]

Hi Lalaji

Yes seems it was the case, we too had a duplicate older version of httpcore
inside plugins, in the process fixing it. Thanks for the note .


On Thu, Mar 28, 2013 at 8:49 PM, Lalaji Sureshika  wrote:

> Hi,
>
> Did you check the ELB built pack contains duplicate versions
> of httpcore/httpcore-nio/http-client jars in plugins folder. We got similar
> issue in APIManager pack built on 4.1.2.Duplicate version-ed jars issue got
> resolved when we update org.wso2.carbon.databridge.datapublisher.feature to
> 4.1.1 in our product.
>
> Thanks;
>
> Thanks;
>
> On Thu, Mar 28, 2013 at 7:17 PM, Isuru Wimalasundera wrote:
>
>> Hi All
>>
>> In the latest ELB build from 4.1.1 branch, which is updated to httpcore
>> 4.2.3wso2v1 recently, gives the given below error. Any idea on this?
>>
>> [2013-03-28 20:09:24,150] ERROR - NIOServerCnxn Thread
>> Thread[HTTPS-Listener I/O dispatcher-1,5,HTTPS-Listener I/O dispatcher
>> thread group] died
>> java.lang.NoSuchMethodError:
>> org.apache.http.params.HttpProtocolParams.getMalformedInputAction(Lorg/apache/http/params/HttpParams;)Ljava/nio/charset/CodingErrorAction;
>> at
>> org.apache.http.impl.nio.reactor.SessionInputBufferImpl.(SessionInputBufferImpl.java:78)
>> at
>> org.apache.http.impl.nio.NHttpConnectionBase.(NHttpConnectionBase.java:146)
>> at
>> org.apache.http.impl.nio.DefaultNHttpServerConnection.(DefaultNHttpServerConnection.java:93)
>> at
>> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.(LoggingNHttpServerConnection.java:62)
>> at
>> org.apache.synapse.transport.http.conn.LoggingUtils.createServerConnection(LoggingUtils.java:73)
>> at
>> org.apache.synapse.transport.http.conn.ServerConnFactory.createConnection(ServerConnFactory.java:90)
>> at
>> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:58)
>> at
>> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:39)
>> at
>> org.apache.http.impl.nio.reactor.AbstractIODispatch.connected(AbstractIODispatch.java:72)
>> at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.sessionCreated(BaseIOReactor.java:242)
>> at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:427)
>> at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:291)
>> at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
>> at
>> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
>> at java.lang.Thread.run(Thread.java:662)
>>
>> Thanks
>> Isuruw
>>
>> --
>> *Isuru Wimalasundera*
>> Software Engineer;  WSO2, Inc.; http://wso2.com,
>>  mobile: +94 77 920 5641
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lalaji Sureshika
> Software Engineer; Development Technologies Team;WSO2, Inc.;
> http://wso2.com/
> email: lal...@wso2.com; cell: +94 71 608 6811
> blog: http://lalajisureshika.blogspot.com
>
>
>


-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Stratos2] Apache server of PHP/MySQL cartridge is not accessible after sometime

[Lakmal Warusawithana]

Will revert key coping thing. Udara please looking to that
On Mar 28, 2013 9:41 PM, "Sajith Kariyawasam"  wrote:

> Hi Lakmal,
>
> Found that Apache server is shutdown after sometime, seems its because of
> the keys we are copying..
>
> In Apache error.log s I can see this..
>
> [Thu Mar 28 10:37:11 2013] [notice] caught SIGTERM, shutting down
> [Thu Mar 28 14:42:00 2013] [warn] RSA server certificate CommonName (CN)
> `ip-10-194-246-138.ec2.internal' does NOT match server name!?
> [Thu Mar 28 14:42:03 2013] [warn] RSA server certificate CommonName (CN)
> `ip-10-194-246-138.ec2.internal' does NOT match server name!?
> [Thu Mar 28 14:42:03 2013] [notice] Apache/2.2.22 (Ubuntu)
> PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
> configured -- resuming normal operations
> [Thu Mar 28 14:42:08 2013] [notice] caught SIGTERM, shutting down
> [Thu Mar 28 14:42:09 2013] [warn] RSA server certificate CommonName (CN)
> `ip-10-194-246-138.ec2.internal' does NOT match server name!?
> [Thu Mar 28 14:42:09 2013] [warn] RSA server certificate CommonName (CN)
> `ip-10-194-246-138.ec2.internal' does NOT match server name!?
> [Thu Mar 28 14:42:09 2013] [notice] Apache/2.2.22 (Ubuntu)
> PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
> configured -- resuming normal operations
> [Thu Mar 28 14:56:12 2013] [notice] caught SIGTERM, shutting down
> [Thu Mar 28 15:46:00 2013] [warn] RSA server certificate CommonName (CN)
> `ip-10-194-246-138.ec2.internal' does NOT match server name!?
> [Thu Mar 28 15:46:04 2013] [warn] RSA server certificate CommonName (CN)
> `localhost' does NOT match server name!?
> [Thu Mar 28 15:46:04 2013] [notice] Apache/2.2.22 (Ubuntu)
> PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
> configured -- resuming normal operations
> [Thu Mar 28 15:46:04 2013] [notice] caught SIGTERM, shutting down
>
>
> -- Forwarded message --
> From: Lakmal Warusawithana 
> Date: Thu, Mar 28, 2013 at 6:32 PM
> Subject: Re: Logs - When a mysql cartridge is registered with Cartridge
> Agent
> To: Sajith Kariyawasam 
>
>
> Yes pls
>  On Mar 28, 2013 6:16 PM, "Sajith Kariyawasam"  wrote:
>
>>
>>
>> [2013-03-28 12:42:22,096]  INFO
>> {org.wso2.carbon.cartridge.agent.service.CartridgeAgentService} -  Trying
>> to add new registrant
>> Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
>> remoteHost='54.225.189.62'}...
>> [2013-03-28 12:42:22,099]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantDatabase} -  Added
>> registrant Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
>> remoteHost='54.225.189.62'}
>> [2013-03-28 12:42:22,100]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Trying to connect to registrant
>> Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
>> remoteHost='54.225.189.62'}...
>> [2013-03-28 12:42:22,100]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Portmappings..
>> [Lorg.wso2.carbon.cartridge.agent.registrant.PortMapping;@2048a158
>> [2013-03-28 12:42:22,100]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Retrying3
>> [2013-03-28 12:42:22,100]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  checking port: 80and addr: /54.225.189.62retry..:3
>> [2013-03-28 12:42:32,104] ERROR
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Error occurred.. connect timed out
>> [2013-03-28 12:42:33,104]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Retrying2
>> [2013-03-28 12:42:33,104]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  checking port: 80and addr: /54.225.189.62retry..:2
>> [2013-03-28 12:42:43,115] ERROR
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Error occurred.. connect timed out
>> [2013-03-28 12:42:44,115]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Retrying1
>> [2013-03-28 12:42:44,116]  INFO
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  checking port: 80and addr: /54.225.189.62retry..:1
>> [2013-03-28 12:42:54,116] ERROR
>> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>>  Error occurred.. connect timed out
>> [2013-03-28 12:42:55,116] ERROR
>> {org.wso2.carbon.cartridge.agent.ClusteringClient} -  Cannot add registrant.
>>
>>
>> Agent retries 3 times only and at that time port 80 seems not up and
>> running
>>
>> so, i will make retry count configurable and will make retry count a
>> higher value
>>
>>
>> --
>> Regards,
>> *
>> *
>> *Sajith Kariyawasam*
>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>
>
>
>
> --
> Regards,
> *
> *
> *Sajith Kariyawasam*
> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>
___
Dev mailing list
Dev@wso2.org
ht

[Dev] [Stratos2] Apache server of PHP/MySQL cartridge is not accessible after sometime

[Sajith Kariyawasam]

Hi Lakmal,

Found that Apache server is shutdown after sometime, seems its because of
the keys we are copying..

In Apache error.log s I can see this..

[Thu Mar 28 10:37:11 2013] [notice] caught SIGTERM, shutting down
[Thu Mar 28 14:42:00 2013] [warn] RSA server certificate CommonName (CN)
`ip-10-194-246-138.ec2.internal' does NOT match server name!?
[Thu Mar 28 14:42:03 2013] [warn] RSA server certificate CommonName (CN)
`ip-10-194-246-138.ec2.internal' does NOT match server name!?
[Thu Mar 28 14:42:03 2013] [notice] Apache/2.2.22 (Ubuntu)
PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
configured -- resuming normal operations
[Thu Mar 28 14:42:08 2013] [notice] caught SIGTERM, shutting down
[Thu Mar 28 14:42:09 2013] [warn] RSA server certificate CommonName (CN)
`ip-10-194-246-138.ec2.internal' does NOT match server name!?
[Thu Mar 28 14:42:09 2013] [warn] RSA server certificate CommonName (CN)
`ip-10-194-246-138.ec2.internal' does NOT match server name!?
[Thu Mar 28 14:42:09 2013] [notice] Apache/2.2.22 (Ubuntu)
PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
configured -- resuming normal operations
[Thu Mar 28 14:56:12 2013] [notice] caught SIGTERM, shutting down
[Thu Mar 28 15:46:00 2013] [warn] RSA server certificate CommonName (CN)
`ip-10-194-246-138.ec2.internal' does NOT match server name!?
[Thu Mar 28 15:46:04 2013] [warn] RSA server certificate CommonName (CN)
`localhost' does NOT match server name!?
[Thu Mar 28 15:46:04 2013] [notice] Apache/2.2.22 (Ubuntu)
PHP/5.3.10-1ubuntu3.6 with Suhosin-Patch mod_ssl/2.2.22 OpenSSL/1.0.1
configured -- resuming normal operations
[Thu Mar 28 15:46:04 2013] [notice] caught SIGTERM, shutting down


-- Forwarded message --
From: Lakmal Warusawithana 
Date: Thu, Mar 28, 2013 at 6:32 PM
Subject: Re: Logs - When a mysql cartridge is registered with Cartridge
Agent
To: Sajith Kariyawasam 


Yes pls
On Mar 28, 2013 6:16 PM, "Sajith Kariyawasam"  wrote:

>
>
> [2013-03-28 12:42:22,096]  INFO
> {org.wso2.carbon.cartridge.agent.service.CartridgeAgentService} -  Trying
> to add new registrant
> Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
> remoteHost='54.225.189.62'}...
> [2013-03-28 12:42:22,099]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantDatabase} -  Added
> registrant Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
> remoteHost='54.225.189.62'}
> [2013-03-28 12:42:22,100]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Trying to connect to registrant
> Registrant{key='595360ac-759c-4d23-9e91-df4b1fec7178',
> remoteHost='54.225.189.62'}...
> [2013-03-28 12:42:22,100]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Portmappings..
> [Lorg.wso2.carbon.cartridge.agent.registrant.PortMapping;@2048a158
> [2013-03-28 12:42:22,100]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Retrying3
> [2013-03-28 12:42:22,100]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  checking port: 80and addr: /54.225.189.62retry..:3
> [2013-03-28 12:42:32,104] ERROR
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Error occurred.. connect timed out
> [2013-03-28 12:42:33,104]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Retrying2
> [2013-03-28 12:42:33,104]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  checking port: 80and addr: /54.225.189.62retry..:2
> [2013-03-28 12:42:43,115] ERROR
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Error occurred.. connect timed out
> [2013-03-28 12:42:44,115]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Retrying1
> [2013-03-28 12:42:44,116]  INFO
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  checking port: 80and addr: /54.225.189.62retry..:1
> [2013-03-28 12:42:54,116] ERROR
> {org.wso2.carbon.cartridge.agent.registrant.RegistrantHealthChecker} -
>  Error occurred.. connect timed out
> [2013-03-28 12:42:55,116] ERROR
> {org.wso2.carbon.cartridge.agent.ClusteringClient} -  Cannot add registrant.
>
>
> Agent retries 3 times only and at that time port 80 seems not up and
> running
>
> so, i will make retry count configurable and will make retry count a
> higher value
>
>
> --
> Regards,
> *
> *
> *Sajith Kariyawasam*
> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>



-- 
Regards,
*
*
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.; http://wso2.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager Load Testing (Store Feature)

[Sanjeewa Malalgoda]

On Thu, Mar 28, 2013 at 8:49 PM, Ruwan Yatawara  wrote:

>
> Hi All,
>
> We executed a load test on the latest multi-tenancy enabled API Manager
> pack with with the Use of Jmeter Scripts.
>
> Following features of the API Store, were tested.
>
>1. Get All APIs
>2. Get All Tags
>3. Get All recently added APIs
>
> Please find below, results of the tests.
>
>   *Test : Get All APIs*
>  *
> *
>  *
> *
>  *10 Tenants 100 APIs each (1000 APIs)*
>  User Count Average Time (ms)  Single User 3169  10 Users 43230
>
>  *100 Tenants 10 Apis each (1000 APIs)*
>  User Count Average Time (ms)  Single User 6119  10 Users 63402  100 Users
> 185196
>
>
>
>  *100 Tenants 20 APIs each (2000 APIs)*
>  User Count Average Time (ms)  Single User 14974  10 Users 172514  100
> Users 182466  300 Users * 328453
>
>  * With 10.37% of the requests getting timed out
>
>
>  *100 Tenants 100 APIs each (1 APIs)*
>  User Count Average Time (ms)  Single User Fails after 210200
>
>
>
>
>
>  *Test : Get Recently Published APIs*
>  *
> *
>
>
>  *100 Tenants 20 APIs each (2000 APIs)*
>  User Count Average Time (ms)  Single User 487  10 Users 3051  100 Users
> 37852  1000 Users * 328291
>
>  * With 6% of the requests getting timed out
>
>
>   *Test : Get Tags*
>  *
> *
>
>
>  *100 Tenants 20 APIs each (2000 APIs)*
>  User Count Average Time (ms)  Single User 682  10 Users 5617  100 Users
> 85346  1000 Users * 359779
>
>  * With 16.7% of the requests getting timed out
>
>
>
> Please note that, these tests were carried out on my local machine.
>
Good work ruwan, These results should be much better than this if we ran in
developer environment. Lets try same thing on developer environment by
using today pack. Also API invocation/subscription and login should take
into account next cycles of tests.

Thanks.
Sanjeewa.

>
>
> Thanks and Regards,
> Ruwan Yatawara
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122175 | +94713068779

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

[Dev] API Manager Load Testing (Store Feature)

[Ruwan Yatawara]

Hi All,

We executed a load test on the latest multi-tenancy enabled API Manager
pack with with the Use of Jmeter Scripts.

Following features of the API Store, were tested.

   1. Get All APIs
   2. Get All Tags
   3. Get All recently added APIs

Please find below, results of the tests.

  *Test : Get All APIs*
 *
*
 *
*
 *10 Tenants 100 APIs each (1000 APIs)*
 User Count Average Time (ms)  Single User 3169  10 Users 43230

 *100 Tenants 10 Apis each (1000 APIs)*
 User Count Average Time (ms)  Single User 6119  10 Users 63402  100 Users
185196



 *100 Tenants 20 APIs each (2000 APIs)*
 User Count Average Time (ms)  Single User 14974  10 Users 172514  100 Users
182466  300 Users * 328453

 * With 10.37% of the requests getting timed out


 *100 Tenants 100 APIs each (1 APIs)*
 User Count Average Time (ms)  Single User Fails after 210200





 *Test : Get Recently Published APIs*
 *
*


 *100 Tenants 20 APIs each (2000 APIs)*
 User Count Average Time (ms)  Single User 487  10 Users 3051  100 Users
37852  1000 Users * 328291

 * With 6% of the requests getting timed out


  *Test : Get Tags*
 *
*


 *100 Tenants 20 APIs each (2000 APIs)*
 User Count Average Time (ms)  Single User 682  10 Users 5617  100 Users
85346  1000 Users * 359779

 * With 16.7% of the requests getting timed out



Please note that, these tests were carried out on my local machine.


Thanks and Regards,
Ruwan Yatawara
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stratos 2 ELB : NoSuchMethodError: HttpProtocolParams.getMalformedInputAction

[Lalaji Sureshika]

Hi,

Did you check the ELB built pack contains duplicate versions
of httpcore/httpcore-nio/http-client jars in plugins folder. We got similar
issue in APIManager pack built on 4.1.2.Duplicate version-ed jars issue got
resolved when we update org.wso2.carbon.databridge.datapublisher.feature to
4.1.1 in our product.

Thanks;

Thanks;

On Thu, Mar 28, 2013 at 7:17 PM, Isuru Wimalasundera wrote:

> Hi All
>
> In the latest ELB build from 4.1.1 branch, which is updated to httpcore
> 4.2.3wso2v1 recently, gives the given below error. Any idea on this?
>
> [2013-03-28 20:09:24,150] ERROR - NIOServerCnxn Thread
> Thread[HTTPS-Listener I/O dispatcher-1,5,HTTPS-Listener I/O dispatcher
> thread group] died
> java.lang.NoSuchMethodError:
> org.apache.http.params.HttpProtocolParams.getMalformedInputAction(Lorg/apache/http/params/HttpParams;)Ljava/nio/charset/CodingErrorAction;
> at
> org.apache.http.impl.nio.reactor.SessionInputBufferImpl.(SessionInputBufferImpl.java:78)
> at
> org.apache.http.impl.nio.NHttpConnectionBase.(NHttpConnectionBase.java:146)
> at
> org.apache.http.impl.nio.DefaultNHttpServerConnection.(DefaultNHttpServerConnection.java:93)
> at
> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.(LoggingNHttpServerConnection.java:62)
> at
> org.apache.synapse.transport.http.conn.LoggingUtils.createServerConnection(LoggingUtils.java:73)
> at
> org.apache.synapse.transport.http.conn.ServerConnFactory.createConnection(ServerConnFactory.java:90)
> at
> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:58)
> at
> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:39)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.connected(AbstractIODispatch.java:72)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.sessionCreated(BaseIOReactor.java:242)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:427)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:291)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
> at java.lang.Thread.run(Thread.java:662)
>
> Thanks
> Isuruw
>
> --
> *Isuru Wimalasundera*
> Software Engineer;  WSO2, Inc.; http://wso2.com,
>  mobile: +94 77 920 5641
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lalaji Sureshika
Software Engineer; Development Technologies Team;WSO2, Inc.;
http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stratos 2 ELB : NoSuchMethodError: HttpProtocolParams.getMalformedInputAction

[Isuru Wimalasundera]

This occurs when I joined a App Server to ELB and when trying to open the
management console with host name.


On Thu, Mar 28, 2013 at 8:17 PM, Isuru Wimalasundera wrote:

> Hi All
>
> In the latest ELB build from 4.1.1 branch, which is updated to httpcore
> 4.2.3wso2v1 recently, gives the given below error. Any idea on this?
>
> [2013-03-28 20:09:24,150] ERROR - NIOServerCnxn Thread
> Thread[HTTPS-Listener I/O dispatcher-1,5,HTTPS-Listener I/O dispatcher
> thread group] died
> java.lang.NoSuchMethodError:
> org.apache.http.params.HttpProtocolParams.getMalformedInputAction(Lorg/apache/http/params/HttpParams;)Ljava/nio/charset/CodingErrorAction;
> at
> org.apache.http.impl.nio.reactor.SessionInputBufferImpl.(SessionInputBufferImpl.java:78)
> at
> org.apache.http.impl.nio.NHttpConnectionBase.(NHttpConnectionBase.java:146)
> at
> org.apache.http.impl.nio.DefaultNHttpServerConnection.(DefaultNHttpServerConnection.java:93)
> at
> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.(LoggingNHttpServerConnection.java:62)
> at
> org.apache.synapse.transport.http.conn.LoggingUtils.createServerConnection(LoggingUtils.java:73)
> at
> org.apache.synapse.transport.http.conn.ServerConnFactory.createConnection(ServerConnFactory.java:90)
> at
> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:58)
> at
> org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:39)
> at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.connected(AbstractIODispatch.java:72)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.sessionCreated(BaseIOReactor.java:242)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:427)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:291)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
> at java.lang.Thread.run(Thread.java:662)
>
> Thanks
> Isuruw
>
> --
> *Isuru Wimalasundera*
> Software Engineer;  WSO2, Inc.; http://wso2.com,
>  mobile: +94 77 920 5641
>
>
>


-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stratos 2 ELB : NoSuchMethodError: HttpProtocolParams.getMalformedInputAction

[Isuru Wimalasundera]

Hi All

In the latest ELB build from 4.1.1 branch, which is updated to httpcore
4.2.3wso2v1 recently, gives the given below error. Any idea on this?

[2013-03-28 20:09:24,150] ERROR - NIOServerCnxn Thread
Thread[HTTPS-Listener I/O dispatcher-1,5,HTTPS-Listener I/O dispatcher
thread group] died
java.lang.NoSuchMethodError:
org.apache.http.params.HttpProtocolParams.getMalformedInputAction(Lorg/apache/http/params/HttpParams;)Ljava/nio/charset/CodingErrorAction;
at
org.apache.http.impl.nio.reactor.SessionInputBufferImpl.(SessionInputBufferImpl.java:78)
at
org.apache.http.impl.nio.NHttpConnectionBase.(NHttpConnectionBase.java:146)
at
org.apache.http.impl.nio.DefaultNHttpServerConnection.(DefaultNHttpServerConnection.java:93)
at
org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection.(LoggingNHttpServerConnection.java:62)
at
org.apache.synapse.transport.http.conn.LoggingUtils.createServerConnection(LoggingUtils.java:73)
at
org.apache.synapse.transport.http.conn.ServerConnFactory.createConnection(ServerConnFactory.java:90)
at
org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:58)
at
org.apache.synapse.transport.passthru.ServerIODispatch.createConnection(ServerIODispatch.java:39)
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.connected(AbstractIODispatch.java:72)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.sessionCreated(BaseIOReactor.java:242)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:427)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:291)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
at java.lang.Thread.run(Thread.java:662)

Thanks
Isuruw

-- 
*Isuru Wimalasundera*
Software Engineer;  WSO2, Inc.; http://wso2.com,
 mobile: +94 77 920 5641
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API-GW uses older Synapse version 2.1.0-wso2v9

[Nuwan Dias]

Updated APIM components. Thanks.

Regards,
NuwanD.


On Thu, Mar 28, 2013 at 7:32 PM, Kasun Indrasiri  wrote:

> Please check for all place where Synapse is used and update it to 2.1.1v4.
>
> 
> org.apache.synapse
> synapse-core
> 2.1.0-wso2v9
> 
> 
> org.apache.axis2
> axis2-codegen
> 
> 
> 
>
>
>
>
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/apimgt/org.wso2.carbon.apimgt.gateway/1.1.2
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/




-- 
Nuwan Dias

Member, Management Committee - Solutions Technology Group
Software Engineer - 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

[Dev] API-GW uses older Synapse version 2.1.0-wso2v9

[Kasun Indrasiri]

Please check for all place where Synapse is used and update it to 2.1.1v4.


org.apache.synapse
synapse-core
2.1.0-wso2v9


org.apache.axis2
axis2-codegen






https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/apimgt/org.wso2.carbon.apimgt.gateway/1.1.2

-- 
Kasun Indrasiri
Associate Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue with a load test with AS 5.1.0 and BAM 2.2.0

[Jorge Infante Osorio]

Hi Kasun.
I change the server name to post this question. This is not the problem. I
can consume this endpoint  using soapui.

The scenario work fine for a while, in the load test it work the last time
for 6632 requests, after that the AS stop processing requests. 

I can see in BAM cluster the events send by AS, so BAM is properly
integrated with AS. Also in the dashboard I see the AS statistic.

If I don´t run the load test the scenario work fine, but when I increase the
load it fail after a while.


Saludos,
Ing. Jorge Infante Osorio.
CDAE.
Fac. 5.
UCI.
“En un mundo perfecto las pizzas serían una comida saludable, las laptops se
cargarían desde una fuente de corriente inalámbrica y todos los JAR serían
bundles de OSGI ”

De: Kasun Gajasinghe [mailto:kas...@wso2.com] 
Enviado el: jueves, 28 de marzo de 2013 5:25
Para: Jorge Infante Osorio
CC: DEV
Asunto: Re: [Dev] Issue with a load test with AS 5.1.0 and BAM 2.2.0

Hi Jorge,

Does this endpoint url of your data service is correct? [1] Also, please
make sure that BAM is properly integrated with AS by verifying the stream
data in cassandra storage.

[1] http://server:80/services/datos_DataService.SOAP12Endpoint/

On Thu, Mar 28, 2013 at 10:11 AM, Jorge Infante Osorio 
wrote:
Hi folks.
I don´t have internet connection to post this question in stackoverflow.
Sorry for that.

During a load test in AS 5.1.0 with a data service and the AS service agent
sending events to BAM 2.2.0 I see this errors (without BAM the test pass
successfully):

This error appears after a while.

TID: [0] [AS] [2013-03-27 13:13:34,507]  INFO
{org.apache.axis2.transport.http.HTTPSender} -  Unable to sendViaPost to
url[http://server:80/services/datos_DataService.SOAP12Endpoint/]
{org.apache.axis2.transport.http.HTTPSender}
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(Unknown Source)
        at java.io.BufferedInputStream.fill(Unknown Source)
        at java.io.BufferedInputStream.read(Unknown Source)
        at
org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
        at
org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
        at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:11
16)
        at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnect
ionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
        at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.j
ava:1973)
        at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.jav
a:1735)
        at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:109
8)
        at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethod
Director.java:398)
        at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDir
ector.java:171)
        at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
        at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTT
PSender.java:622)
        at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
        at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
        at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithC
ommons(CommonsHTTPTransportSender.java:451)
        at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTT
PTransportSender.java:278)
        at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
        at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:398)
        at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
peration.java:224)
        at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
        at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:554)
        at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:530)
        at
org.apache.jsp.admin.jsp.WSRequestXSSproxy_005fajaxprocessor_jsp._jspService
(org.apache.jsp.admin.jsp.WSRequestXSSproxy_005fajaxprocessor_jsp:274)
        at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:4
03)
        at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
        at
org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at
org.eclipse.equino

Re: [Dev] Usability improvement for API-M subscription

[Afkham Azeez]

On Thu, Mar 28, 2013 at 5:54 PM, Chanaka Jayasena  wrote:

> It's better to have an Application centered view along with the API
> centered view.
>

+1


>  I think there are lot of usability improvements that we can do along with
> that. We can do some mock-up base discussions and do these improvements. I
> am not sure when and which version we should target.
>
> thanks,
> Chanaka
>
>
> On Thu, Mar 28, 2013 at 3:58 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Thu, Mar 28, 2013 at 3:23 PM, Lalaji Sureshika wrote:
>>
>>> Hi,
>>>
>>> On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez  wrote:
>>>


 On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez  wrote:

>
>
> On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika wrote:
>
>> Hi,
>>
>> On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias  wrote:
>>>
 On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez wrote:

>
>
> On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe <
> sume...@wso2.com> wrote:
>
>> On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez wrote:
>>
>>> Right now you have to navigate to an API, and then associate it
>>> with an Application. Edit Application only allows you to change the 
>>> name &
>>> tier. IMO, it is more natural to create an application, and then 
>>> add APIs
>>> to that application, rather than navigating to the API & then 
>>> adding it to
>>> the app.
>>
>>
>> Azeez,
>> Your suggesting a UI enhancement. right?
>> This means with in application view, we should provide some means
>> of searching for APIs, then select version.
>>
>
>
> Yes, UI enhancement.
>

 I'm guessing it would be something like this.

 List My Applications -> Choose an Application and click "Add APIs"
 -> Search for APIs and select the ones to be added to the App -> 
 Commit.

>>>
>>> Yes, that is correct. My concern is, once you create an Application,
>>> you are lost because the flow is broken. You have to start a new flow by
>>> going to APIs, and then associate an app with the APIs.
>>>
>>
>>I guess,if there's a link available in Applications page pointing
>> to APIs page with some indication similar to to 'select APIs from browse
>> APIs page' will be sufficient..As APIs page already providing
>>  browse/search/subscribe to APIs..
>>
>
> No it is not sufficient. Once you add an application, it appears on
> the list at the bottom part of the page. Add application should be a
> wizard.
>
> Step 1: Define application name
> Step 2: Select tier - this page needs to contain briefly what each
> tier provides, features/limitations etc.
> Step 3: Add APIs to Application
> Step 4: Generate keys
>
> The user experience should be smooth & unbroken. This is not just a
> problem with API-M UIs, but may of our other UIs as well. We need to make
> an effort to improve these aspects, and such small improvements will go a
> long way.
>

>>>  Should this be added as a work item for a future release/current
>>> release?
>>>
>>> With the above your suggested way,for Step 3 and Step4,are you
>>> suggesting to redirect to existing browse API and subscriptions pages or
>>> introducing new popup UIs.
>>>
>>
>> New UIs.
>>
>>
>>> Please pardon,but still I believe,once an application created,if there's
>>> a link available in the created application row to redirect into APIs
>>> page,it'll support your flow from the step 3 and continue.But with that
>>> way,the current limitation is,you cannot subscribe to multiple APIs at one
>>> time.
>>>
>>
>> that is not a natural flow because once you are in the API-first view,
>> you have to select the application again from the dropdown, and you have to
>> repeat the same for each & every API you want to add to the application
>>
>>
>>>
>>> Anyhow,if we are going to implement above,I believe it has to be done in
>>> a future release[ Not the next release 1.4.0],as we have to come up with a
>>> proper UI design.
>>>
>>> Thanks;
>>>


>
>
>>
>> Thanks;
>>
>> Thanks;
>>
>>>
>>>

 Thanks,
 NuwanD.

>
>
>>
>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: 
>>> **http://twitter.com/afkham_azeez*

Re: [Dev] Usability improvement for API-M subscription

[Chanaka Jayasena]

It's better to have an Application centered view along with the API
centered view. I think there are lot of usability improvements that we can
do along with that. We can do some mock-up base discussions and do these
improvements. I am not sure when and which version we should target.

thanks,
Chanaka


On Thu, Mar 28, 2013 at 3:58 PM, Afkham Azeez  wrote:

>
>
> On Thu, Mar 28, 2013 at 3:23 PM, Lalaji Sureshika  wrote:
>
>> Hi,
>>
>> On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez  wrote:
>>>


 On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika wrote:

> Hi,
>
> On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias  wrote:
>>
>>> On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez wrote:
>>>


 On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe <
 sume...@wso2.com> wrote:

> On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez wrote:
>
>> Right now you have to navigate to an API, and then associate it
>> with an Application. Edit Application only allows you to change the 
>> name &
>> tier. IMO, it is more natural to create an application, and then add 
>> APIs
>> to that application, rather than navigating to the API & then adding 
>> it to
>> the app.
>
>
> Azeez,
> Your suggesting a UI enhancement. right?
> This means with in application view, we should provide some means
> of searching for APIs, then select version.
>


 Yes, UI enhancement.

>>>
>>> I'm guessing it would be something like this.
>>>
>>> List My Applications -> Choose an Application and click "Add APIs"
>>> -> Search for APIs and select the ones to be added to the App -> Commit.
>>>
>>
>> Yes, that is correct. My concern is, once you create an Application,
>> you are lost because the flow is broken. You have to start a new flow by
>> going to APIs, and then associate an app with the APIs.
>>
>
>I guess,if there's a link available in Applications page pointing
> to APIs page with some indication similar to to 'select APIs from browse
> APIs page' will be sufficient..As APIs page already providing
>  browse/search/subscribe to APIs..
>

 No it is not sufficient. Once you add an application, it appears on the
 list at the bottom part of the page. Add application should be a wizard.

 Step 1: Define application name
 Step 2: Select tier - this page needs to contain briefly what each tier
 provides, features/limitations etc.
 Step 3: Add APIs to Application
 Step 4: Generate keys

 The user experience should be smooth & unbroken. This is not just a
 problem with API-M UIs, but may of our other UIs as well. We need to make
 an effort to improve these aspects, and such small improvements will go a
 long way.

>>>
>>  Should this be added as a work item for a future release/current release?
>>
>> With the above your suggested way,for Step 3 and Step4,are you suggesting
>> to redirect to existing browse API and subscriptions pages or introducing
>> new popup UIs.
>>
>
> New UIs.
>
>
>> Please pardon,but still I believe,once an application created,if there's
>> a link available in the created application row to redirect into APIs
>> page,it'll support your flow from the step 3 and continue.But with that
>> way,the current limitation is,you cannot subscribe to multiple APIs at one
>> time.
>>
>
> that is not a natural flow because once you are in the API-first view, you
> have to select the application again from the dropdown, and you have to
> repeat the same for each & every API you want to add to the application
>
>
>>
>> Anyhow,if we are going to implement above,I believe it has to be done in
>> a future release[ Not the next release 1.4.0],as we have to come up with a
>> proper UI design.
>>
>> Thanks;
>>
>>>
>>>


>
> Thanks;
>
> Thanks;
>
>>
>>
>>>
>>> Thanks,
>>> NuwanD.
>>>


>
>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> /sumedha

Re: [Dev] Usability improvement for API-M subscription

[Afkham Azeez]

On Thu, Mar 28, 2013 at 3:23 PM, Lalaji Sureshika  wrote:

> Hi,
>
> On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika wrote:
>>>
 Hi,

 On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez  wrote:

>
>
> On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias  wrote:
>
>> On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>> On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe <
>>> sume...@wso2.com> wrote:
>>>
 On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez wrote:

> Right now you have to navigate to an API, and then associate it
> with an Application. Edit Application only allows you to change the 
> name &
> tier. IMO, it is more natural to create an application, and then add 
> APIs
> to that application, rather than navigating to the API & then adding 
> it to
> the app.


 Azeez,
 Your suggesting a UI enhancement. right?
 This means with in application view, we should provide some means
 of searching for APIs, then select version.

>>>
>>>
>>> Yes, UI enhancement.
>>>
>>
>> I'm guessing it would be something like this.
>>
>> List My Applications -> Choose an Application and click "Add APIs" ->
>> Search for APIs and select the ones to be added to the App -> Commit.
>>
>
> Yes, that is correct. My concern is, once you create an Application,
> you are lost because the flow is broken. You have to start a new flow by
> going to APIs, and then associate an app with the APIs.
>

I guess,if there's a link available in Applications page pointing to
 APIs page with some indication similar to to 'select APIs from browse APIs
 page' will be sufficient..As APIs page already providing
  browse/search/subscribe to APIs..

>>>
>>> No it is not sufficient. Once you add an application, it appears on the
>>> list at the bottom part of the page. Add application should be a wizard.
>>>
>>> Step 1: Define application name
>>> Step 2: Select tier - this page needs to contain briefly what each tier
>>> provides, features/limitations etc.
>>> Step 3: Add APIs to Application
>>> Step 4: Generate keys
>>>
>>> The user experience should be smooth & unbroken. This is not just a
>>> problem with API-M UIs, but may of our other UIs as well. We need to make
>>> an effort to improve these aspects, and such small improvements will go a
>>> long way.
>>>
>>
>  Should this be added as a work item for a future release/current release?
>
> With the above your suggested way,for Step 3 and Step4,are you suggesting
> to redirect to existing browse API and subscriptions pages or introducing
> new popup UIs.
>

New UIs.


> Please pardon,but still I believe,once an application created,if there's
> a link available in the created application row to redirect into APIs
> page,it'll support your flow from the step 3 and continue.But with that
> way,the current limitation is,you cannot subscribe to multiple APIs at one
> time.
>

that is not a natural flow because once you are in the API-first view, you
have to select the application again from the dropdown, and you have to
repeat the same for each & every API you want to add to the application


>
> Anyhow,if we are going to implement above,I believe it has to be done in a
> future release[ Not the next release 1.4.0],as we have to come up with a
> proper UI design.
>
> Thanks;
>
>>
>>
>>>
>>>

 Thanks;

 Thanks;

>
>
>>
>> Thanks,
>> NuwanD.
>>
>>>
>>>


>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>



 --
 /sumedha
 m: +94 773017743
 b :  bit.ly/sumedha

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: 
>>> **http://twitter.com/afkham_azeez*
>>> *
>>> linked

Re: [Dev] Usability improvement for API-M subscription

[Lalaji Sureshika]

Hi,

On Thu, Mar 28, 2013 at 10:59 AM, Afkham Azeez  wrote:

>
>
> On Wed, Mar 27, 2013 at 3:33 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Mar 27, 2013 at 3:02 PM, Lalaji Sureshika wrote:
>>
>>> Hi,
>>>
>>> On Wed, Mar 27, 2013 at 1:40 PM, Afkham Azeez  wrote:
>>>


 On Wed, Mar 27, 2013 at 2:39 PM, Nuwan Dias  wrote:

> On Wed, Mar 27, 2013 at 2:35 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Mar 27, 2013 at 2:33 PM, Sumedha Rubasinghe > > wrote:
>>
>>> On Wed, Mar 27, 2013 at 2:24 PM, Afkham Azeez wrote:
>>>
 Right now you have to navigate to an API, and then associate it
 with an Application. Edit Application only allows you to change the 
 name &
 tier. IMO, it is more natural to create an application, and then add 
 APIs
 to that application, rather than navigating to the API & then adding 
 it to
 the app.
>>>
>>>
>>> Azeez,
>>> Your suggesting a UI enhancement. right?
>>> This means with in application view, we should provide some means of
>>> searching for APIs, then select version.
>>>
>>
>>
>> Yes, UI enhancement.
>>
>
> I'm guessing it would be something like this.
>
> List My Applications -> Choose an Application and click "Add APIs" ->
> Search for APIs and select the ones to be added to the App -> Commit.
>

 Yes, that is correct. My concern is, once you create an Application,
 you are lost because the flow is broken. You have to start a new flow by
 going to APIs, and then associate an app with the APIs.

>>>
>>>I guess,if there's a link available in Applications page pointing to
>>> APIs page with some indication similar to to 'select APIs from browse APIs
>>> page' will be sufficient..As APIs page already providing
>>>  browse/search/subscribe to APIs..
>>>
>>
>> No it is not sufficient. Once you add an application, it appears on the
>> list at the bottom part of the page. Add application should be a wizard.
>>
>> Step 1: Define application name
>> Step 2: Select tier - this page needs to contain briefly what each tier
>> provides, features/limitations etc.
>> Step 3: Add APIs to Application
>> Step 4: Generate keys
>>
>> The user experience should be smooth & unbroken. This is not just a
>> problem with API-M UIs, but may of our other UIs as well. We need to make
>> an effort to improve these aspects, and such small improvements will go a
>> long way.
>>
>
 Should this be added as a work item for a future release/current release?

With the above your suggested way,for Step 3 and Step4,are you suggesting
to redirect to existing browse API and subscriptions pages or introducing
new popup UIs.
Please pardon,but still I believe,once an application created,if there's
a link available in the created application row to redirect into APIs
page,it'll support your flow from the step 3 and continue.But with that
way,the current limitation is,you cannot subscribe to multiple APIs at one
time.

Anyhow,if we are going to implement above,I believe it has to be done in a
future release[ Not the next release 1.4.0],as we have to come up with a
proper UI design.

Thanks;

>
>
>>
>>
>>>
>>> Thanks;
>>>
>>> Thanks;
>>>


>
> Thanks,
> NuwanD.
>
>>
>>
>>>
>>>


 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * **
 email: **az...@wso2.com* * cell: +94 77 3320919
 blog: **http://blog.afkham.org* *
 twitter: 
 **http://twitter.com/afkham_azeez*
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*

>>>
>>>
>>>
>>> --
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Member, Management Committee - Solutions Technology Group
> Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 77