Foren
using two company ID for one portal instance
Vishal Srivastava, geändert vor 9 Jahren.
using two company ID for one portal instance
Junior Member Beiträge: 26 Beitrittsdatum: 07.07.14 Neueste Beiträge
Hi Everyone ,
I have just migrated my liferay version from 6.1 to 6.2.
After successfully migrated know when i am deploying my portlet i am having two issues.
-First if i am using New Fresh DB Config-:
In my custome portlet if i am trying to open any contact from prev version contact do not get properly loaded.
-Second if i am using OLD DB as of 6.1
If my old db has user xyz@liferay.com and i am trying open his information it shows error.
SO Please suggest how can i use OLD COMPANY ID = 10154 and NEW COMPANY ID = 10157 in Liferay 6.2
Thanks in advance for your help.
PLZ reply ASAP
I have just migrated my liferay version from 6.1 to 6.2.
After successfully migrated know when i am deploying my portlet i am having two issues.
-First if i am using New Fresh DB Config-:
In my custome portlet if i am trying to open any contact from prev version contact do not get properly loaded.
-Second if i am using OLD DB as of 6.1
If my old db has user xyz@liferay.com and i am trying open his information it shows error.
SO Please suggest how can i use OLD COMPANY ID = 10154 and NEW COMPANY ID = 10157 in Liferay 6.2
Thanks in advance for your help.
PLZ reply ASAP
Olaf Kock, geändert vor 9 Jahren.
RE: using two company ID for one portal instance
Liferay Legend Beiträge: 6403 Beitrittsdatum: 23.09.08 Neueste Beiträge
If both servers are available under the same domain name, you might confront them with inappropriate cookies - e.g. stating a nonexistent companyId. Delete the cookies and try again to see if this is your problem.
Vishal Srivastava, geändert vor 9 Jahren.
RE: using two company ID for one portal instance
Junior Member Beiträge: 26 Beitrittsdatum: 07.07.14 Neueste Beiträge
Still have same issue.
On OLD DB whenever i am trying to open old record in edit mode its automatically firing
SQL INSERT COMMAND-: in case of update
Could not execute JDBC batch update; SQL [insert into User_ (uuid_, companyId, createDate, modifiedDate, defaultUser, contactId, password_, passwordEncrypted, passwordReset, passwordModifiedDate, digest, reminderQueryQuestion, reminderQueryAnswer, graceLoginCount, screenName, emailAddress, facebookId, ldapServerId, openId, portraitId, languageId, timeZoneId, greeting, comments, firstName, middleName, lastName, jobTitle, loginDate, loginIP, lastLoginDate, lastLoginIP, lastFailedLoginDate, failedLoginAttempts, lockout, lockoutDate, agreedToTermsOfUse, emailAddressVerified, status, userId) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
On OLD DB whenever i am trying to open old record in edit mode its automatically firing
SQL INSERT COMMAND-: in case of update
Could not execute JDBC batch update; SQL [insert into User_ (uuid_, companyId, createDate, modifiedDate, defaultUser, contactId, password_, passwordEncrypted, passwordReset, passwordModifiedDate, digest, reminderQueryQuestion, reminderQueryAnswer, graceLoginCount, screenName, emailAddress, facebookId, ldapServerId, openId, portraitId, languageId, timeZoneId, greeting, comments, firstName, middleName, lastName, jobTitle, loginDate, loginIP, lastLoginDate, lastLoginIP, lastFailedLoginDate, failedLoginAttempts, lockout, lockoutDate, agreedToTermsOfUse, emailAddressVerified, status, userId) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update