[Tomcat, HTTPD, Servlets & JSP] - Problem with NDC
by adalse0
Hi everybody,
i'm not sure if this is the right section for my post,
but i couldn't find something more suitable...
I'm working on a tapestry application and we found out,
that it would be very helpful using NDC to assign every log message to the user who triggered it.
After tapestry provides the method pageBeginRender() and pageEndRender(), which are called before and after rendering of each page, it put the NDC.push() method in the pageBeginRender-method and NDC.pop() and remove() to pageEndRender().
I made these changes and testet the result in my local development environment and saw that everything worked. (My local environment consists of a JBoss and a standalone Tomcat, because in our case this is more comfortable for GUI development)
After checking in these changes and taking a look into the logfile of our nightly build server (which is using no standalone tomcat but just one JBoss) i saw that some log messages include the information added via NDC and others do not.
After a more exact view on the logfile, i think that the problem is the following:
When we are calling a ejb-method (which calls push(), pop() and remove() on her part) on a page, the ejb-method's pop() also affects my NDC in Webclient?!?
If this is really the problem, i'm wondering why our serverside code runs in the same thread than the WebClient?!?
I would be grateful about every hint you can give me onthis topic, thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240337#4240337
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240337
15 years
[JBoss/Spring Integration] - Re: Spring Component Auto Detection
by mike_mackey
thats hard to read ... better
| $ ls
| META-INF
| jboss-spring-int-deployers.jar
| jboss-spring-int-vfs.jar
| jboss-spring.jar
| spring-2.5.6.jar
| spring-beans-2.5.6.jar
| spring-context-2.5.6.jar
| spring-context-support-2.5.6.jar
| spring-core-2.5.6.jar
| spring-orm-2.5.6.jar
| spring-tx-2.5.6.jar
| spring-web-2.5.6.jar
| spring-webmvc-2.5.6.jar
|
|
|
|
| | $ ls
| | META-INF
| | aopalliance-1.0.jar
| | asm-3.1.jar
| | asm-commons-3.1.jar
| | asm-tree-3.1.jar
| | asm-util-3.1.jar
| | aspectjrt-1.6.1.jar
| | aspectjweaver-1.6.1.jar
| | cglib-nodep-2.1_3.jar
| | classworlds-1.1-alpha-2.jar
| | common-mgt-fw.jar
| | common-mgt-fw.war
| | commons-collections-3.2.1.jar
| | commons-dbcp-1.2.2.jar
| | commons-logging-1.1.1.jar
| | commons-pool-1.4.jar
| | hessian-3.1.5.jar
| | jdom-1.1.jar
| | jsr250-api-1.0.jar
| | jstl-1.1.2.jar
| | jta-1.1.jar
| | junit-3.8.1.jar
| | log4j-1.2.14.jar
| | maven-archiver-2.2.jar
| | maven-artifact-2.0.4.jar
| | maven-artifact-manager-2.0.4.jar
| | maven-ear-plugin-2.3.1.jar
| | maven-model-2.0.4.jar
| | maven-plugin-api-2.0.4.jar
| | maven-profile-2.0.4.jar
| | maven-project-2.0.4.jar
| | maven-repository-metadata-2.0.4.jar
| | maven-settings-2.0.4.jar
| | mysql-connector-java-5.1.6.jar
| | plexus-archiver-1.0-alpha-7.jar
| | plexus-container-default-1.0-alpha-9.jar
| | plexus-utils-1.2.jar
| | quartz-1.6.1.jar
| | standard-1.1.2.jar
| | wagon-provider-api-1.0-alpha-6.jar
| |
| |
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240308#4240308
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240308
15 years
[JBoss/Spring Integration] - Re: Spring Component Auto Detection
by mike_mackey
This is the contents of my deployers directory
$ ls
META-INF spring-context-support-2.5.6.jar
jboss-spring-int-deployers.jar spring-core-2.5.6.jar
jboss-spring-int-vfs.jar spring-orm-2.5.6.jar
jboss-spring.jar spring-tx-2.5.6.jar
spring-2.5.6.jar spring-web-2.5.6.jar
spring-beans-2.5.6.jar spring-webmvc-2.5.6.jar
spring-context-2.5.6.jar
my ear contents (I'm still trying to pear this down)
$ ls
META-INF jta-1.1.jar
aopalliance-1.0.jar junit-3.8.1.jar
asm-3.1.jar log4j-1.2.14.jar
asm-commons-3.1.jar maven-archiver-2.2.jar
asm-tree-3.1.jar maven-artifact-2.0.4.jar
asm-util-3.1.jar maven-artifact-manager-2.0.4.jar
aspectjrt-1.6.1.jar maven-ear-plugin-2.3.1.jar
aspectjweaver-1.6.1.jar maven-model-2.0.4.jar
cglib-nodep-2.1_3.jar maven-plugin-api-2.0.4.jar
classworlds-1.1-alpha-2.jar maven-profile-2.0.4.jar
common-mgt-fw.jar maven-project-2.0.4.jar
common-mgt-fw.war maven-repository-metadata-2.0.4.jar
commons-collections-3.2.1.jar maven-settings-2.0.4.jar
commons-dbcp-1.2.2.jar mysql-connector-java-5.1.6.jar
commons-logging-1.1.1.jar plexus-archiver-1.0-alpha-7.jar
commons-pool-1.4.jar plexus-container-default-1.0-alpha-9.jar
hessian-3.1.5.jar plexus-utils-1.2.jar
jdom-1.1.jar quartz-1.6.1.jar
jsr250-api-1.0.jar standard-1.1.2.jar
jstl-1.1.2.jar wagon-provider-api-1.0-alpha-6.jar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240304#4240304
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240304
15 years
[JBossWS] - Re: JBOSS-5.1.0.GA web service client doesn't work ( runtime
by rangalo
This was indeed a missing jars in classpath problem.
I had to add following to the classpath:
| $ echo $CLASSPATH
| jboss_libs/jboss-common-core.jar:jboss_libs/jbossall-client.jar:jboss_libs/jbossws-spi.jar:jboss_libs/jbossws-native-core.jar:jboss_libs/jbossws-native-client.jar::jboss_libs/jaxb-impl.jar:jboss_libs/jboss-xml-binding.jar:jboss_libs/stax-api.jar:jboss_libs/wstx.jar:jboss_libs/jboss-logging-jdk.jar:jboss_libs/jboss-logging-spi.jar:jboss_libs/jbossws-common.jar:jboss_libs/wsdl4j.jar:jboss_libs/mail.jar:jboss_libs/policy.jar:jboss_libs/commons-logging.jar:jboss_libs/javassist.jar:jboss_libs/jboss-remoting.jar
|
All these libs were from jboss/client
But after the client started working, I had following exception in server.log.
| 3:29:21,925 ERROR [[HelloBean]] Servlet.service() for servlet HelloBean threw exception
| java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
| at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169)
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.createSOAPMessage(SOAPFaultHelperJAXWS.java:295)
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:256)
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:187)
| at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
| at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
| at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
|
|
On client side it looks like following:
| $ wsrunclient.sh -cp "dist/hello-client.jar:jboss-generated:lib:$CLASSPATH" com.hardik.mejb.JAXWSClient
| http://localhost:8080/hello-ws-hello-ws/HelloBean?WSDL
| [Fatal Error] :-1:-1: Premature end of file.
| 2: null
|
I installed JBOSS from jboss-5.1.0.GA-jdk6.zip file.
thanks & regards.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240300#4240300
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240300
15 years