{"id":87,"date":"2026-10-05T16:45:00","date_gmt":"2026-10-05T16:45:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/05\/spring-transactional-pitfalls\/"},"modified":"2026-10-05T16:45:00","modified_gmt":"2026-10-05T16:45:00","slug":"spring-transactional-pitfalls","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/05\/spring-transactional-pitfalls\/","title":{"rendered":"@Transactional Neden \u00c7al\u0131\u015fmad\u0131? Spring&#8217;de S\u0131k Yap\u0131lan Hatalar"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Spring&#8217;de transaction y\u00f6netimi o kadar kolay ki \u00e7o\u011fu zaman \u00fczerinde d\u00fc\u015f\u00fcn\u00fclm\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Metodun \u00fcst\u00fcne bir anotasyon eklenir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Transactional\npublic void transfer(...) { ... }<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ve transaction y\u00f6netimi halledilmi\u015f kabul edilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ta ki production&#8217;da yar\u0131m kalm\u0131\u015f bir i\u015flemin verisi g\u00f6r\u00fclene kadar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Proxy her \u015feyi a\u00e7\u0131kl\u0131yor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><code>@Transactional<\/code> sihirli de\u011fil. Spring, bean&#8217;in etraf\u0131na bir proxy koyar. D\u0131\u015far\u0131dan gelen \u00e7a\u011fr\u0131 \u00f6nce proxy&#8217;ye ula\u015f\u0131r. Proxy transaction&#8217;\u0131 ba\u015flat\u0131r, ger\u00e7ek metodu \u00e7a\u011f\u0131r\u0131r, sonra commit veya rollback yapar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu tek c\u00fcmle, transaction ile ilgili s\u00fcrprizlerin \u00e7o\u011funu a\u00e7\u0131kl\u0131yor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Self-invocation<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>@Service\npublic class OrderService {\n\n    public void placeAll(List&lt;Order&gt; orders) {\n        for (Order o : orders) {\n            place(o);\n        }\n    }\n\n    @Transactional\n    public void place(Order o) { ... }\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>place<\/code> metodu <code>@Transactional<\/code>. Ama <code>placeAll<\/code> i\u00e7inden <code>this.place()<\/code> olarak \u00e7a\u011fr\u0131l\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu \u00e7a\u011fr\u0131 proxy&#8217;den ge\u00e7mez. Do\u011frudan nesnenin kendisine gider.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sonu\u00e7: transaction hi\u00e7 ba\u015flamaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7\u00f6z\u00fcm, transaction s\u0131n\u0131r\u0131n\u0131 d\u0131\u015far\u0131dan \u00e7a\u011fr\u0131lan metoda ta\u015f\u0131mak veya transaction&#8217;l\u0131 metodu ayr\u0131 bir bean&#8217;e ay\u0131rmakt\u0131r. \u0130kincisi genellikle tasar\u0131m a\u00e7\u0131s\u0131ndan da daha temiz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Private metotlar<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ayn\u0131 sebeple <code>private<\/code> metotlara konan <code>@Transactional<\/code> etkisizdir. Proxy bu metotlar\u0131 g\u00f6remez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring 6 ile birlikte proxy tabanl\u0131 yap\u0131larda <code>protected<\/code> ve package-private metotlar da desteklenmeye ba\u015fland\u0131. Ama <code>private<\/code> h\u00e2l\u00e2 \u00e7al\u0131\u015fm\u0131yor ve IDE&#8217;ler bu konuda her zaman uyar\u0131 vermiyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Checked exception rollback yapmaz<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu muhtemelen en \u015fa\u015f\u0131rt\u0131c\u0131 olan\u0131:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Transactional\npublic void importFile(...) throws IOException {\n    repository.save(header);\n    parseLines(...);   \/\/ IOException f\u0131rlat\u0131yor\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>IOException<\/code> f\u0131rlat\u0131ld\u0131\u011f\u0131nda <code>header<\/code> kayd\u0131 rollback olmaz. Commit edilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Spring varsay\u0131lan olarak sadece <code>RuntimeException<\/code> ve <code>Error<\/code> i\u00e7in rollback yapar. Checked exception&#8217;lar i\u00e7in transaction commit edilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu, EJB d\u00f6neminden kalan bir kural. Checked exception&#8217;\u0131n i\u015f ak\u0131\u015f\u0131n\u0131n beklenen bir par\u00e7as\u0131 oldu\u011fu varsay\u0131l\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Davran\u0131\u015f\u0131 de\u011fi\u015ftirmek i\u00e7in a\u00e7\u0131k\u00e7a belirtmek gerekir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Transactional(rollbackFor = Exception.class)<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Exception&#8217;\u0131 yutmak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir ba\u015fka yayg\u0131n durum:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Transactional\npublic void process() {\n    try {\n        paymentService.charge(...);\n    } catch (Exception e) {\n        log.error(\"charge failed\", e);\n    }\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>paymentService.charge<\/code> da <code>@Transactional<\/code> ise ve i\u00e7inde exception olu\u015ftuysa, i\u00e7 transaction mevcut transaction&#8217;\u0131 rollback-only olarak i\u015faretler. D\u0131\u015f metot exception&#8217;\u0131 yakalad\u0131 ve normal \u015fekilde bitti.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Commit an\u0131nda \u015fu hata gelir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>UnexpectedRollbackException:\nTransaction silently rolled back because it has been marked as rollback-only<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Geli\u015ftirici hatay\u0131 yakalad\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcn\u00fcyordu. Ama transaction \u00e7oktan geri al\u0131nmak \u00fczere i\u015faretlenmi\u015fti.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Transaction i\u00e7inde d\u0131\u015f \u00e7a\u011fr\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Teknik olarak hata de\u011fil ama production&#8217;da en \u00e7ok problem \u00e7\u0131karan kal\u0131p bu:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Transactional\npublic void checkout(...) {\n    orderRepository.save(order);\n    paymentGateway.charge(order);   \/\/ 2-3 saniye\n    notificationClient.send(order); \/\/ 500 ms\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Transaction a\u00e7\u0131k oldu\u011fu s\u00fcrece bir veritaban\u0131 connection&#8217;\u0131 tutulur ve lock&#8217;lar bekler.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">D\u0131\u015f servis yava\u015flad\u0131\u011f\u0131nda connection pool h\u0131zla t\u00fckenir. \u00dcstelik \u00f6deme ba\u015far\u0131l\u0131 olup sonra transaction rollback olursa, para \u00e7ekilmi\u015f ama sipari\u015f kaydedilmemi\u015f olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">D\u0131\u015f \u00e7a\u011fr\u0131lar\u0131 transaction d\u0131\u015f\u0131na almak, transaction&#8217;lar\u0131 k\u0131sa tutmak ve gerekirse outbox ile sonraya b\u0131rakmak daha g\u00fcvenli bir yap\u0131 olu\u015fturur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">readOnly ne yapar?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><code>@Transactional(readOnly = true)<\/code> bir performans ipucudur. Hibernate dirty checking yapmaz, baz\u0131 driver&#8217;lar sorgular\u0131 read replica&#8217;ya y\u00f6nlendirebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama yazma i\u015flemini her ortamda engelleyece\u011finin garantisi yoktur. Bir g\u00fcvenlik mekanizmas\u0131 olarak de\u011fil, optimizasyon olarak d\u00fc\u015f\u00fcn\u00fclmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>@Transactional<\/code> bir anotasyon olarak basit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama arkas\u0131ndaki davran\u0131\u015f\u0131 bilmeden kullan\u0131ld\u0131\u011f\u0131nda, en zor fark edilen veri tutarl\u0131l\u0131\u011f\u0131 hatalar\u0131n\u0131n kayna\u011f\u0131 oluyor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Anotasyon orada ama rollback olmuyor. Self-invocation, checked exception, private metot ve transaction i\u00e7inde d\u0131\u015f servis \u00e7a\u011fr\u0131s\u0131 gibi Spring&#8217;de s\u0131k g\u00f6r\u00fclen tuzaklar.<\/p>\n","protected":false},"author":1,"featured_media":86,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-87","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mimari"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/87","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=87"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/87\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/86"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=87"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=87"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=87"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}