-
1. Re: jBPM in Websphere 6.0
jchela Jun 15, 2007 3:57 PM (in response to jchela)just to clarify, i did search the forum and I found couple of people having asked this question but haven't seen any helpful response.
-
2. Re: jBPM in Websphere 6.0
kukeltje Jun 16, 2007 11:04 PM (in response to jchela)did you try? there is a jBPM war file... deploy it and get back with error reports
-
3. Re: jBPM in Websphere 6.0
ghezzi Sep 28, 2007 3:37 AM (in response to jchela)I've tried the approach of deploying jbpm-console.war under websphere 6.1.0.3
(previously i've modify WEB-INF/classes/hibernate.cfg.xml changing the db driver for my needs)
i've added hibernate jars which was a documented suggestion
Then i get
[9/28/07 8:52:39:493 CEST] 0000001e WebApp E Extension processor failed to initialize in factory: com.ibm.ws.jsf.extprocessor.JSFExtensionFactory@41744174
java.lang.NoClassDefFoundError: edu.emory.mathcs.backport.java.util.concurrent.ConcurrentMap
i add
jboss-backport-concurrent.jar
and put them inside WEB-INF\lib
then i get this
[9/28/07 8:55:44:569 CEST] 00000020 WebApp E Extension processor failed to initialize in factory: com.ibm.ws.jsp.webcontainerext.ws.WASJSPExtensionFactory@53d853d8
java.lang.NoSuchMethodError: com/sun/faces/util/Util.getLogger(Ljava/lang/String;)Ljava/util/logging/Logger;
(i have tried to add also log4j and commons-logging but nothing changes)
...and the application is not work since if try to access the webapp i get
Error 403: SRVE0190E: File not found: /index.jsp
Furthermore there's some other problem because
in the log i see
[9/28/07 9:11:31:024 CEST] 000001e1 javaURLContex E NMSV0310E: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. Exception stack trace:
javax.naming.ConfigurationException [Root exception is javax.naming.NameNotFoundException: Name not found in context "java:".]
at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:411)
at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:388)
at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:204)
which seems to be related to a bug fixed in bpm 3.2.3 i've seen
on jira
I would like to use the console to deploy my processes and monitor
them.... i think i wil lgo for custom deploy
[examples here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85420]
bye -
4. Re: jBPM in Websphere 6.0
fjacquet Oct 11, 2007 11:07 AM (in response to jchela)change datasource in hibernate from java:/jbpmDS to the same value as your WebSphere datasource
it will remove this issue
but I have same nasty issue on
[11.10.07 17:02:17:153 CEST] 000000f3 SystemErr R java.lang.NoSuchMethodError: com.sun.faces.util.Util: method getLogger(Ljava/lang/String;)Ljava/util/logging/Logger; not found
at com.sun.faces.application.WebappLifecycleListener.(WebappLifecycleListener.java:67)