Mi 11 Jun 2008
CWWBF0060E: Cannot find a specific session EJB for the process
Geschrieben von Jürgen Mayer unter Software, Erfahrungen, experience
Tags: BPEL, erfahrung, experience, ProcessServer, WebSphere
I currently work with the IBM Process Server. I created a process using BPEL and wanted to test it. I got the stack trace below. The application can’t start because the Session EJB isn’t available. I enabled the function (projects menu) that automatically performs a rebuild, due to this I recognized (used unkown variables inside a java snippet) some errors. After I fixed these errors I could restart the application without an error, the the Session EJB for the process could be created.
“Clean often” if you work with Websphere Integration Developer is what I suggest. This is also mentioned here at this ‘Get started’ article from Websphere technical developer journal.
If you also work with IBM ProcessServer you may find these tutorials helpful: http://www.webagesolutions.com/knowledgebase/waskb/index.html
I’m glad to see some comments with helpful ‘BPEL with Websphere products’ Tutorials.
SystemErr R com.ibm.websphere.management.exception.AdminException: CWWBF0060E: Die Session-EJB component.Create_Something_1 für den Prozess konnte nicht gefunden werden.
at com.ibm.bpe.processarchive.ProcessServerTask.throwAdminException(ProcessServerTask.java:851)
at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.getBPELContext(SCDLProcessComponentConfigureTask.java:246)
at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.populateBpcDeploymentExtension(SCDLProcessComponentConfigureTask.java:675)
at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.performTask(SCDLProcessComponentConfigureTask.java:153)
at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:253)
at java.lang.Thread.run(Thread.java:570)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at com.ibm.bpe.processarchive.ProcessServerTask.throwAdminException(ProcessServerTask.java:851)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.getBPELContext(SCDLProcessComponentConfigureTask.java:246)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.populateBpcDeploymentExtension(SCDLProcessComponentConfigureTask.java:675)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.performTask(SCDLProcessComponentConfigureTask.java:153)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:253)
[11.06.08 11:11:54:421 CEST] 0000007b SystemErr R at java.lang.Thread.run(Thread.java:570)
Update: Regarding the above error you may also find this useful: http://www-01.ibm.com/support/docview.wss?uid=swg21318484 ( Session EJB bean not found during application deployment ).
What helped me really in an other case having the above error: I created a new workspace and imported the existing projects. So I could get rid of the error. The ejb-xml was created now with EJB references.
Verwandte Beiträge:
- None
6. Oktober 2011 um 11:17
Hi,
This did not work for me, but creating a new workspace and import the project worked. So I make a comparison between the two “.metadata” folders, and found a difference in the “.metadata/.plugins/org.eclipse.core.runtime/.settings/com.ibm.wbit.command.framework.prefs” file: in this file, I set the “BUILD_LEVEL” setting to “3″ (was “2″), and after a workspace restart and clean… the Web project was finally generated, and now it works
3. April 2012 um 09:02
Hi,
Thx Schniouf, you just save me a lot of time today
I have done some research, and it looks like you are the only guy on the internet which has found a real solution to this problem.