Note that there are some explanatory texts on larger screens.

plurals
  1. POHandling 'The EJB does not exist' or 'Cannot load from BACKUPSTORE FOR Key'
    primarykey
    data
    text
    <p>so the problem is pretty simple:</p> <p>We are using JSF 2.0 with Primefaces and EJB to handle our application and we have encountered a problem. We have a single <code>@SessionScoped</code> bean in which we store all ours <code>@Stateful Session Beans</code>.</p> <p>In one case, (when we didn't handle some exceptions from JPA) and there is an exception: </p> <pre><code>javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.2.0.v20110202-r8913): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "webuser_idwebuser_pk" Detail: Key (idwebuser)=(6) already exists. </code></pre> <p>It leads to destruction of one of our <code>@Stateful Session Bean</code>. So after refreshing the website, when JSF is still working correctly, after filling the form and trying to submit it, by invoking a method from that Bean there is an exception:</p> <pre><code>javax.ejb.NoSuchObjectLocalException: The EJB does not exist. session-key: 22900a4d007e1f-6dcc714a-0 </code></pre> <p>What is the most problematic, we have to restart and redeploy the application to make it work on the same computer (or web browser) because the JSF's <code>@SessionScoped</code> Bean is somehow kept through cookies or something.</p> <p>So the solution I guess would be to force the destuction of that <code>@SessionScoped</code> or refresh the session somehow, but actually I have no idea how to do so. Or what would be a better approach.</p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload