java.lang.IllegalStateException: Transaction already active

最新推荐文章于 2025-04-29 20:31:28 发布
最新推荐文章于 2025-04-29 20:31:28 发布
阅读量8.6k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： Webservice
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/zwp2014/article/details/40782831
本文讨论了在处理WebService中的客户端时遇到的事务重复开启错误，并提供了详细的解决方案，包括错误分析、原因解释及代码修改建议。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

在处理webservice中的客户端时出现如下错误：

log4j:WARN No appenders could be found for logger (org.hibernate.cfg.annotations.Version).

log4j:WARN Please initialize the log4j system properly.
java.lang.IllegalStateException: Transaction already active
at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:35)
at com.mana.Entity.EntityManagerHelper.beginTransaction(EntityManagerHelper.java:42)
at com.mana.dao.impl.BreedersscoresDaoWsImpl.save_breedersscores(BreedersscoresDaoWsImpl.java:10)
at com.mana.operation.WSImpl.save(WSImpl.java:18)
at com.mana.test.Test.main(Test.java:14)

error

原因：Test文件中事务被重复开启了。

解决办法：仔细查找文件，发现BreedersscoresDaoWsImpl已经有过事务的相关处理过，所以只需将Test中的事务处理取消掉就可以。

kakfa 常见错误（长期更新 2023.09.05）
一起学习一起进步~
06-19 2136
我们只需要在消费者配置中设置一个即可，这个错误的原因是未设置group id，但又使用了subscribe(topic) 或基于 Kafka 的偏移量管理策略使用组管理功能引起。若不清楚group id请显示的指定分区，避免将错误的group id写入。springboot启动后连接kafka集群报错：协调器不正确，标记协调器未知。springboot指定消费者群组：消费者配置类添加下面代码（消费者配置类可查看。指定消费者群组进行消费，成功消费后将自动创建所指定的消费者群组。
Android进阶之路 - 异常汇总
Android、前端、小程序、后端
12-28 1135
后续工作中，持续更新。 1.Error:null value in entry: annotationProcessorOutputFolder=null（条目中的空值） 通用解决方案 删除根目录下的 .gradle文件，之后重新编译使用 2.android.view.WindowManager$BadTokenException: Unable to add window – to...
Transaction already active
在路上
05-30 499
还ibernate,java,后端开发,开发
transaction already active
wang1144的专栏
08-16 6326
这个问题是使用spring 事务管理时经常出现的错误，最开始时相当令我头疼，也不知道是哪里出现的问题。在网上找了一阵后，依然无解。意思就是说上一个事务处于激活状态中，不能开始新的数据库更新操作。   开始事务的方法一般是这样的： EntityTransaction txn = slavesDao.startTransaction();    try {     ...     //sl
as not registered for synchronization because synchronization is not active错误
BYXhy的博客
04-29 501
as not registered for synchronization because synchronization is not active这个错误是在JOSN格式的数据封装到实体类中没有加RequestBody注解。
[FATAL_ERROR] Uncaught PDOException: There is already an active transaction
weixin_30660027的博客
06-06 1148
[FATAL_ERROR] Uncaught PDOException: There is already an active transaction 。。。 $mysql->beginTransaction(); 出现这个错误就是事务嵌套了。意思就是本来一段代码中已经开启了事务处理， 然后在这段代码中又写多了一个事务，同时开启了两个事务处理就会冲突。 转载于:https:/...
记 PDO报 There is already an active transaction 报错
新一的博客
03-01 4977
代码大概逻辑如下： Db::beginTransaction(); $update //更新操作 $add //新增操作 if(! $add && $update===false){ Db::rollback(); }else{ Db::commit(); } 查看日志，在add时有一条数据异常，导致新增失败 后面就一直报 There is ...
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) ~[na:na] at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.apache.catalina.startup.Tomcat.start(Tomcat.java:467) ~[tomcat-embed-core-9.0.31.jar!/:9.0.31] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:107) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.<init>(TomcatWebServer.java:88) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getTomcatWebServer(TomcatServletWebServerFactory.java:438) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getWebServer(TomcatServletWebServerFactory.java:191) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:180) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:153) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:544) ~[spring-context-5.2.4.RELEASE.jar!/:5.2.4.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.5.RELEASE.jar!/:2.2.5.RELEASE] at com.cn.travel.TravelApplication.main(TravelApplication.java:16) ~[classes!/:0.0.1-SNAPSHOT] at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[na:na] at java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na] at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) ~[travel-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) ~[travel-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) ~[travel-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) ~[travel-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] Caused by: java.lang.IllegalStateException: Not a file URL at org.springframework.boot.loader.jar.Handler.getRootJarFile(Handler.java:304) ~[travel-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT] ... 58 common frames omitted 2025-07-10 04:43:26.009 INFO 26542 --- [ main] org.apache.jasper.servlet.TldScanner : At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 2025-07-10 04:43:26.012 INFO 26542 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-07-10 04:43:26.012 INFO 26542 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 1442 ms 2025-07-10 04:43:26.070 INFO 26542 --- [ main] c.a.d.s.b.a.DruidDataSourceAutoConfigure : Init DruidDataSource 2025-07-10 04:43:26.258 INFO 26542 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} inited 2025-07-10 04:43:26.368 INFO 26542 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default] 2025-07-10 04:43:26.468 INFO 26542 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 5.4.12.Final 2025-07-10 04:43:26.607 INFO 26542 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final} 2025-07-10 04:43:26.789 INFO 26542 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.MariaDB103Dialect 2025-07-10 04:43:26.819 WARN 26542 --- [ main] o.h.e.j.e.i.JdbcEnvironmentInitiator : HHH000341: Could not obtain connection metadata : Unknown column 'RESERVED' in 'WHERE' 2025-07-10 04:43:26.819 INFO 26542 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.MariaDB103Dialect 2025-07-10 04:43:26.986 INFO 26542 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform] 2025-07-10 04:43:26.990 INFO 26542 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2025-07-10 04:43:27.624 WARN 26542 --- [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning MyBatisConfiguration.pageHelper() 2025-07-10 04:43:27.806 INFO 26542 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor' 2025-07-10 04:43:27.887 INFO 26542 --- [ main] o.s.b.a.w.s.WelcomePageHandlerMapping : Adding welcome page template: index 2025-07-10 04:43:27.933 WARN 26542 --- [ main] org.thymeleaf.templatemode.TemplateMode : [THYMELEAF][main] Template Mode 'LEGACYHTML5' is deprecated. Using Template Mode 'HTML' instead. 2025-07-10 04:43:27.958 INFO 26542 --- [ main] t.m.m.autoconfigure.MapperCacheDisabler : Clear tk.mybatis.mapper.util.MsUtil CLASS_CACHE cache. 2025-07-10 04:43:27.959 INFO 26542 --- [ main] t.m.m.autoconfigure.MapperCacheDisabler : Clear tk.mybatis.mapper.genid.GenIdUtil CACHE cache. 2025-07-10 04:43:27.960 INFO 26542 --- [ main] t.m.m.autoconfigure.MapperCacheDisabler : Clear tk.mybatis.mapper.version.VersionUtil CACHE cache. 2025-07-10 04:43:27.960 INFO 26542 --- [ main] t.m.m.autoconfigure.MapperCacheDisabler : Clear EntityHelper entityTableMap cache. 2025-07-10 04:43:28.068 INFO 26542 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2025-07-10 04:43:28.090 INFO 26542 --- [ main] ConditionEvaluationReportLoggingListener : Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled. 2025-07-10 04:43:28.092 ERROR 26542 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPLICATION FAILED TO START *************************** Description: Web server failed to start. Port 80 was already in use. Action: Identify and stop the process that's listening on port 80 or configure this application to listen on another port. 2025-07-10 04:43:28.094 INFO 26542 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Shutting down ExecutorService 'applicationTaskExecutor' 2025-07-10 04:43:28.095 INFO 26542 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default' 2025-07-10 04:43:28.096 INFO 26542 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} closing ... 2025-07-10 04:43:28.101 INFO 26542 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} closed ┌──(kali㉿kali)-[/mnt/hgfs/shiyansucai] └─$ sudo systemctl status mariadb ● mariadb.service - MariaDB 11.8.2 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; preset: disabled) Active: active (running) since Thu 2025-07-10 03:52:33 EDT; 51min ago Invocation: 0e8e759073774f3db4beb277c6a197b5 Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Main PID: 1079 (mariadbd) Status: "Taking your SQL requests now..." Tasks: 11 (limit: 14518) Memory: 161M (peak: 162.7M, swap: 4K, swap peak: 4K) CPU: 2.785s CGroup: /system.slice/mariadb.service └─1079 /usr/sbin/mariadbd Jul 10 03:52:32 kali mariadbd[1079]: 2025-07-10 3:52:32 0 [Note] Plugin 'wsrep-provider' is disabled. Jul 10 03:52:32 kali mariadbd[1079]: 2025-07-10 3:52:32 0 [Note] Recovering after a crash using tc.log Jul 10 03:52:32 kali mariadbd[1079]: 2025-07-10 3:52:32 0 [Note] Starting table crash recovery... Jul 10 03:52:32 kali mariadbd[1079]: 2025-07-10 3:52:32 0 [Note] Crash table recovery finished. Jul 10 03:52:32 kali mariadbd[1079]: 2025-07-10 3:52:32 0 [Note] InnoDB: Buffer pool(s) load completed at 25> Jul 10 03:52:33 kali mariadbd[1079]: 2025-07-10 3:52:33 0 [Note] Server socket created on IP: '127.0.0.1'. Jul 10 03:52:33 kali mariadbd[1079]: 2025-07-10 3:52:33 0 [Note] mariadbd: Event Scheduler: Loaded 0 events Jul 10 03:52:33 kali mariadbd[1079]: 2025-07-10 3:52:33 0 [Note] /usr/sbin/mariadbd: ready for connections. Jul 10 03:52:33 kali mariadbd[1079]: Version: '11.8.2-MariaDB-1 from Debian' socket: '/run/mysqld/mysqld.soc> Jul 10 03:52:33 kali systemd[1]: Started mariadb.service - MariaDB 11.8.2 database server. ┌──(kali㉿kali)-[/mnt/hgfs/shiyansucai] └─$ mysql -u root -p123456 -h 127.0.0.1 travel_db -e "SELECT 1;" +---+ | 1 | +---+ | 1 | +---+ ┌──(kali㉿kali)-[/mnt/hgfs/shiyansucai] └─$ tail -f /mnt/hgfs/shiyansucai/logs/application.log tail: cannot open '/mnt/hgfs/shiyansucai
最新发布
07-11
他们可能对Linux系统有一定了解，但在Java或Spring Boot配置上可能需要更具体的指导。用户可能没有提到他们是否已经尝试更改端口号，或者是否检查了其他服务是否占用了端口80。 我需要分步骤解决这两个主要问题：...
Spring：事务处理的实现
qq_40623110的博客
09-03 636
事务处理的实现 Spring在对事务进行统一处理其实底层还是使用到了aop，TransactionProxyFactoryBean将对事务的处理事件使用aop做增强和织入。对数据源的事务处理（提交、回滚）的实现是通过事务管理器TransactionManager来进行支持的。通过TransactionAspectSupport来赋予TransactionManager的事务处理可以通过aop进行操作。 [外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-cRDeUXmk-1599
AndroidX Fragment探究-状态保存和恢复
chidh的博客
03-28 2872
文章目录概述源码探究状态保存状态恢复commit & commitAllowingStateLoss总结 概述 我们知道Activity提供了onSaveInstanceState和onRestoreInstanceState回调方法用于状态保存和恢复，同样FragmentActivity和Fragment也支持状态保存和恢复，FragmentActivity会在适当的时机，通过Fragm...
java.lang.IllegalStateException: commit already called
八戒卖萌的博客
06-12 380
java.lang.IllegalStateException: commit already called Fragment  在互相切换时候 会报这样的错误，如果在你一个类中已经使用一个成员变量transaction去调用了一次commit()方法，那么在其它外部类中就不能再使用一个成员变量transaction再次调用commit()方法就会提示你 已经用过啦，我的我的情景
java.lang.IllegalStateException: Fragment already active
火星男孩的分享空间
08-28 1597
activity的onresume中 Bundle bundleOffice = new Bundle(); bundleOffice.putSerializable("officeMsg", officeMsg); mFragOffice.setArguments(bundleOffice);setArguments报错： Caused by: java.lang.IllegalSt
解决Caused by: java.lang.IllegalStateException:
热门推荐
牛肉胡辣汤
11-02 1万+
通过调整JVM的-Xss参数、检查循环继承依赖项和更新相关库和依赖，我们可以解决​​Caused by: java.lang.IllegalStateException: 由于StackOverflower错误无法完成对web应用程序[/lib]的批注的扫描​​异常。在解决这个问题时，我们需要对应用程序的结构和依赖进行深入的分析和调试，以确定根本原因并采取相应的措施。当我们开发Web应用程序时，有时候会遇到上述的​​异常。
IllegalTransactionStateException（非法事务状态异常）可能的原因和解决方法
Java开源程序猿
12-30 1570
尝试在没有激活的事务上下文中执行事务操作，例如在没有事务注解或事务配置的情况下执行事务相关操作。在一些框架或环境中，尝试在不同类型的事务（如本地事务和全局事务）之间进行操作可能导致异常。尝试在不允许的情况下进行事务状态转换，例如在一个没有激活事务的环境中执行提交或回滚操作。如果尝试在一个事务中嵌套另一个事务，但是事务管理器不支持所需的嵌套级别，可能会导致异常。事务管理器的配置可能不正确，导致在不合适的情况下执行了事务相关的操作。可能存在多个事务并发执行，导致某些事务操作在不正确的事务状态下执行。
已解决：java.lang.IllegalStateException 异常解决合集
猿鹏探码的博客
08-21 1636
异常通常表示对象当前的状态不符合要求。在处理这种异常时，需要检查操作的状态、资源的使用情况、事务的管理等。通过仔细分析异常信息，确保方法调用顺序正确，并在适当的状态下进行操作，可以有效解决此类问题。通过与开发者社区和团队的协作，可以快速找到问题的根本原因并提出解决方案。
几天几夜了，终于解决了
run的博客
05-23 1833
首先亮一下自己遇到的奇葩错误：Exception in thread "main" java.lang.IllegalStateException: Transaction already active    at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:52)    ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值