-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With simple performance load get: java.lang.IllegalStateException: No MssqlRowMetadata #160
Comments
Thanks for the report. I wasn't able to reproduce the mentioned issue, neither locally nor using Azure SQL Servers. |
Have been able to reproduce with more simple service with JMeter. So will push example to github shortly with how to reproduce. |
Ok posted my example code here. https://github.com/ravredd/test-spring-r2dbc-mssql The README has instructions. It is a very simple spring app with not a lot to it. two columns in a db. I cannot get this to fail when running service locally. Only when deployed to Azure. I even tried given my container locally the minimum cpu, memory etc. And tried different max pooling settings. No change in result. In Azure it fails but locally passes. Uses Azure App Service on S1-1 plan. Nothing special on the Azure SQL Server side. |
I tried to reproduce the issue with no luck. Can you
|
My team also encountered this strange issue as well. Our project setup is on SpringBoot 2.3.4, WebFlux, r2dbc-mssql. Our database instance is running on MSSQL 2017 After deploying our app to our on-premise kubernetes cluster we started experiencing this issue of the database result getting mixed up. This never happen on our local machine. To share, we proceeded to upgrade our SpringBoot to the latest stable 2.4.4, unfortunately the issue still persist. In the spirit to achieve not blocking IO, we are switching to reactive mongo which seems to be a more mature in this reactive community, hope that this issue with MS SQL driver can be resolved in the future. |
Yeah this is what we are telling all our teams to move away from azure
mssql. R2dbc for it is not production ready.
…On Thu, Apr 15, 2021 at 8:45 AM levi85 ***@***.***> wrote:
My team also encountered this strange issue as well. Our project setup is
on SpringBoot 2.3.4, WebFlux, r2dbc-mssql. Our database instance is running
on MSSQL 2017
After deploying our app to our on-premise kubernetes cluster we started
experiencing this issue of the database result getting mixed up. This never
happen on our local machine.
To share, we proceeded to upgrade our SpringBoot to the latest stable
2.4.4, unfortunately the issue still persist. In the spirit to achieve not
blocking IO, we are switching to reactive mongo which seems to be a more
mature in this reactive community, hope that this issue with MS SQL driver
can be resolved in the future.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZPLOYKSJ4HV7DVBOTHBTTI3UYFANCNFSM4OLKYTBQ>
.
|
Part of the problem is that we're not able to reproduce the issue. Without that, it's next to impossible to diagnose the problem. |
It happened to our team as well, sporadically on our cheap build server in Azure (Standard_F4s_v2). We changed to a faster machine (Standard_D8s_v3), and it has not happened since. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Please refrain from posting further stack traces without providing a reproducer. Thank you. |
I had the same problem running my Application (Spring Boot 2.6.2, r2dbc-mssql 0.8.7.RELEASE, Java 17). The problem occurred only on Azure App Service (B1). On the local environment, everything was perfect. But I have added to url parameter |
Bug Report
Versions
Current Behavior
Essentially copied https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/configure-spring-data-r2dbc-with-azure-sql-server
Changed from TODOs to Mandates for my purpose. There is only a post and a get controller as the todo example. Only difference is the word todo to mandate
See stack trace below. This happens almost immediately when tests start using jmeter
Stack trace
Table schema
Input Code
On post mandateRepository.save(mandate); -- ReactiveCrudRepositoryOn get
mandateRepository.findAll();
-- your SQL here; Using base ReactiveCrudRepository
Steps to reproduce
You can use the todo example, deploy as docker container to Azure app service, connected to azure sql server db. Run JMeter with 25 concurrent users, 10 cycles, 1 post and 1 get on each. Error will begin showing.
Java spring boot as reference TODO example
Input Code
// your code here;
Expected behavior/code
No exception nor failed requests.
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: