Re: ApacheJMeter_mongodb is missing from maven central

2014-01-11 Thread Mark Collin
Do you have a rough ETA for getting the 2.10 and 2.11 ApacheJMeter_mongodb jars 
up in maven central?

I have a new release of the jmeter-maven-plugin ready to go and I’m trying to 
decide whether to wait for the jar to be in maven central, or just mark the 
missing jar as a known problem with a workaround for when it is available.


On 8 Jan 2014, at 00:22, sebb seb...@gmail.com wrote:

 On 8 January 2014 00:09, Milamber milam...@apache.org wrote:
 Hello,
 
 Thanks for report. I've fixed this for next release.
 
 @Sebb, what is the best way to upload the mongo maven package ?
 
 I don't know if it's possible to add extra jars to an existing release or
 not.
 I suggest you ask on the Maven user list.
 
 Note: since the pom is source, we probably ought to vote on the updates.
 Also we should ensure that the jars in the release are copies of the
 ones in the binary archive, rather than rebuilds.
 
 Since all write access to Maven Central is via Nexus, and Nexus can
 only hold one staging area for each GA pair, this will have to be done
 in two stages.
 i.e. upload 2.10 (somehow), vote, promote
 then repeat for 2.11
 
 Milamber
 
 
 Le 07/01/2014 10:54, Mark Collin a ecrit :
 
 I’ve logged this as:
 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=55965
 
 
 On 7 Jan 2014, at 10:47, Mark Collin mark.col...@lazeryattack.com
 wrote:
 
 Just been going through the dependencies in maven central today and
 I’ve
 noticed that ApacheJMeter_mongodb is missing for 2.10 and 2.11.
 
 Can these be uploaded?
 
 
 



enhancement to jmeter.sh startup script

2014-01-11 Thread James Liang
Hi guys,

The bin/jmeter.sh script will fail to launch if it is called via symlink or 
called from outside of bin.

Adding the following snippet of script will resolve the true path, cd to it, 
and then start jmeter.

--

# resolve the true full path (e.g. called from outside of bin, called via 
symlinks, and etc.)
SOURCE=${BASH_SOURCE[0]}
while [ -h $SOURCE ]; do # resolve $SOURCE until the file is no longer a 
symlink
  DIR=$( cd -P $( dirname $SOURCE )  pwd )
  SOURCE=$(readlink $SOURCE)
  [[ $SOURCE != /* ]]  SOURCE=$DIR/$SOURCE # if $SOURCE was a relative 
symlink, we need to resolve it relative to the path where the symlink file was 
located
done
DIR=$( cd -P $( dirname $SOURCE )  pwd )

echo start jmeter.sh from $DIR
cd $DIR

# the rest of the jmeter.sh scripts
# i.e.  JMETER_OPTS= ...



Thanks,
James Liang




Re: enhancement to jmeter.sh startup script

2014-01-11 Thread sebb
On 12 January 2014 00:00, James Liang jli...@andera.com wrote:
 Hi guys,

 The bin/jmeter.sh script will fail to launch if it is called via symlink or 
 called from outside of bin.

 Adding the following snippet of script will resolve the true path, cd to it, 
 and then start jmeter.

Thanks - could you add that to a Bugzilla issue?

Also, does that fix work for all shells?
It looks like it might be specific to bash.

 --

 # resolve the true full path (e.g. called from outside of bin, called via 
 symlinks, and etc.)
 SOURCE=${BASH_SOURCE[0]}
 while [ -h $SOURCE ]; do # resolve $SOURCE until the file is no longer a 
 symlink
   DIR=$( cd -P $( dirname $SOURCE )  pwd )
   SOURCE=$(readlink $SOURCE)
   [[ $SOURCE != /* ]]  SOURCE=$DIR/$SOURCE # if $SOURCE was a relative 
 symlink, we need to resolve it relative to the path where the symlink file 
 was located
 done
 DIR=$( cd -P $( dirname $SOURCE )  pwd )

 echo start jmeter.sh from $DIR
 cd $DIR

 # the rest of the jmeter.sh scripts
 # i.e.  JMETER_OPTS= ...



 Thanks,
 James Liang




bug and fix for ProxyControl.deliverSampler() method

2014-01-11 Thread James Liang
Bug:

The Test Script Recorder (proxy) supports filtering of url patterns before 
sending the http requests to the Recording Controller.  Just to be clear, this 
part works.  However, if we add a View Results Tree element to the Test Script 
Recorder, the View Results Tree captures all calls and completely ignores the 
filtering rules.

As a result the calls captured by Recording Controller is in consistent with 
the View Results Tree of the recorder.  This complicates the reconciliation of 
the captured tests and the recorded result tree.  Furthermore, the filter is 
use to filter out resources (e.g. jpg, css, etc.) which are quite numerous.  
The test script recorder would be easier to use and more consistent if the Test 
Script Recorder honors the filter rule when it forwards the result to the View 
Results Tree.  In other words, the Test Scripts Recorder should send the same 
output to both the Recording Controller and View Results Tree.

Fix:
ProxyControl.java

method:
public synchronized void deliverSampler(final HTTPSamplerBase sampler, final 
TestElement[] subConfigs, final SampleResult result)

changes:

move line 545 to after 536 (before 537) so that the filter rule applies to the 
notification.

The code of the line to move is:
notifySampleListeners(new SampleEvent(result, WorkBench)); // TODO - is this 
the correct threadgroup name?

I've attached the corrected java file.  The fix is based on the v2_10 src tree.
http://svn.apache.org/viewvc/jmeter/tags/v2_10/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java?revision=1533926view=markup



Thanks,
James Liang




Re: bug and fix for ProxyControl.deliverSampler() method

2014-01-11 Thread sebb
Bug reports and enhancement requests are much easier to keep track of
if they are recorded in the JMeter issue tracking system, i.e.
Bugzilla.

Could you please create yourself a login and upload the details there?
Thanks!


On 12 January 2014 00:35, James Liang jli...@andera.com wrote:
 Bug:



 The Test Script Recorder (proxy) supports filtering of url patterns before
 sending the http requests to the Recording Controller.  Just to be clear,
 this part works.  However, if we add a View Results Tree element to the Test
 Script Recorder, the View Results Tree captures all calls and completely
 ignores the filtering rules.



 As a result the calls captured by Recording Controller is in consistent with
 the View Results Tree of the recorder.  This complicates the reconciliation
 of the captured tests and the recorded result tree.  Furthermore, the filter
 is use to filter out resources (e.g. jpg, css, etc.) which are quite
 numerous.  The test script recorder would be easier to use and more
 consistent if the Test Script Recorder honors the filter rule when it
 forwards the result to the View Results Tree.  In other words, the Test
 Scripts Recorder should send the same output to both the Recording
 Controller and View Results Tree.



 Fix:

 ProxyControl.java



 method:

 public synchronized void deliverSampler(final HTTPSamplerBase sampler, final
 TestElement[] subConfigs, final SampleResult result)



 changes:



 move line 545 to after 536 (before 537) so that the filter rule applies to
 the notification.



 The code of the line to move is:

 notifySampleListeners(new SampleEvent(result, WorkBench)); // TODO - is
 this the correct threadgroup name?



 I’ve attached the corrected java file.  The fix is based on the v2_10 src
 tree.

 http://svn.apache.org/viewvc/jmeter/tags/v2_10/src/protocol/http/org/apache/jmeter/protocol/http/proxy/ProxyControl.java?revision=1533926view=markup







 Thanks,

 James Liang