DO NOT REPLY [Bug 45419] Return Accept-Ranges from DefaultServlet

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45419





--- Comment #12 from Kapil   2009-05-15 01:25:39 PST ---
(In reply to comment #10)
> This has been fixed in 6.0.x and will be included in 6.0.19 onwards.

Hi Mark,

One of my customer is facing the issue that he is not able to byte server the
PDF as PDF is getting completely downloaded in the memory first and then
displayed..They are using JBOSS 4.0.3 SP1 ...I was going through the link
https://issues.apache.org/bugzilla/show_bug.cgi?id=45419 and it says that this
has been fixed in 6.0.x and will be included in 6.0.19 onwardsSo what can i
suggest to my customer ..because even with Jboss 4.2.0 ,tomcat 6.0.13 is
shipped ...so if they upgrade to JBOSS 4.2.0 will it solve their issue?? .They
are using Java Code to serve the PDF and i got one suggestion to implement
byter serving functionality in the servlet but it is causing some performance
issues.

Kindly advice 

Regards
KApil

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47197] New: Error in RUNNING.txt

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47197

   Summary: Error in RUNNING.txt
   Product: Tomcat 6
   Version: 6.0.18
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Documentation
AssignedTo: dev@tomcat.apache.org
ReportedBy: mar...@iskon.hr


There is a small error in the RUNNING.txt file around line 100 in the "Advanced
Configuration - Multiple Tomcat Instances" section. 

The file states that the "setenv.sh" file has to be copied over in the bin
folder of the particular instance, it should be "setclasspath.sh"

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: mod_jk 1.2.28 on i5/OS

2009-05-15 Thread Henri Gomez
Hi Rainer.

With your latest patch, it seems to works.

May be the problem wasn't in thread collision but just with pool
problem with double inits.

I'll do more tests and so stress load


Regards

>2009/5/14 Henri Gomez :
> I'll try the new patch today.
>
> Thanks for your time on this !
>
> Le 13 mai 09 à 15:51, Rainer Jung  a écrit :
>
>> Sorry for the broken patch. Besides the not so nice multiple registation
>> of the cleanup, the real problem for the crash after the patch is, that
>> clear() on a pool already calls the cleanup. So I had to register the
>> cleanup for the parent pool (pconf) and not for the pool itself.
>>
>> I'll think about the thread-safety next, but as I said that is not the
>> cause for your crashes.
>>
>> Regards,
>>
>> Rainer
>>
>> On 13.05.2009 14:56, Henri Gomez wrote:
>>>
>>> Some comments on your latest provided patch :
>>>
>>>      if (!jk_resolv_pool) {
>>>           if (apr_pool_create(&jk_resolv_pool, (apr_pool_t *)pool)
>>> != APR_SUCCESS) {
>>>               JK_TRACE_EXIT(l);
>>>               return JK_FALSE;
>>>           }
>>>       }
>>>       /* We need to clear the pool reference, if the pool gets destroyed
>>>                       * via its parent pool. */
>>>       apr_pool_cleanup_register(jk_resolv_pool, &jk_resolv_pool,
>>> jk_resolv_cleanup, jk_resolv_cleanup);
>>>       apr_pool_clear(jk_resolv_pool);
>>>       if (apr_sockaddr_info_get
>>>           (&remote_sa, host, APR_UNSPEC, (apr_port_t) port, 0,
>>> jk_resolv_pool)
>>>           != APR_SUCCESS) {
>>>           JK_TRACE_EXIT(l);
>>>           return JK_FALSE;
>>>       }
>>>
>>> Why not just add the cleanup register in pool create side ?
>>>
>>>      if (!jk_resolv_pool) {
>>>           if (apr_pool_create(&jk_resolv_pool, (apr_pool_t *)pool)
>>> != APR_SUCCESS) {
>>>               JK_TRACE_EXIT(l);
>>>               return JK_FALSE;
>>>           }
>>>
>>>       /* We need to clear the pool reference, if the pool gets destroyed
>>>                       * via its parent pool. */
>>>       apr_pool_cleanup_register(jk_resolv_pool, &jk_resolv_pool,
>>> jk_resolv_cleanup, jk_resolv_cleanup);
>>>       }
>>>
>>>       apr_pool_clear(jk_resolv_pool);
>>>       if (apr_sockaddr_info_get
>>>           (&remote_sa, host, APR_UNSPEC, (apr_port_t) port, 0,
>>> jk_resolv_pool)
>>>           != APR_SUCCESS) {
>>>           JK_TRACE_EXIT(l);
>>>           return JK_FALSE;
>>>       }
>>>
>>>
>>> Also what could happen if we get many threads calling jk_resolv at the
>>> same time ?
>>
>> 
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



svn commit: r775080 - in /tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster: mcast/McastServiceImpl.java membership/McastServiceImpl.java

2009-05-15 Thread pero
Author: pero
Date: Fri May 15 10:28:29 2009
New Revision: 775080

URL: http://svn.apache.org/viewvc?rev=775080&view=rev
Log:
reset loopback=true that cluster member from same machine can communicate

Modified:

tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/mcast/McastServiceImpl.java

tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/membership/McastServiceImpl.java

Modified: 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/mcast/McastServiceImpl.java
URL: 
http://svn.apache.org/viewvc/tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/mcast/McastServiceImpl.java?rev=775080&r1=775079&r2=775080&view=diff
==
--- 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/mcast/McastServiceImpl.java
 (original)
+++ 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/mcast/McastServiceImpl.java
 Fri May 15 10:28:29 2009
@@ -170,7 +170,8 @@
 protected void setupSocket() throws IOException {
 if (mcastBindAddress != null) {
 try {
-log.info("Attempting to bind the multicast socket to 
"+address+":"+port);
+   if(log.isInfoEnabled())
+log.info("Attempting to bind the multicast socket to 
"+address+":"+port);
 socket = new MulticastSocket(new 
InetSocketAddress(address,port));
 } catch (BindException e) {
 /*
@@ -178,13 +179,13 @@
  * to the multicast address. In this case only bind to the
  * port.
  */
-log.info("Binding to multicast address, failed. Binding to 
port only.");
+log.warn("Binding to multicast address, failed. Binding to 
port only.");
 socket = new MulticastSocket(port);
 }
 } else {
 socket = new MulticastSocket(port);
 }
-socket.setLoopbackMode(true); //hint that we don't need loop back 
messages
+socket.setLoopbackMode(false); //hint that we don't need loop back 
messages
 if (mcastBindAddress != null) {
if(log.isInfoEnabled())
 log.info("Setting multihome multicast interface to:" +

Modified: 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/membership/McastServiceImpl.java
URL: 
http://svn.apache.org/viewvc/tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/membership/McastServiceImpl.java?rev=775080&r1=775079&r2=775080&view=diff
==
--- 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/membership/McastServiceImpl.java
 (original)
+++ 
tomcat/sandbox/tomcat-oacc/trunk/src/share/org/apache/catalina/cluster/membership/McastServiceImpl.java
 Fri May 15 10:28:29 2009
@@ -182,7 +182,8 @@
 protected void setupSocket() throws IOException {
 if (mcastBindAddress != null) {
 try {
-log.info("Attempting to bind the multicast socket to 
"+address+":"+port);
+if(log.isInfoEnabled())
+log.info("Attempting to bind the multicast socket to 
"+address+":"+port);
 socket = new MulticastSocket(new 
InetSocketAddress(address,port));
 } catch (BindException e) {
 /*
@@ -190,13 +191,13 @@
  * to the multicast address. In this case only bind to the
  * port.
  */
-log.info("Binding to multicast address, failed. Binding to 
port only.");
+log.warn("Binding to multicast address, failed. Binding to 
port only.");
 socket = new MulticastSocket(port);
 }
 } else {
 socket = new MulticastSocket(port);
 }
-socket.setLoopbackMode(true); //hint that we don't need loop back 
messages
+socket.setLoopbackMode(false); //hint that we don't need loop back 
messages
 if (mcastBindAddress != null) {
if(log.isInfoEnabled())
 log.info("Setting multihome multicast interface to:" +



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47197] Error in RUNNING.txt

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47197


Mark Thomas  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Comment #1 from Mark Thomas   2009-05-15 04:24:42 PST ---
RUNNING.txt is correct.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47197] Error in RUNNING.txt

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47197





--- Comment #2 from Marko Gnjidic   2009-05-15 05:00:40 PST ---
Created an attachment (id=23665)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23665)
The invalid RUNNING.txt

I just checked again to see if I saw something wrong, but again I must say the
file is not correct, in Tomcat 6.0.18 "bin" directory file named "setenv.sh"
does not exist, and still in the line number 109 of the RUNNING.txt it is
referenced as obligatory? The proper file to transfer into "bin" folder of the
second instance is actually setclasspath.sh (Unix) or setclasspath.bat
(Windows), so this is an error. If you still think I'm wrong please tell me
where do I copy the setenv.sh file from and why Tomcat executable complains
that it needs a copy of setclasspath.sh?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47197] Error in RUNNING.txt

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47197


Marko Gnjidic  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 45419] Return Accept-Ranges from DefaultServlet

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45419





--- Comment #13 from Mark Thomas   2009-05-15 06:04:06 PST ---
Bugzilla is not a support forum. You should use the Tomcat users mailing list
or perhaps the equivalent for JBoss.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47197] Error in RUNNING.txt

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47197


Mark Thomas  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID




--- Comment #3 from Mark Thomas   2009-05-15 06:11:38 PST ---
> I just checked again to see if I saw something wrong, but again I must say the
> file is not correct, in Tomcat 6.0.18 "bin" directory file named "setenv.sh"
> does not exist, and still in the line number 109 of the RUNNING.txt it is
> referenced as obligatory?

Read RUNNING.txt again. It doesn't say that.

> The proper file to transfer into "bin" folder of the
> second instance is actually setclasspath.sh (Unix) or setclasspath.bat
> (Windows), so this is an error.

Wrong. There is no need to copy setclasspath.sh|bat and it should be ignored if
you do.

> If you still think I'm wrong please tell me
> where do I copy the setenv.sh file from and why Tomcat executable complains
> that it needs a copy of setclasspath.sh?

Bugzilla is not a support forum. Use the users list to get help fixing your
setup.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



DO NOT REPLY [Bug 47203] New: Make JMXAdaptorLifecycleListener Java 1.4 compatible

2009-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=47203

   Summary: Make JMXAdaptorLifecycleListener Java 1.4 compatible
   Product: Tomcat 5
   Version: Unknown
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: ichae...@gmail.com


Created an attachment (id=23666)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23666)
Patch for JMXAdaptorLifecycleListener.patch

Hi,

The JMXAdaptorLifecycleListener is used to start a RMI connector, so that
application launched are accessible through JConsole. Please check the section
"JMX Technology for Remote Management" at th following URL =>
http://java.sun.com/developer/technicalArticles/J2SE/jmx.html

For now, the JMXAdaptorLifecycleListener is only available in Java 5.
The purpose of this patch is to make it available for Java 1.4,
and make this class available in standard in the tomcat 5.5 package.
This was not the case before because this class was only Java 5 compatible.

In Java 1.4, you will need the following jar to be able to launch the server :
 - jmxri.jar ( JMX Reference API)
 - jmx-remote.jar, rmi.ssl ( JMX-Remote Reference API)

Best regards,

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org