[JBoss jBPM] - Re: Problem deploying jbpm-console
by clecompt
I'm currently trying to deploy the 3.2.2 jbpm-enterprise.ear in a jboss application server configured to use the JBossWebClassloader (it needs to since another app depends on this). I have moved the myfaces jars to the jbpm-console.war/WEB-INF/lib directory within the ear and added a jboss-app.xml file to partition the class loader for the ear. This setup seems to work fine on my local machine which is windows XP using the JBOSS supplied with the suite (modified accordingly). On Solaris however, I receive the error:
http-0.0.0.0-18950-1 2007-10-09 18:12:22,097 | ERROR | session= | user= | org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-console].[Faces Servlet] | Servlet.service() for servlet Faces Servlet threw exception
| java.lang.NullPointerException
| at com.sun.faces.lifecycle.ELResolverInitPhaseListener.populateFacesELResolverForJsp(ELResolverInitPhaseListener.java:135)
| at com.sun.faces.lifecycle.ELResolverInitPhaseListener.beforePhase(ELResolverInitPhaseListener.java:100)
| at org.apache.myfaces.lifecycle.LifecycleImpl.informPhaseListenersBefore(LifecycleImpl.java:520)
| at org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:105)
| at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
On the windows server instance I get a similar related message but the application appears fine and I can log in:
2007-10-09 18:09:52,770 ERROR [STDERR] Oct 9, 2007 6:09:52 PM com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp
| INFO: JSF1027: [null] The ELResolvers for JSF were not registered with the JSP container.
Could this be dependent upon the data source? I have switched that to use an Oracle schema generated using the supplied database scripts.
Also, the version of the target JBOSS instance is 4.0.4 GA (the same build as the suite's server).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093222#4093222
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093222
18Â years, 7Â months
[JBoss Seam] - NullPointerException in org.jboss.seam.webservice.SOAPReques
by sg26565
I tried to write a conversational webservice with seam 2.0.0.CR2
My first problem was that the documented way of putting a standard-jaxws-endpoint-config.xml file into META-INF didn't work at all. Instead I added a handler-chain to sun-jaxws.xml.
<?xml version="1.0" encoding="UTF-8"?>
| <endpoints xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime" version="2.0">
| <endpoint name="Hello" implementation="hello.Hello" url-pattern="/ws/hello">
| <handler-chains xmlns="http://java.sun.com/xml/ns/javaee">
| <handler-chain>
| <protocol-bindings>##SOAP11_HTTP</protocol-bindings>
| <handler>
| <handler-name>SOAP Request Handler</handler-name>
| <handler-class>org.jboss.seam.webservice.SOAPRequestHandler</handler-class>
| </handler>
| </handler-chain>
| </handler-chains>
| </endpoint>
| </endpoints>
This way the SOAPRequestHandler was callled, but it threw a NullPointerException:
ava.lang.NullPointerException
| at org.jboss.seam.webservice.SOAPRequestHandler.handleOutbound(SOAPRequestHandler.java:107)
| at org.jboss.seam.webservice.SOAPRequestHandler.handleMessage(SOAPRequestHandler.java:56)
| at
| ...
The Exception was caused by the following statement in org.jboss.seam.webservice.SOAPRequestHandler line 107 where getSOAPHeader() returns null:
SOAPMessageContext smc = (SOAPMessageContext) messageContext;
| SOAPElement element = smc.getMessage().getSOAPHeader().addChildElement(CIDQN);
If I change the code to:
SOAPMessageContext smc = (SOAPMessageContext) messageContext;
| SOAPMessage msg = smc.getMessage();
| SOAPPart part = msg.getSOAPPart();
| SOAPEnvelope env = part.getEnvelope();
| SOAPHeader header = env.getHeader();
| if (header == null) {
| header = env.addHeader();
| }
| SOAPElement element = header.addChildElement(CIDQN);
then the webservice works as expected.
So my question is: Is this a bug in seam, or is something wrong with my setup?
btw.: I'm running seam 2.0.0.CR2 with jax-ws 2.1.1 and jdk1.5.0_13 on tomcat 6.0.14
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093215#4093215
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093215
18Â years, 7Â months
[Messaging, JMS & JBossMQ] - maxMessages
by Renen
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJMSMessageListener defines "maxMessages" as follows:
anonymous wrote :
| maxMessages - read this number of messages before delivering messages to the mdb (each message is delivered individually on the same thread in an attempt to avoid context excessive context switching) - default 1
|
Which seems to behave as one would like it. Set it to two, and two messages are processed at a time. Set it to four, and four get processed at a time. And that number of MDBs get constructed.
In other words, maxMessages seems to define the number of MDBs that will be instantiated, and each MDB is single threaded. Is this correct?
In EJB2, there you could configure min-pool-size and max-pool-size, but the MDBs seemed to be multi-threaded. Certainly, setting max-pool-size to 1 did not turn your bean into a singleton. So EJB3 would definitely seem to be a step forward. Having said that, is it possible or relevant to ask about controlling the "threadedness" of EJB3 MDBs? Am I right to assume that I don't need to worry about it?
Thanks in advance for the clarification!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093213#4093213
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093213
18Â years, 7Â months