You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Sky Wang (JIRA)" <ji...@apache.org> on 2008/10/23 09:42:52 UTC
[jira] Created: (CAMEL-1019) unexpected result in pressure testing
unexpected result in pressure testing
-------------------------------------
Key: CAMEL-1019
URL: https://issues.apache.org/activemq/browse/CAMEL-1019
Project: Apache Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 1.4.0
Environment: operating system: Red Hat Enterprise Linux AS release 3
Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
software plaform: apache-camel-1.4.0
Reporter: Sky Wang
I develop an application on camel.It's routing logic as follows:
<route>
<from uri="cxf:bean:routerEndpoint" />
<try>
<process ref="ipValidateProcessor" />
<choice>
<when>
<!-- First predicate -->
<el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
<to uri="cxf:bean:serviceEndpoint" />
<process ref="responseProcessor" />
</when>
<otherwise>
<process ref="invalidIPProcessor" />
</otherwise>
</choice>
<catch>
<exception>com.aspire.archtype.camel.exception.AppException</exception>
<process ref="sreExceptionHandler"></process>
</catch>
</try>
</route>
I do a pressure testing on this application with LoadRunner.
My test case is as follows:
1. loadrunner send a reqeust
2. server receive the request, and then forward it to IPValidateProcessor
3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
4. do <to uri="cxf:bean:serviceEndpoint" />
5. do <process ref="responseProcessor" />
6. end
I only want to test the <when> clause in the routing logic.
When only one virtual user runs the test case once, it runs ok.
But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1019) unexpected result in pressure testing
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1019:
-----------------------------------
Fix Version/s: 1.5.0
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Assignee: Willem Jiang
> Fix For: 1.5.0
>
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1019) unexpected result in pressure testing
Posted by "Sky Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sky Wang updated CAMEL-1019:
----------------------------
Attachment: processors.rar
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Sky Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46775#action_46775 ]
Sky Wang commented on CAMEL-1019:
---------------------------------
IPValidateProcessor doesn't care about requestor's IP address, I hard code follow logic in the processor:
exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Sky Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46777#action_46777 ]
Sky Wang commented on CAMEL-1019:
---------------------------------
some output log in the invalidIPProcessor:
...
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
Request ServiceID is [2674]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
Request ServiceID is [2674]
IP_VALIDATE_RESULT is [null]
...
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46773#action_46773 ]
Willem Jiang commented on CAMEL-1019:
-------------------------------------
Are your virtual users using the same IP address to send the request ?
Can you write the log in the responseProcessor for tracing the request?
I don't think it is a concurrent issue of camel, here are some document about it[1].
[1] http://activemq.apache.org/camel/parallel-processing-and-ordering.html
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46789#action_46789 ]
Willem Jiang commented on CAMEL-1019:
-------------------------------------
After went through your code, I found you made a great mistake in your processor.
You can't store the exchange as the object member, which is the critical variable when you run the processor in the multi-thread environment.
Since more than one thread can change the exchange object in the IPValidateProcessor, that will explain why your IPValidateProcessor can't set the right exchange's message header.
You need to keep your processors to use the original process method, which makes sure your processor's process method is reentrant function(可重入函数).
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46774#action_46774 ]
Willem Jiang commented on CAMEL-1019:
-------------------------------------
Did you try to send the request with 5 , 10, 20 virtual user ?
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1019) unexpected result in pressure testing
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-1019.
---------------------------------
Assignee: Willem Jiang
Resolution: Won't Fix
This is a user code error.
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Assignee: Willem Jiang
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Sky Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46815#action_46815 ]
Sky Wang commented on CAMEL-1019:
---------------------------------
Willem, you are right.I have a mistake understanding about processor. Thanks a lot for your help!
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
> Assignee: Willem Jiang
> Fix For: 1.5.0
>
> Attachments: processors.rar
>
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1019) unexpected result in pressure
testing
Posted by "Sky Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46776#action_46776 ]
Sky Wang commented on CAMEL-1019:
---------------------------------
I try 10 virtual users, the same result.
I have upload my processors in the attachments.
> unexpected result in pressure testing
> -------------------------------------
>
> Key: CAMEL-1019
> URL: https://issues.apache.org/activemq/browse/CAMEL-1019
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.4.0
> Environment: operating system: Red Hat Enterprise Linux AS release 3
> Hardware:HP PROLIANT BL460c ,4Core CPU, 4G Memory
> software plaform: apache-camel-1.4.0
> Reporter: Sky Wang
>
> I develop an application on camel.It's routing logic as follows:
> <route>
> <from uri="cxf:bean:routerEndpoint" />
> <try>
> <process ref="ipValidateProcessor" />
> <choice>
> <when>
> <!-- First predicate -->
> <el>${in.headers.IP_VALIDATE_RESULT == 'true'}</el>
> <to uri="cxf:bean:serviceEndpoint" />
> <process ref="responseProcessor" />
> </when>
> <otherwise>
> <process ref="invalidIPProcessor" />
> </otherwise>
> </choice>
> <catch>
> <exception>com.aspire.archtype.camel.exception.AppException</exception>
> <process ref="sreExceptionHandler"></process>
> </catch>
> </try>
> </route>
> I do a pressure testing on this application with LoadRunner.
> My test case is as follows:
> 1. loadrunner send a reqeust
> 2. server receive the request, and then forward it to IPValidateProcessor
> 3. IPValidateProcessor set exchange.getIn().setHeader("IP_VALIDATE_RESULT", "true");
> 4. do <to uri="cxf:bean:serviceEndpoint" />
> 5. do <process ref="responseProcessor" />
> 6. end
> I only want to test the <when> clause in the routing logic.
> When only one virtual user runs the test case once, it runs ok.
> But when have 30 virtual users concurrent run for 1 minute, some of the transactions run into <otherwise> clause.I found that they run into <otherwise> because in.headers.IP_VALIDATE_RESULT is null.
> I don't now why, the same requests, most run into <when> clause, few run into <otherwith> clause?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.