|
|
|
|
|
|
|
|
|
|
|
and correct the mistake... |
There are details available:
The problem occurred in class com.livis.livingtalks.web.PitemWebImpl The following exception was finally reported: javax.transaction.TransactionRolledbackException: com.livis.livingtalks.model.LivingTalksException: The database did ignore your request!
Possibly, some field contained too many characters?
(255 and 4000 are typical limits.)
The item was: nested exception is: com.evermind.server.rmi.OrionRemoteException: Error enlisting connection resource: javax.transaction.RollbackException: The transaction has been marked for rollback (Error in transaction: com.evermind.transaction.MarshallingXAException: SQL Error: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/LTDEMO [Restart required]); nested exception is: javax.transaction.RollbackException: The transaction has been marked for rollback (Error in transaction: com.evermind.transaction.MarshallingXAException: SQL Error: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/LTDEMO [Restart required]); nested exception is: javax.transaction.RollbackException: The transaction has been marked for rollback (Error in transaction: com.evermind.transaction.MarshallingXAException: SQL Error: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/LTDEMO [Restart required]) root exception is: javax.transaction.RollbackException: The transaction has been marked for rollback (Error in transaction: com.evermind.transaction.MarshallingXAException: SQL Error: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/LTDEMO [Restart required])
