[Bug 61319] jmeter 3.2 Smtp smapler The same script Different in different versions running state, jmeter 3.2 false, jmeter 3.1 true, why? Can someone answer that?

2023-05-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61319 dfou...@apache.org changed: What|Removed |Added Group||readonly Group

[Bug 66139] Open Model Thread Group using CSV Data Set Config

2022-09-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66139 dfou...@apache.org changed: What|Removed |Added Summary|Open Model Thread Group |Open Model Thread Group

[Bug 66139] Open Model Thread Group using CSV Data Set Configfd

2022-09-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66139 dfou...@apache.org changed: What|Removed |Added Group||readonly Summary|Open

[Bug 66139] Open Model Thread Group using CSV Data Set Config

2022-09-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66139 Vladimir Sitnikov changed: What|Removed |Added Summary|Open Model Thread Group |Open Model Thread Group

[Bug 66139] Open Model Thread Group using CSV Data Set Confi

2022-09-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66139 Vladimir Sitnikov changed: What|Removed |Added Summary|Open Model Thread Group |Open Model Thread Group

[Bug 66270] New: TestStateListener implementation should be supported for NoThreadClone elements only

2022-09-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66270 Bug ID: 66270 Summary: TestStateListener implementation should be supported for NoThreadClone elements only Product: JMeter Version: 5.5 Hardware: All OS

[Bug 66269] HeaderManager instances could be reused across threads

2022-09-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66269 Vladimir Sitnikov changed: What|Removed |Added Summary|HeaderManager instances |HeaderManager instances

[Bug 66269] New: HeaderManager instances could be reused across instances

2022-09-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66269 Bug ID: 66269 Summary: HeaderManager instances could be reused across instances Product: JMeter Version: 5.5 Hardware: All OS: All Status

[Bug 66268] New: Jmeter response getting truncated

2022-09-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66268 Bug ID: 66268 Summary: Jmeter response getting truncated Product: JMeter Version: 5.4.1 Hardware: PC Status: NEW Severity: major Priority: P2

Bug report for JMeter [2022/09/18]

2022-09-18 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66265] JSR / groovy get crazy when using ${__counter} in commented out line

2022-09-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66265 --- Comment #2 from Felix Schumacher --- After sending the last comment, it struck me, that the problem here is, that the missing argument to counter lets JMeter use the original text as a script and that leads to Groovy seeing

[Bug 66265] JSR / groovy get crazy when using ${__counter} in commented out line

2022-09-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66265 Felix Schumacher changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Felix

[Bug 66264] Token Parsing Error:Lexcial error at line....Encountered:"\u202a"(8234)

2022-09-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66264 Felix Schumacher changed: What|Removed |Added OS||All Status|NEW

[Bug 66265] New: JSR / groovy get crazy when using ${__counter} in commented out line

2022-09-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66265 Bug ID: 66265 Summary: JSR / groovy get crazy when using ${__counter} in commented out line Product: JMeter Version: 5.5 Hardware: PC OS: All

[Bug 66264] New: Token Parsing Error:Lexcial error at line....Encountered:"\u202a"(8234)

2022-09-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66264 Bug ID: 66264 Summary: Token Parsing Error:Lexcial error at lineEncountered:"\u202a"(8234) Product: JMeter Version: 5.0 Hardware: PC S

[Bug 66262] New: No possibility to record connectTime with backend listener

2022-09-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66262 Bug ID: 66262 Summary: No possibility to record connectTime with backend listener Product: JMeter Version: 5.5 Hardware: PC OS: All Status

[Bug 66261] New: JDBC requests in a Transaction Controller not use the same connection。

2022-09-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66261 Bug ID: 66261 Summary: JDBC requests in a Transaction Controller not use the same connection。 Product: JMeter Version: unspecified Hardware: PC Status: NEW

[Bug 66251] JMeter does not support files with Chinese/Japanese characters

2022-09-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66251 --- Comment #2 from Ziven --- Created attachment 38387 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38387=edit Step2. After the upload, it cant show Chinese Characters as expected -- You are receiving this mail because:

[Bug 66251] JMeter does not support files with Chinese/Japanese characters

2022-09-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66251 --- Comment #1 from Ziven --- Created attachment 38386 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38386=edit Choose a File With Chinese Characters In Filename to upload -- You are receiving this mail because: You are the assig

[Bug 66250] Loop Controller not working with HTTP Cache Manager Enabled

2022-09-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66250 --- Comment #1 from Jerome --- If you're making the same Get requests in a loop then the cache manager will not send several identical requests. Instead you'll see "No Request Sent (Queried From Cache)" in the response message. Try

[Bug 66258] New: Distribute as Flatpak at Flathub

2022-09-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66258 Bug ID: 66258 Summary: Distribute as Flatpak at Flathub Product: JMeter Version: unspecified Hardware: All OS: Linux Status: NEW Severity: enhancement

Bug report for JMeter [2022/09/11]

2022-09-11 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66251] New: JMeter does not support files with Chinese/Japanese characters

2022-09-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66251 Bug ID: 66251 Summary: JMeter does not support files with Chinese/Japanese characters Product: JMeter Version: 5.4.3 Hardware: PC OS: Linux

Bug report for JMeter [2022/09/04]

2022-09-04 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66250] New: Loop Controller not working with HTTP Cache Manager Enabled

2022-09-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66250 Bug ID: 66250 Summary: Loop Controller not working with HTTP Cache Manager Enabled Product: JMeter Version: 5.5 Hardware: PC OS: Linux Status

[Bug 66249] New: Help button not launching the browser

2022-09-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66249 Bug ID: 66249 Summary: Help button not launching the browser Product: JMeter Version: 5.5 Hardware: PC OS: Linux Status: NEW Severity: minor

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-09-01 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #7 from John --- When this is for testing for services used by a browser I agree (mostly). I'm testing services which are use from another service. So no browser involved. The calling service is using connection pooling, so

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-09-01 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #6 from Vladimir Sitnikov --- Well, historically, JMeter thread corresponds to a "user session", so per-thread caching is probably not that far from what typical applications would have. For instance, if you fully

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-09-01 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #5 from John --- Maybe, but it is not included in the next requests in the same thread. Even if keepalive is turned off. So for the next connect it is not included but making a new SLL connection. That is not consequent I think

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #4 from Vladimir Sitnikov --- The SSL context is not shared across threads, so technically speaking it should be included to "connect time" for properly attributing SSL overheads -- You are receiving this mail be

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #3 from John --- Did some more testing: With jmeter 5.5 and java version 1.8.0_341 the problem is the same. When using jmeter 5.5 and openjdk 18 the problem is still there but the difference between the first en second request

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #2 from John --- I'am using java version "1.8.0_341" -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 --- Comment #1 from John --- Created attachment 38382 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38382=edit jmx -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66248] First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 John changed: What|Removed |Added CC||gls...@gmail.com OS

[Bug 66248] New: First https request is much slower because of Creating threadLocal SSL context

2022-08-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66248 Bug ID: 66248 Summary: First https request is much slower because of Creating threadLocal SSL context Product: JMeter Version: 5.4.3 Hardware: PC Status: NEW

[Bug 66244] Replace terms master/slave

2022-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66244 --- Comment #4 from Philippe Mouawad --- It was done in june 2020: https://github.com/apache/jmeter/commit/1a1984ae3f7ad0abc3745d85d61c811092f429aa So probably released in JMeter 5.4: - https://projects.apache.org/project.html?jmeter

[Bug 66244] Replace terms master/slave

2022-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66244 --- Comment #3 from carlee.fros...@epsilon.com --- In what version were these terms removed from use in JMeter? I'd like to compare it to the version I'm using. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66244] Replace terms master/slave

2022-08-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66244 Philippe Mouawad changed: What|Removed |Added OS||All Status|NEW

[Bug 66244] Replace terms master/slave

2022-08-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66244 --- Comment #1 from carlee.fros...@epsilon.com --- Created attachment 38379 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38379=edit Jmeter's documented use of offensive terms Jmeter's documented use of offensive terms --

[Bug 66244] New: Replace terms master/slave

2022-08-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66244 Bug ID: 66244 Summary: Replace terms master/slave Product: JMeter Version: unspecified Hardware: PC Status: NEW Severity: normal Priority: P2

Bug report for JMeter [2022/08/28]

2022-08-28 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66157] Code Textbox Text Colour

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66157 --- Comment #8 from Brian Tully --- I'm confirming that it is fixed for me as well, on my Mac, with the latest trunk build. Is there any way to use the same rsyntaxtextarea class for the Response Body textarea within View Results Tree? Right

[Bug 65187] Response Body is not formatted correctly (View Results Tree) - use rsyntaxtextarea class?

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65187 --- Comment #16 from Brian Tully --- With the recent fix to Darklaf and rsyntaxtextarea (https://bz.apache.org/bugzilla/show_bug.cgi?id=66157) I'm wondering if the Response Body textarea can be updated to use the rsyntaxtextarea class, so

[Bug 65187] Response Body is not formatted correctly (View Results Tree) - use rsyntaxtextarea class?

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65187 Brian Tully changed: What|Removed |Added Version|5.4.1 |5.5 Summary|Response Body

[Bug 64224] View Results Tree: Response Data->Response Body is illegible with Darcula theme

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64224 Brian Tully changed: What|Removed |Added Status|NEW |RESOLVED OS

[Bug 65187] Response Body is not formatted correctly (View Results Tree) v5.4.1

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65187 --- Comment #15 from Brian Tully --- Can the rsyntaxtextarea class be used for the Response Body textarea, like it is being used for request headers and response headers? -- You are receiving this mail because: You are the assignee

[Bug 66157] Code Textbox Text Colour

2022-08-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66157 --- Comment #7 from Brian Tully --- I had posted several related bugs related to Darklaf and dark themes, where textareas were unreadable due to the dark text against a dark background. In my bug reports I was referring to the textareas within

[Bug 65187] Response Body is not formatted correctly (View Results Tree) v5.4.1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65187 --- Comment #14 from Brian Tully --- Hi again Felix - I'm hoping you might point me in the right direction on how can I contribute to JMeter, especially in relation to the display/formatting of the various fields for the View Results Tree. I

[Bug 66237] Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66237 --- Comment #3 from nathan88w...@gmail.com --- Created attachment 38375 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38375=edit Image showing the issue -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66237] Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66237 nathan88w...@gmail.com changed: What|Removed |Added Attachment #38374|0 |1 is obsolete

[Bug 66237] Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66237 nathan88w...@gmail.com changed: What|Removed |Added OS||All --- Comment #2 from

[Bug 66237] Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66237 --- Comment #1 from nathan88w...@gmail.com --- Created attachment 38374 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38374=edit Showing where Thread issue occurs -- You are receiving this mail because: You are the assig

[Bug 66237] New: Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1

2022-08-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66237 Bug ID: 66237 Summary: Constant Throughput Timer : 0 TPS + shared algorithm + thread lifetime runs all Threads - 1 Product: JMeter Version: 5.5 Hardware: PC

[Bug 66234] New: Chunk file upload with PUT method is failing due to incorrect Content-Length auto calculation

2022-08-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66234 Bug ID: 66234 Summary: Chunk file upload with PUT method is failing due to incorrect Content-Length auto calculation Product: JMeter Version: 5.4.3 Hardware: PC

[Bug 57730] SampleEvent for TransactionSampler: isTransactionSampleEvent return false with parent mode

2022-08-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=57730 --- Comment #3 from Fei Luan --- Please fix this bug. I use 5.4.3 and it is still there. I'm affected by it seriously. An easier way to reproduce this bug: Add a transaction controller with a sampler to script. Then add a Beanshell listener

[Bug 66232] Outdated Doc about ${__time} function.

2022-08-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66232 --- Comment #2 from wangz...@fit2cloud.com --- (In reply to Vladimir Sitnikov from comment #1) > Should we rollback the change for backwardcompatibility then? I think it depends on the reason of this change. If it aims at solving some ot

[Bug 66232] Outdated Doc about ${__time} function.

2022-08-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66232 --- Comment #1 from Vladimir Sitnikov --- Should we rollback the change for backwardcompatibility then? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66232] New: Outdated Doc about ${__time} function.

2022-08-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66232 Bug ID: 66232 Summary: Outdated Doc about ${__time} function. Product: JMeter Version: 5.5 Hardware: All OS: All Status: NEW Severity: normal

Bug report for JMeter [2022/08/21]

2022-08-21 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Bug report for JMeter [2022/08/14]

2022-08-14 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 65318] Incorrect display of decimal numbers in JSON related elements

2022-08-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65318 --- Comment #4 from andreaslin...@gmail.com --- Created attachment 38361 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38361=edit Example testplan for JSON Assertion bug -- You are receiving this mail because: You are the assig

[Bug 65318] Incorrect display of decimal numbers in JSON related elements

2022-08-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65318 --- Comment #3 from andreaslin...@gmail.com --- Hello, I created a PR that should fix the issues with the JSON Assertion: https://github.com/apache/jmeter/pull/723 -- You are receiving this mail because: You are the assignee for the bug.

Bug report for JMeter [2022/08/07]

2022-08-07 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66201] New: Getting error while running JMeter script using Extended CSV Data set config file in Non GUI mode

2022-08-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66201 Bug ID: 66201 Summary: Getting error while running JMeter script using Extended CSV Data set config file in Non GUI mode Product: JMeter Version: 5.4.1 Hardware: PC

[Bug 61697] Introduce Darcula Look And Feel to make JMeter UI more attractive

2022-08-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61697 Vladimir Sitnikov changed: What|Removed |Added Attachment #35554|application/xml |image/png mime type

[Bug 63640] Auto-Correlation as core functionality in JMeter

2022-08-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63640 Michael Johnson changed: What|Removed |Added OS||All --- Comment #1 from Michael

Bug report for JMeter [2022/07/31]

2022-07-31 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66180] private "user defined variable" component scope error

2022-07-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66180 Felix Schumacher changed: What|Removed |Added OS||All Status|NEW

[Bug 66180] New: private "user defined variable" component scope error

2022-07-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66180 Bug ID: 66180 Summary: private "user defined variable" component scope error Product: JMeter Version: 5.5 Hardware: PC Status: NEW Severity: normal

Bug report for JMeter [2022/07/24]

2022-07-24 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #14 from Felix Schumacher --- Thanks for the PR. It looks promising to me. (Must have misunderstood your second comment ;)) I personally think it is a good thing to have dependencies removed, when they are duplicated (we have

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #13 from PJ Fanning --- I have done a PR that is just a POC showing that xalan can probably be removed. https://github.com/apache/jmeter/pull/721 I can continue work on this POC - but I would like to know if it is worthwhile

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #12 from Vladimir Sitnikov --- > Noone benefits from keeping a project alive when there are not enough > maintainers The CVE is trivial to fix, and it would help A LOT of users who depend on xalan today. They will be able t

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #11 from PJ Fanning --- https://lists.apache.org/thread/2qvl7r43wb4t8p9dd9om1bnkssk07sn8 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #10 from PJ Fanning --- Xalan is being putting in the ASF attic. The PMC is inactive. Noone benefits from keeping a project alive when there are not enough maintainers. Java runtime XPath support and Saxon are very valid

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #9 from Vladimir Sitnikov --- I just wonder: is xalan-j really that bad? What if we just fix the CVE in question and release a newer Xalan version? Then **everybody** would benefit from that. -- You are receiving this mail

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #8 from PJ Fanning --- https://docs.oracle.com/javase/9/docs/api/javax/xml/xpath/XPath.html#evaluateExpression-java.lang.String-org.xml.sax.InputSource- was only added in Java 9 but would do exactly what you need - see https

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #7 from Felix Schumacher --- Another problem I found, is that we guess the return of xpath expressions. The standard XPath api has no such capability. At least, I haven't found it yet. Such guessing takes place in XPathUtil

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #6 from Felix Schumacher --- I tried to get rid of the xalan dependency by removing it from the usual places in the gradle files, but it seems that other libraries build steps (ant?) have dependencies on them and bring xalan back

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #5 from PJ Fanning --- Without xalan, it looks like XPathUtil would need to be rewritten - the 3 imports starting with https://github.com/apache/jmeter/blob/master/src/core/src/main/java/org/apache/jmeter/util/XPathUtil.java#L52

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #4 from Vladimir Sitnikov --- We have public class PropertiesBasedPrefixResolver extends org.apache.xml.utils.PrefixResolverDefault, so we have non-trivial usage of xalan. It does not sound like "just remove runtime

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 Felix Schumacher changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #3 from Felix

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 --- Comment #2 from PJ Fanning --- I'm a member of the ASF Security committee and I'm just trying to nudge PMCs to keep their dependencies up to date. I do a lot of PRs for ASF teams but I'm getting to the stage where I'm getting a bit fed up

[Bug 66171] remove xalan dependency due to it being end of life

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 Felix Schumacher changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Felix

[Bug 66172] NOT Able to End the Test and Generate Report after One Hour Execution in NON GUI Mode

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66172 Felix Schumacher changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Felix

[Bug 66172] New: NOT Able to End the Test and Generate Report after One Hour Execution in NON GUI Mode

2022-07-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66172 Bug ID: 66172 Summary: NOT Able to End the Test and Generate Report after One Hour Execution in NON GUI Mode Product: JMeter Version: 5.4.1 Hardware: PC

[Bug 66171] New: remove xalan dependency due to it being end of life

2022-07-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66171 Bug ID: 66171 Summary: remove xalan dependency due to it being end of life Product: JMeter Version: 5.5 Hardware: All OS: All Status: NEW Severity

Bug report for JMeter [2022/07/17]

2022-07-17 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 65782] While using JMeter's Html Assertion I m getting an error failure message - html assertion: can't parse argument number

2022-07-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65782 --- Comment #4 from Felix Schumacher --- Have you tried the current JMeter 5.5? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 65782] While using JMeter's Html Assertion I m getting an error failure message - html assertion: can't parse argument number

2022-07-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65782 --- Comment #3 from Sonu Mahajan --- When checking the Assertion results, for HTML Assertion, using the Site WWW,google.com getting this basic issue And have checked on every browser version 5.3, 5.4 -- You are receiving this mail because

[Bug 66140] Report generation fails

2022-07-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 --- Comment #13 from Felix Schumacher --- https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/lastSuccessfulBuild/artifact/src/dist/build/distributions/ -- You are receiving this mail because: You are the assignee for the bug.

[Bug 66140] Report generation fails

2022-07-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 --- Comment #12 from Frederic Girard --- Hello, "one of the next builds from trunk" Please where can I find them ? -- You are receiving this mail because: You are the assignee for the bug.

Bug report for JMeter [2022/07/10]

2022-07-10 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66140] Report generation fails

2022-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 --- Comment #11 from Felix Schumacher --- commit 157db3679a5ed14e97f4b7dd59f29b395217cd48 AuthorDate: Sat Jul 9 14:48:17 2022 +0200 Make failing tests run again and add more tests Bugzilla Id: 66140 --- .../apache/jmeter/report/core

[Bug 66140] Report generation fails

2022-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 Felix Schumacher changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #10 from

[Bug 66165] Not able to publish data to IOT hub

2022-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66165 Felix Schumacher changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution

[Bug 66165] Not able to publish data to IOT hub

2022-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66165 --- Comment #2 from Ranjith --- Yes, i used third party MQTT plugin. Is there any other way to perform load test IOT hub using mqtt protocol? Thanks and Regards Ranjithkumar P -- You are receiving this mail because: You are the assignee

[Bug 66165] Not able to publish data to IOT hub

2022-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66165 Felix Schumacher changed: What|Removed |Added Status|NEW |NEEDINFO OS

[Bug 66140] Report generation fails

2022-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 Felix Schumacher changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #9 from Felix

[Bug 66140] Report generation fails

2022-07-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66140 --- Comment #8 from Felix Schumacher --- Created attachment 38337 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38337=edit Simple test file to reproduce error message When the separator doesn't match the fields in the header, we

  1   2   3   4   5   6   7   8   9   10   >