jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60889] JMeter JDBC sample will call SELECT USER() when testing with MySQL JDBC
Date Fri, 07 Apr 2017 16:49:58 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60889

--- Comment #13 from Philippe Mouawad <p.mouawad@ubik-ingenierie.com> ---
(In reply to Liu XP from comment #12)
> In JMeter 3.1 response, we can see more info about the JDBC URL and
> DriverName.
> It is good for us know detail JDBC pool info that was used by JDBC sampler
> in View Results Tree.
> 
> 3.1 Response headers:
> 1190470568,
> URL=jdbc:mysql://10.100.17.1:3306/test?useUnicode=true&characterEncoding=utf-
> 8, UserName=test@10.101.20.49, MySQL-AB JDBC Driver
> 
> I think JDBC pool name, JDBC URL and DriverName is valuable in response. 

Unfortunately giving such information requires for now calling a method on
Connection which might trigger a server call.
Fixing that would require storing this info in DataSourceComponentImpl (see
DataSourceComponent.java) so that it can be reused in JDBCSampler class in 
DataSourceElement.getConnection(getDataSource()); which would need to be
changed.

If you want this to be integrated before 3.2 release, then please provide a PR,
otherwise we'll have to wait after that.

A quick fix is to just call:
res.setResponseHeaders(getDataSource());

This would not lose information compared to 2.13 but it would compared to
3.0/3.1. And I don't know if many users use this information.




And
> I agree with your opinion that we should not put any information that
> impacts load on DB Server or response times. And your patch suggestion is
> also reasonable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message