Daniel Jabonete

Hi Fritz,

I had tried your implementation codes and steps to hit the exception. I ran these codes in a web setting using two browsers with respective Session ID.

Although, I was able to lock the entity and the other user wait until the first user commits his changes, it seems there were different exceptions with each scenarios, especially when the lock expires. I encountered “javax.transaction.NotSupportedException: Nested Transactions are not supported” and “java.lang.IllegalMonitorStateException”, that I believed can be treated easily, hence based on these tests the “PessimisticLockException” seems not that easy to get around and can be thrown as an explicit exception, as we intended it to be.

I will still try and search a couple of resolutions in order to attain a much direct or straight-forward approach, and will post it here.

My apologies for my late response to this post.

If you guys still have other ideas or codes that you would like to show or share in relation to this topic/subject, please don’t hesitate to post it here.

Thanks very much!

Cheers!
Daniel

Hi Rafael,

Its seems these were the case. It started a transaction and closes it once done.

I am calling a flush from the Entity Manager to commit the update immediately to the database.

Hence, from your reply with regards to the behavior of "Stateless" Session Bean, I create a "Stateful" Session Bean with an extended Persistent Context Type, please see below:

import java.util.HashMap; import java.util.Map; import javax.ejb.Remove; import javax.ejb.Stateful; import javax.persistence.EntityManager; import javax.persistence.LockModeType; import javax.persistence.PersistenceContext; import javax.persistence.PersistenceContextType; import javax.persistence.PessimisticLockException; @Stateful public class EmployeeUpdateServiceBean { @PersistenceContext(unitName = "EmployeeService", type = PersistenceContextType.EXTENDED) private EntityManager em; private Employee emp; public Employee findForEmployeeUpdate(int empId) { try { Map<String, Object> props = new HashMap<String, Object>(); props.put("javax.persistence.lock.timeout", 10000); emp = em.find(Employee.class, empId, LockModeType.PESSIMISTIC_WRITE, props); em.lock(emp, LockModeType.PESSIMISTIC_WRITE); } catch (PessimisticLockException pessLockExcep) { pessLockExcep.printStackTrace(); } return emp; } public Employee updateEmployee(int empId, long salary) { System.out.println("updateEmployee emp = " + emp); if (emp != null) { em.lock(emp, LockModeType.PESSIMISTIC_WRITE); emp.setSalary(salary); flushChanges(); } return emp; } @Remove protected void flushChanges() { try { em.flush(); } catch (PessimisticLockException pessLockEx) { throw new ChangeCollisionException(); } } }
import java.io.Serializable; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.ManyToOne; import javax.persistence.Version; @Entity public class Employee implements Serializable { private static final long serialVersionUID = 2551888112127389783L; @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private int id; private String name; private long salary; @ManyToOne private Department department; @Version private int version; public int getId() { return id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public long getSalary() { return salary; } public void setSalary(long salary) { this.salary = salary; } public Department getDepartment() { return department; } public void setDepartment(Department department) { this.department = department; } public int getVersion() { return version; } public void setVersion(int version) { this.version = version; } @Override public String toString() { return "Employee [id=" + id + ", name=" + name + ", salary=" + salary + ", department=" + department + ", version=" + version + "]"; } @Override public int hashCode() { final int prime = 31; int result = 1; result = prime * result + id; result = prime * result + ((name == null) ? 0 : name.hashCode()); result = prime * result + version; return result; } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (getClass() != obj.getClass()) return false; Employee other = (Employee) obj; if (id != other.id) return false; if (name == null) { if (other.name != null) return false; } else if (!name.equals(other.name)) return false; if (version != other.version) return false; return true; } }
From these changes I still cannot hit the "PessimisticLockException". It seem that the only way to throw this exception is to compare the before & after state of an entity and throw it manually.

Sorry for the late response.

Any more ideas or insights about this puzzle.

Thanks!

Hi Rafael,

The test scenario would be User1 and User2 accessed the Web Application, then querying the Employee table and list it after find all.

Both users selected the same Employee record with the intention of updating the salary. User1 acquired a pessimistic lock to Employee 10001A at the other end User2 also selected Employee 10001A with the intention of updating the salary. Up onto this point User2 should not be able to acquire a lock to the record since User1 acquired an exclusive pessimistic lock to it.

Should the Pessimistic Lock Exception had been thrown here or if User1 commits his update and User2 also made his with stale copy of the entity?

I am trying to trigger or hit the "PessimisticLockException" in a Web Application context using a stateless session bean with an Entity Manager locking each entity with Pessimistic Lock Type.

Any thought or insights in relation to these?

Thanks very much, appreciate it!

Cheers!
Daniel

Hi Rafael,

Thanks for your reply!

As for my test and setup, I am using a single Entity Manager and in a Web Application accessing by concurrent users.

Although, OptimisticLockException would be sufficient, and I am thinking of eagerly or exclusively acquiring the lock for an entity update.

Any ideas?

I think the "javax.persistence.PessimisticLockException" can be triggered by setting the lock timeout to "0", but it is considered an issue, please see reference bug filed under "Bug 326424 - SELECT FOR UPDATE *NOWAIT* causes syntax error on MySQL".

I was hoping to hit or trigger the "javax.persistence.PessimisticLockException" by using the Entity Manger's find method, passing the Pessimistic Write Lock Type then lock the entity and proceed with the update. And then the other user who tries to update the same entity (with a stale values of the entity) will get the exception. This might also sound optimistic locking, but the main idea would be that the other user cannot update the same entity the 1st user locked for update.

Any ideas about these matters?

Thanks!

Greetings!

I would like to kindly ask how to trigger or hit a “javax.persistence.PessimisticLockException” runtime exception upon locking an entity.

I am hoping for your assistance, and insights in relation to this question.

Thanks very much in advance, I appreciate your time and effort!

Best regards,
Daniel

Greetings!

I found where the problem lies in my code.

Primarily, it was not on the @ElementCollection or @CollectionTable annotation configurations, but rather on the Department relationship @OneToMany annotation. In which by default has a fetch Type of “javax.persistence.FetchType.LAZY”, so the moment I executed the “SELECT” query statement in my “FindAll” button the Department entity didn’t eagerly load its employees.

package examples.model; import java.io.Serializable; import java.util.ArrayList; import java.util.List; import javax.persistence.Column; import javax.persistence.Entity; import javax.persistence.FetchType; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.OneToMany; import javax.persistence.OrderBy; @Entity public class Department implements Serializable { @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="DEPT_ID") private int id; private String name; /** * The FetchType.EAGER make sure that the employees' entity are loaded * when the Department are being read from the database. */ @OneToMany(mappedBy = "department", fetch=FetchType.EAGER) @OrderBy("name ASC") private List<Employee> employees; public Department() { employees = new ArrayList<Employee>(); } public int getId() { return id; } public void setId(int id) { this.id = id; } public String getName() { return name; } public void setName(String deptName) { this.name = deptName; } public void addEmployee(Employee employee) { getEmployees().add(employee); if (employee.getDepartment() != null) { employee.getDepartment().getEmployees().remove(employee.getName()); } employee.setDepartment(this); } public List<Employee> getEmployees() { return employees; } @Override public String toString() { StringBuilder sb = new StringBuilder("Department "); sb.append(" id: "); sb.append(id); sb.append(" name: "); sb.append(name); sb.append(" employeeCount: "); if (getEmployees() != null) { sb.append(getEmployees().size()); } return sb.toString(); } }

I hope this serve as a reference resolution for those who are encountering similar problems with JPA 2.

Thanks very much!

Best regards,
Daniel

Greetings!

I would like to kindly ask some help with regards to my weird problem in JPA 2.1 @ElementCollection/@CollectionTable mapping.

I have created the mapping below:

package examples.model; import java.io.Serializable; import java.util.Map; import javax.persistence.CollectionTable; import javax.persistence.Column; import javax.persistence.ElementCollection; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.JoinColumn; import javax.persistence.ManyToOne; import javax.persistence.MapKeyColumn; @Entity public class Employee implements Serializable { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) @Column(name="EMP_ID") private int id; private String name; private long salary; @ElementCollection @CollectionTable(name = "EMP_PHONE") @MapKeyColumn(name = "PHONE_TYPE") @Column(name = "PHONE_NUM") private Map<String, String> phoneNumbers; @ManyToOne @JoinColumn(name="DEPT_ID") private Department department; public int getId() { return id; } public void setId(int id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public long getSalary() { return salary; } public void setSalary(long salary) { this.salary = salary; } public Department getDepartment() { return department; } public void setDepartment(Department department) { this.department = department; } public Map<String, String> getPhoneNumbers() { return phoneNumbers; } public void setPhoneNumbers(Map<String, String> phoneNumbers) { this.phoneNumbers = phoneNumbers; } public String toString() { StringBuffer aBuffer = new StringBuffer("Employee "); aBuffer.append(" id: "); aBuffer.append(id); aBuffer.append(" with dept: "); if (null != department) { aBuffer.append(department.getName()); } aBuffer.append(" phoneNumbers: "); for (Map.Entry e : phoneNumbers.entrySet()) { aBuffer.append(e.getKey() + "[" + e.getValue() + "] "); } return aBuffer.toString(); } }

I was able to add, update, and read records from my Database. The issue arises when stop my local web app then start it again, and test the “FindAll” button that executes the select statement for getting the entire Employee in the table.
It hangs and there were logs exceptions that have been thrown, please see below:

[EL Finest]: 2014-08-19 15:30:37.805--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--sequencing connected, state is NoPreallocation_State [EL Finest]: 2014-08-19 15:30:37.806--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--sequence SEQ_GEN_IDENTITY: preallocation size 1 [EL Finest]: 2014-08-19 15:30:37.806--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--sequencing connected, state is Preallocation_Transaction_NoAccessor_State [EL Finest]: 2014-08-19 15:30:37.806--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--sequence SEQUENCE: preallocation size 50 [EL Finest]: 2014-08-19 15:30:37.806--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--sequence SEQ_GEN: preallocation size 50 [EL Info]: 2014-08-19 15:30:37.827--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--file:/D:/MyFilez/MyProJpa2Workspace/Chapter5/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/ElementCollectionStringMap/WEB-INF/classes/_EmployeeService login successful [EL Finest]: 2014-08-19 15:30:37.857--ServerSession(1769005174)--Connection(65610490)--Thread(Thread[http-bio-8080-exec-8,5,main])--query column meta data (null.null.DEPARTMENT.null) [EL Finest]: 2014-08-19 15:30:37.857--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Finest]: 2014-08-19 15:30:37.876--ServerSession(1769005174)--Connection(65610490)--Thread(Thread[http-bio-8080-exec-8,5,main])--query column meta data (null.null.EMPLOYEE.null) [EL Finest]: 2014-08-19 15:30:37.876--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Finest]: 2014-08-19 15:30:37.889--ServerSession(1769005174)--Connection(65610490)--Thread(Thread[http-bio-8080-exec-8,5,main])--query column meta data (null.null.EMP_PHONE.null) [EL Finest]: 2014-08-19 15:30:37.889--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Finest]: 2014-08-19 15:30:37.9--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query DataModifyQuery(sql="ALTER TABLE EMPLOYEE ADD CONSTRAINT FK_EMPLOYEE_DEPT_ID FOREIGN KEY (DEPT_ID) REFERENCES DEPARTMENT (DEPT_ID)") [EL Finest]: 2014-08-19 15:30:37.9--ServerSession(1769005174)--Connection(1522981231)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:37.9--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:37.9--ServerSession(1769005174)--Connection(1093705965)--Thread(Thread[http-bio-8080-exec-8,5,main])--ALTER TABLE EMPLOYEE ADD CONSTRAINT FK_EMPLOYEE_DEPT_ID FOREIGN KEY (DEPT_ID) REFERENCES DEPARTMENT (DEPT_ID) [EL Fine]: 2014-08-19 15:30:38.019--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT 1 [EL Finest]: 2014-08-19 15:30:38.021--ServerSession(1769005174)--Connection(1522981231)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Warning]: 2014-08-19 15:30:38.021--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Can't write; duplicate key in table '#sql-b60_c3' Error Code: 1022 Call: ALTER TABLE EMPLOYEE ADD CONSTRAINT FK_EMPLOYEE_DEPT_ID FOREIGN KEY (DEPT_ID) REFERENCES DEPARTMENT (DEPT_ID) Query: DataModifyQuery(sql="ALTER TABLE EMPLOYEE ADD CONSTRAINT FK_EMPLOYEE_DEPT_ID FOREIGN KEY (DEPT_ID) REFERENCES DEPARTMENT (DEPT_ID)") [EL Finest]: 2014-08-19 15:30:38.024--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query DataModifyQuery(sql="ALTER TABLE EMP_PHONE ADD CONSTRAINT FK_EMP_PHONE_Employee_EMP_ID FOREIGN KEY (Employee_EMP_ID) REFERENCES EMPLOYEE (EMP_ID)") [EL Finest]: 2014-08-19 15:30:38.024--ServerSession(1769005174)--Connection(1032637158)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.024--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.024--ServerSession(1769005174)--Connection(1601498268)--Thread(Thread[http-bio-8080-exec-8,5,main])--ALTER TABLE EMP_PHONE ADD CONSTRAINT FK_EMP_PHONE_Employee_EMP_ID FOREIGN KEY (Employee_EMP_ID) REFERENCES EMPLOYEE (EMP_ID) [EL Fine]: 2014-08-19 15:30:38.219--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT 1 [EL Finest]: 2014-08-19 15:30:38.22--ServerSession(1769005174)--Connection(1032637158)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Warning]: 2014-08-19 15:30:38.221--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Can't write; duplicate key in table '#sql-b60_c3' Error Code: 1022 Call: ALTER TABLE EMP_PHONE ADD CONSTRAINT FK_EMP_PHONE_Employee_EMP_ID FOREIGN KEY (Employee_EMP_ID) REFERENCES EMPLOYEE (EMP_ID) Query: DataModifyQuery(sql="ALTER TABLE EMP_PHONE ADD CONSTRAINT FK_EMP_PHONE_Employee_EMP_ID FOREIGN KEY (Employee_EMP_ID) REFERENCES EMPLOYEE (EMP_ID)") [EL Finest]: 2014-08-19 15:30:38.223--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query DataReadQuery(sql="SELECT * FROM SEQUENCE WHERE SEQ_NAME = 'SEQ_GEN'") [EL Finest]: 2014-08-19 15:30:38.223--ServerSession(1769005174)--Connection(871791365)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.223--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.224--ServerSession(1769005174)--Connection(1877784856)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT * FROM SEQUENCE WHERE SEQ_NAME = SEQ_GEN [EL Finest]: 2014-08-19 15:30:38.227--ServerSession(1769005174)--Connection(871791365)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.229--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query DataReadQuery(sql="SELECT * FROM SEQUENCE WHERE SEQ_NAME = 'SEQ_GEN'") [EL Finest]: 2014-08-19 15:30:38.229--ServerSession(1769005174)--Connection(1697797278)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.229--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.229--ServerSession(1769005174)--Connection(1425088016)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT * FROM SEQUENCE WHERE SEQ_NAME = SEQ_GEN [EL Finest]: 2014-08-19 15:30:38.231--ServerSession(1769005174)--Connection(1697797278)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Finer]: 2014-08-19 15:30:38.251--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Canonical Metamodel class [examples.model.Department_] not found during initialization. [EL Finer]: 2014-08-19 15:30:38.252--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Canonical Metamodel class [examples.model.Employee_] not found during initialization. [EL Finest]: 2014-08-19 15:30:38.252--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--End deploying Persistence Unit EmployeeService; session file:/D:/MyFilez/MyProJpa2Workspace/Chapter5/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/ElementCollectionStringMap/WEB-INF/classes/_EmployeeService; state Deployed; factoryCount 1 [EL Finer]: 2014-08-19 15:30:38.468--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--client acquired: 350942644 [EL Finer]: 2014-08-19 15:30:38.476--UnitOfWork(1937558831)--Thread(Thread[http-bio-8080-exec-8,5,main])--TX binding to tx mgr, status=STATUS_ACTIVE [EL Finer]: 2014-08-19 15:30:38.476--ClientSession(350942644)--Thread(Thread[http-bio-8080-exec-8,5,main])--acquire unit of work: 1937558831 [EL Finer]: 2014-08-19 15:30:38.476--UnitOfWork(1937558831)--Thread(Thread[http-bio-8080-exec-8,5,main])--begin unit of work flush [EL Finer]: 2014-08-19 15:30:38.477--UnitOfWork(1937558831)--Thread(Thread[http-bio-8080-exec-8,5,main])--end unit of work flush [EL Finest]: 2014-08-19 15:30:38.477--UnitOfWork(1937558831)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query ReadAllQuery(referenceClass=Employee sql="SELECT EMP_ID, NAME, SALARY, DEPT_ID FROM EMPLOYEE") [EL Finest]: 2014-08-19 15:30:38.478--ServerSession(1769005174)--Connection(95728258)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.478--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.479--ServerSession(1769005174)--Connection(344675398)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT EMP_ID, NAME, SALARY, DEPT_ID FROM EMPLOYEE [EL Finest]: 2014-08-19 15:30:38.48--ServerSession(1769005174)--Connection(95728258)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.486--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query ReadObjectQuery(name="department" referenceClass=Department ) [EL Finest]: 2014-08-19 15:30:38.487--ServerSession(1769005174)--Connection(715138060)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.487--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.488--ServerSession(1769005174)--Connection(1339297268)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT DEPT_ID, NAME FROM DEPARTMENT WHERE (DEPT_ID = ?) bind => [1] [EL Finest]: 2014-08-19 15:30:38.489--ServerSession(1769005174)--Connection(715138060)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.493--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--Execute query ReadAllQuery(name="employees" referenceClass=Employee ) [EL Finest]: 2014-08-19 15:30:38.494--ServerSession(1769005174)--Connection(852310980)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection acquired from connection pool [read]. [EL Finest]: 2014-08-19 15:30:38.494--ServerSession(1769005174)--Thread(Thread[http-bio-8080-exec-8,5,main])--reconnecting to external connection pool [EL Fine]: 2014-08-19 15:30:38.494--ServerSession(1769005174)--Connection(256268673)--Thread(Thread[http-bio-8080-exec-8,5,main])--SELECT EMP_ID, NAME, SALARY, DEPT_ID FROM EMPLOYEE WHERE (DEPT_ID = ?) ORDER BY NAME ASC bind => [1] [EL Finest]: 2014-08-19 15:30:38.504--ServerSession(1769005174)--Connection(852310980)--Thread(Thread[http-bio-8080-exec-8,5,main])--Connection released to connection pool [read].

I am not sure if I missed something or there are existing bugs in relation to this, but I already upgrade to the latest version of EclipseLink and MySQL Connector for Java.

I am hoping someone already encounter these particular anomalies when trying out these use case in JPA 2.1. I appreciate any help you could impart.

Thanks very much in advance!

Best regards,
Daniel

Great discussions there Jared!

Seems this thread has been awaken once more. You've mentioned a lot of good points out there, most especially when it comes to composing each applications/portlet for the portal.

The separation of views or pages per web application in a portal can really be a great deal (+1 points) for Portal/Porlet Development.

Although, I am not pretty much sure about the slowness, perhaps that can be resolved during performance testing and tuning phases.

Another side I am looking at would be the time-to-market (or hosting) the application, if the application is for public consumptions, there are few hosting companies out there that offer good services when it comes to java hosting.
They are at most only offering tomcat container for deploying your web applications, and I am not sure if there are good hosting companies or service out there that can cater for Portal/Portlet deployment.

I am mentioning this area for Portal/Portlet Development since some how if we development a good applications out of it, but we cannot get it out of the market (if we are operating by our selves for example), then it is a problem.
But if some corporations will do this deployment for you or you are working for company that is doing Portal/Portlet Development then its fine.

Greetings!

I would like to kindly ask if there were questions pertaining to XML, Deployment, Testing, and Migration in the exam?

Thanks very much in advance!

Cheers!
Daniel

Greetings!

I am hoping you could kindly help me with the error I am encountering as describe below.

I am trying to separate my entities via package, like the following below:

- manyToManyMap.model.Employee
- overrideCollectionTableColumn.model.Employee

And I am trying to define a separate persistence-unit in my persistence.xml for each package, please see below:
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" version="2.0"> <persistence-unit name="EmployeeServiceDb5_OverrideCollectionTableColumn" transaction-type="JTA"> <jta-data-source>jdbc/empServDb5/overrideCollectionTableColumn </jta-data-source> <class>chapter5.overrideCollectionTableColumn.model.Employee</class> <exclude-unlisted-classes>false</exclude-unlisted-classes> <properties> <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" /> <property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost:3306/DB5_OverrideCollectionTableColumn" /> <property name="javax.persistence.jdbc.user" value="user" /> <property name="javax.persistence.jdbc.password" value="password" /> <!-- enable this property to see SQL and other logging --> <property name="eclipselink.logging.level" value="FINE" /> <property name="eclipselink.ddl-generation" value="create-or-extend-tables" /> </properties> </persistence-unit> <persistence-unit name="EmployeeServiceDb5_ManyToManyMap" transaction-type="JTA"> <jta-data-source>jdbc/empServDb5/manyToManyMap</jta-data-source> <class>chapter5.manyToManyMap.model.Employee</class> <exclude-unlisted-classes>false</exclude-unlisted-classes> <properties> <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" /> <property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost:3306/DB5_ManyToManyMap" /> <property name="javax.persistence.jdbc.user" value="user" /> <property name="javax.persistence.jdbc.password" value="password" /> <!-- enable this property to see SQL and other logging --> <property name="eclipselink.logging.level" value="FINE" /> <property name="eclipselink.ddl-generation" value="create-or-extend-tables" /> </properties> </persistence-unit> </persistence>
But went I tried to deploy it in Glassfish 3.1 from Eclipse (Juno) the following error prompts:
[#|2013-05-08T16:46:15.042+0800|SEVERE|oracle-glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=20;_ThreadName=Thread-2;|Exception while preparing the app : Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.EntityManagerSetupException Exception Description: Predeployment of PersistenceUnit [EmployeeServiceDb5_OverrideCollectionTableColumn] failed. Internal Exception: Exception [EclipseLink-7237] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.ValidationException Exception Description: Entity name must be unique in a persistence unit. Entity name [Employee] is used for the entity classes [manyToManyMap.model.Employee] and [overrideCollectionTableColumn.model.Employee]. Local Exception Stack: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.EntityManagerSetupException Exception Description: Predeployment of PersistenceUnit [EmployeeServiceDb5_OverrideCollectionTableColumn] failed. Internal Exception: Exception [EclipseLink-7237] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.ValidationException Exception Description: Entity name must be unique in a persistence unit. Entity name [Employee] is used for the entity classes [manyToManyMap.model.Employee] and [overrideCollectionTableColumn.model.Employee]. at org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:221) at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1402) at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:208) at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:206) at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120) at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224) at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495) at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233) at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168) at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:353) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291) at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:145) at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:575) at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:461) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:389) at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:380) at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:220) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: Exception [EclipseLink-7237] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.ValidationException Exception Description: Entity name must be unique in a persistence unit. Entity name [Employee] is used for the entity classes [manyToManyMap.model.Employee] and [overrideCollectionTableColumn.model.Employee]. at org.eclipse.persistence.exceptions.ValidationException.nonUniqueEntityName(ValidationException.java:1363) at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.addAlias(MetadataProject.java:392) at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.processEntity(EntityAccessor.java:934) at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:607) at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processStage2(MetadataProject.java:1645) at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:532) at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:526) at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1337) ... 24 more
I am not sure if this is a bug, or I am missing something in JPA 2.0. I already tried to provide different name for each "Employee" entity, but there was an error in persisting an object.

Is there a work around for these scenario, or I might just need to create a separate project for each persistence unit.

Thank you in advance for your insights, time and assistance.

Cheers!
Daniel

Greetings!

In today's Cloud Computing, SOA and Web Services, where every aspect of distributed computing can be transmitted by public and private servers using these technologies, what EJB 3.1 technologies can offer to the developers, and businesses that cannot achieved by the later.

Thanks very much!

Cheers!
Daniel

"i would rather die a meningful death,
than live a meaningless life..."
by corry aquino ex-president of the philippines

Hi,

The profiling tools depends in your IDE.

Netbeans has its own profiling, might want ot check out the NetBeans website for the instructions.

Eclipse also has a lot of profiling tools plugins, might want to checkout the particular plugin that might suites you.

Cheers!

you need to do a profiling for your application to identified the bottleneck.

this way, it will give you an idea of where, and what causing the problems.

cheers!