You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/05/07 03:02:17 UTC

[GitHub] [shardingsphere] King1031 opened a new issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

King1031 opened a new issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453


   Caused by: org.hibernate.TransactionException: Already have an associated managed connection
   ![image](https://user-images.githubusercontent.com/32608606/81249815-2aeb4080-9052-11ea-8cba-d6da415dd95e.png)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] terrymanu commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-630084792


   Closed because no response anymore


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] kimmking commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
kimmking commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-625023195


   I guess we can't support hot-reload for hibernate now. Hibernate hold a connection by itself that sharding-jdbc can't control. So when sharding-jdbc reload and renew all connections with ds, those hold by hibernate is still the older ones.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] King1031 commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
King1031 commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-625019014


   full stack here:
   [stack.txt](https://github.com/apache/shardingsphere/files/4590660/stack.txt)
   
   we used default type of transaction like this:
   ![企业微信截图_1588824591814](https://user-images.githubusercontent.com/32608606/81253715-c59c4d00-905b-11ea-8c6b-e6cee0800d5d.png)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] cherrylzhao commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
cherrylzhao commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-625002949


   please show the full stack trace, and what type of transaction you have used? 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] King1031 commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
King1031 commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-625030650


   if I switch to version 4.0.1 it works normally


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] cherrylzhao commented on issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
cherrylzhao commented on issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453#issuecomment-625123308


   I have tested `sharding-spring-boot-jpa-example`, it's ok.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere] terrymanu closed issue #5453: After source code changed in spring boot, hot reload thow exception, sharding-sphere upgrade from 4.0.1 to 4.1.0

Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #5453:
URL: https://github.com/apache/shardingsphere/issues/5453


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org