[jboss-user] [Performance Tuning] - Re: AJP Connector currentThreadCount stays at maximum
My setup has the same issue, which was introduced in the JBoss 4.2 series that
upgraded from Tomcat 5.5 to Tomcat 6.
I suspect this has to do with the fact that Tomcat 6 doesn't support the
*SpareThreads attributes on the connectors any more. The documentation says
that one must define an element (which defines a thread pool) and reference it
in the connector.
In my opinion, your case should be configured like this:
Executor name=default minSpareThreads=5 maxThreads=256 /
| Connector port=8009 address=${jboss.bind.address} protocol=AJP/1.3
| emptySessionPath=true enableLookups=false redirectPort=8443
| connectionTimeout=2 executor=default /
It you use other connectors as well, they might want to reference the executor
as well. It seems that it's not possible to set maxSpareThreads any more.
I've tried fiddling with this in my own setup, but I end up in a situation
where mod_jk ends up writing to closed Tomcat sockets which result in requests
that lock until mod_jk times out. At this point, though, I don't have the time
to look more into the matter.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208440#4208440
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208440
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Performance Tuning] - Re: AJP Connector currentThreadCount stays at maximum
TIt seems that the forum lets me write HTML in the message. My previous message should have read: The documentation says that one must define an Executor element (which defines a thread pool) and reference it in the connector. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4208444#4208444 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208444 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration DEPLOYMENT] - Wrong redirects for HTTP/1.0 clients when running through AJ
Summary: When running JBoss 4.2 through an AJP/1.3 connector, JBoss 4.2 sends meaningless redirects to HTTP/1.0 clients if they didn't include Host header. Detailed explanation: I'm running Debian Linux etch with Sun's JDK 1.6u11, Apache2.2 + mod_jk, JBoss 4.2.3 (JDK 6 version). I've created a simple webapp directory in the deploy folder named ROOT.war, and it includes a single file named index.jsp with this contents: % response.sendRedirect(/test); % After starting up JBoss, I make an HTTP/1.0 request for the URL /: jbosstest:~# telnet localhost 80 | Trying 127.0.0.1... | Connected to localhost. | Escape character is '^]'. | GET / HTTP/1.0 | | HTTP/1.1 302 Moved Temporarily | Date: Thu, 22 Jan 2009 17:04:53 GMT | Server: Apache/2.2.3 (Debian) mod_jk/1.2.18 | X-Powered-By: Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)/JBossWeb-2.0 | Set-Cookie: JSESSIONID=F4EF264027A06BC0A34849F7E2683BFE; Path=/ | Location: http://localhost:8009/test | Content-Length: 0 | Connection: close | Content-Type: text/html;charset=ISO-8859-1 | | Connection closed by foreign host. The response is (as expected) a redirect to /test, but the hostname (localhost) and port (8009) are meaningless. If I include the Host header in the request (this is not required for HTTP/1.0 requests) or make any HTTP/1.1 request (which will includes the Host header), the server has the expected behavior and sends a redirect to the server itself (in my case jbosstest.mydomain) on the correct port (80). Also, this is only an issue when running through the AJP/1.3 connector, the HTTP/1.1 connector works fine. I've checked with other JBoss versions, and all versions from the 4.2 and 5 series has this behavior. The latest 4.0 version (4.0.5.GA) sends the correct redirect in all cases, so this issue seems to have been introduced in the JBoss 4.2 series (which switched from Tomcat 5.5 to JBossWeb 2.0). Does anyone know how to fix this? It seems this new behaviour is useless to some or all HTTP/1.0 clients. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4204242#4204242 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4204242 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: Wrong redirects for HTTP/1.0 clients when running throug
Since this is probably a JBoss Web Server issue, I'll ask in the JBoss Web Server forum instead. My sincerest apologies for this inconvenience. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4204262#4204262 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4204262 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI/Naming/Network] - Re: Remote JNDI connects locally
I have solved our problems today. We needed to change several things to make it work. 1) Start JBoss with the option -b 0.0.0.0. Otherwise, JBoss only binds to localhost. This should usually give connection refused when doing remote JNDI through the server's real IP, but it didn't in our case, we just got naming errors. This might be due to network configuration and maybe because we're running under Linux VServer where localhost may have a differnt meaning than usual. 2) We accidentally were looking up in the java:-namespace. When doing this, the Context.PROVIDER_URL was silently ignored and generates no warnings or errors but does lookups locally. I was also told that it is a good idea to set jnp.disableDiscovery = true in the InitialContext environment to ensure that you get the server you're asking for and not a different one, if the server you asked for is unavailable. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4192984#4192984 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4192984 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI/Naming/Network] - Re: Remote JNDI connects locally
Let me clarify in case my original description was not clear: I am trying to do a simple job of looking an object up in a remote JNDI registry (192.168.1.10, i.e. not the machine itself). When run from the command line, the code above works perfectly by looking the object up in [EMAIL PROTECTED], but when run from within a JBoss server (e.g. in a servlet) running on another server, it is always looked up in the JNDI registry running on the server itself (thereby ignoring my PROVIDER_URL). I've tried looking for a jndi.properties file that may specify another URL but there are none. I have nothing to go on at this point and have practically given up. I hope someone can help. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4192809#4192809 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4192809 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI/Naming/Network] - Remote JNDI connects locally
I have a remote session bean running on one JBoss 4.2.3 + JDK 6 server and would like to connect to it from code running in another JBoss 4.2.3 + JDK 6 server. My suggestion to doing this is: Hashtable environment = new Hashtable(); | environment.put(Context.INITIAL_CONTEXT_FACTORY, org.jnp.interfaces.NamingContextFactory); | environment.put(Context.URL_PKG_PREFIXES, org.jboss.naming rg.jnp.interfaces); | environment.put(Context.PROVIDER_URL, jnp://192.168.1.10:1099); | InitialContext context = new InitialContext(enviroment); | Object bar = context.lookup(foo); Even though I have asked to connect to the JNDI server running at 192.168.1.10 by providing the PROVIDER_URL, the lookup seems to be performed on the JNDI server running on the same server as the code (i.e. localhost), and therefore it cannot find what I'm looking for. My conclusion is that PROVIDER_URL is ignored or that something overrides it. It think that my setup is very common, and since I can't make it work, there must be some fundamental thing about JNDI that I don't know about, so please, could someone enlighten me? Thanks up front. :-) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4192585#4192585 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4192585 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Advanced Documentation] - Re: When can we expect JBossAS 4.2 documentation?
Damn, those RedHat docs are so full of errors, it seems that they need some serious proofreading. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4092457#4092457 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4092457 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Advanced Documentation] - Re: When can we expect JBossAS 4.2 documentation?
Thanks for the link, I wasn't aware of it. One can only wonder why the docs have not been updated for the community and put on the http://labs.jboss.com/jbossas/docs page. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4092044#4092044 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4092044 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Advanced Documentation] - Re: When can we expect JBossAS 4.2 documentation?
Now 4.2.1 has been released, still no 4.2 docs. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4065298#4065298 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065298 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Advanced Documentation] - When can we expect JBossAS 4.2 documentation?
The JBossAS 4.2 has been on the market for a month now, and there is still no official documentation on http://labs.jboss.com/jbossas/docs When can we expect it? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4054260#4054260 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4054260 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Tomcat, HTTPD, Servlets JSP] - Re: Tapestry output changes from Tomcat to JBoss
The problem seemed to be related to the file.encoding JVM system property having an unexpected value. This was related to the fact that the proper locale support wasn't present in the Linux system. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4001712#4001712 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001712 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Tomcat, HTTPD, Servlets JSP] - Tapestry output changes from Tomcat to JBoss
I'm experiencing a strange problem. When deploying my Tapestry 4 application directly in Tomcat 5.5.20, it runs perfectly, and my localized messages (rendered using ) are output as UTF-8 strings, and the HTTP response headers and HTML headers says that the content type is text/html;charset=UTF-8. So far, so good. BUT, when I fire up my JBoss 4.0.5GA which has an embedded Tomcat 5.5.20 and I deploy my Tapestry application, the localized messages suddenly render as iso-8859-1 but the HTTP response headers and HTML headers still tell the same content type, namely UTF-8. This means that all non-ascii characters show up as ? in my browser because my iso-8859-1 output is parsed as UTF-8 by the browser. Do anyone have any past experiences on what causes my problem? Do anyone have a solution? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3983839#3983839 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3983839 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJB 3.0 RC8 Preview - FD Released
I can't believe that the some haven't fixed these problems and updated the official EJB 3 package (RC9?) so it works. It's over a month since the first user reported missing files. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3958917#3958917 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3958917 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
