Eclipselink generating sequence twice which is unexcepted [message #1861518] |
Tue, 17 October 2023 07:24 |
Sanjana C Messages: 31 Registered: December 2022 |
Member |
|
|
Hi Team,
I am using eclipselink 2.7.6 with weblogic 12c.
When i run a insert operation which follows generating sequence, i see eclipselink generats sequence twice.
[EL Fine]: sql: 2023-10-17 08:59:21.434--ClientSession(1507239121)--Connection(1104718965)--Thread(Thread[main,5,main])--SELECT BAS_SEQ.NEXTVAL FROM DUAL
[EL Fine]: sql: 2023-10-17 08:59:21.455--ClientSession(1507239121)--Connection(1104718965)--Thread(Thread[main,5,main])--SELECT SAM_SEQ.NEXTVAL FROM DUAL
[EL Fine]: sql: 2023-10-17 08:59:21.472--ClientSession(1507239121)--Connection(1104718965)--Thread(Thread[main,5,main])--SELECT MIG_SEQ.NEXTVAL FROM DUAL
[EL Fine]: sql: 2023-10-17 08:59:21.489--ClientSession(1507239121)--Connection(1104718965)--Thread(Thread[main,5,main])--SELECT MIG_SEQ.NEXTVAL FROM DUAL
[EL Fine]: sql: 2023-10-17 08:59:21.512--ClientSession(1507239121)--Connection(1104718965)--Thread(Thread[main,5,main])--SELECT SYSDATE FROM DUAL
In above log , MIG_SEQ is generated twice. So record is inserted with id 1 and later when i search for record , it just takes latest sequence i.e 2 and throws error saying no record available.
Below is persistence.xml
<properties>
<property name="eclipselink.logging.level" value="ALL" />
<property name="eclipselink.logging.level.sql" value="ALL"/>
<property name="eclipselink.logging.parameters" value="true" />
<property name="eclipselink.logging.logger" value="DefaultLogger"/>
<property name="eclipselink.jdbc.bind-paramaters" value="true" />
<property name="eclipselink.target-database" value="Oracle" />
<property name="eclipselink.persistence-context.flush-mode" value="commit" />
<property name="eclipselink.persistence-context.reference-mode" value="WEAK" />
<property name="eclipselink.weaving" value="static" />
<property name="eclipselink.jdbc.exclusive-connection.mode" value="Always" />
<property name="eclipselink.sessions-xml" value="sessions.xml" />
<property name="eclipselink.session-name" value="default" />
</properties>
sessions.xml
<session xsi:type="server-session">
<name></name>
<logging xsi:type="server-log"></logging>
<primary-project xsi:type="xml"></primary-project>
<additional-project xsi:type="xml"></additional-project>
<login xsi:type="database-login">
<platform-class>org.eclipse.persistence.platform.database.oracle.Oracle10Platform</platform-class>
<!-- usage of external connect information - uses the spring toplink transaction manager -->
<external-connection-pooling>true</external-connection-pooling>
<external-transaction-controller>true</external-transaction-controller>
<sequencing>
<default-sequence xsi:type="native-sequence">
<name>Native</name>
<preallocation-size>1</preallocation-size>
</default-sequence>
</sequencing>
</login>
<connection-policy>
<exclusive-connection>true</exclusive-connection>
<lazy>false</lazy>
</connection-policy>
</session>
I tried disabling the weaving but still can see the duplicate sequence generated . I see there was a bug in 2.5 eclipselink version but iam using 2.7.6
Please let me know if any one faced or resolved this issue.
Thanks,
Sanjana
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04043 seconds