Bug 961290 - PSQLException: Large Objects may not be used in auto-commit mode
Summary: PSQLException: Large Objects may not be used in auto-commit mode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Edson Tirelli
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-09 11:07 UTC by Jiri Locker
Modified: 2013-05-09 15:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
PostgreSQL 9.2
Last Closed: 2013-05-09 15:00:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
server.log (63.76 KB, text/plain)
2013-05-09 11:07 UTC, Jiri Locker 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 852044 0 unspecified VERIFIED Cannot view human task list on EAP 6.0 with Hibernate 4 and PostgreSQL due to: org.postgresql.util.PSQLException: Large ... 2023-05-15 19:53:43 UTC

Internal Links: 852044

Description Jiri Locker 2013-05-09 11:07:46 UTC 
Created attachment 745613 [details]
server.log

Description of problem:
kie-ide fails to deploy due to this exception when persistence is configured with PostgreSQL datasource.

Version-Release number of selected component (if applicable):
DR4

Steps to Reproduce:
1. setup pgsql datasource on eap 6.1
2. change kie-ide.war/<...>/persistence.xml to use pgsql datasource
3. start the server
  
Additional info:
See attached server.log for full exception trace.
Comment 1 Jiri Locker 2013-05-09 11:12:49 UTC 
Similar issue with LOBs and PostgreSQL has been fixed for 5.3: bug 852044.
Comment 2 Jiri Locker 2013-05-09 12:00:29 UTC 
Probably error in my configuration. When creating datasource in EAP admin console jta attribute of the datsource defaults to true. I didn't check this. Setting jta="true" avoids the exception an kie-ide deploys OK.

Please close as not a bug if this behavior is correct.
Comment 3 Jiri Locker 2013-05-09 12:02:04 UTC 
> defaults to true
should be "defaults to false"
Note You need to log in before you can comment on or make changes to this bug.