DO NOT REPLY [Bug 38211] - Unable to compiler JSP-Files with Tomcat > 5.5.9

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38211


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Mod_JK / Tomcat : How does Tomcat know its name in mod_jk side?

[gaston . azerty]

Thanks

Quoting Rainer Jung <[EMAIL PROTECTED]>:

> The name associated with each worker must match the one used for the
> jvmRoute attribute specified on the Engine element of the corresponding
> node's server.xml.
>
> It's not explicitely passed via AJP. You need to keep the names in
> workers.properties/server.xml in sync by yourself.
>
> Rainer
>
> [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I'm always working on mod_jk and I have got a question about cookie
> generation
> > on the Tomcat side.
> > When a request has been send by a new client, he obtains a Cookie, this
> cookie
> > has been generated by Tomcat (worker). In this cookie, we find the route to
> the
> > correct worker for the next request (JSESSIONID=EF45..B01.worker1, worker1
> is
> > the route) (if sticky_session is on), but how Tomcat knows that his name in
> > mod_jk side is "worker1"?
> > Where this information has been sent in the ajp protocol?
> >
> > Regards,
> >
> > Thomas
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 38211] - Unable to compiler JSP-Files with Tomcat > 5.5.9

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38211


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED




--- Additional Comments From [EMAIL PROTECTED]  2006-07-24 09:19 ---
I finally found what was the problem, and Tomcat was not in charge of this 
problem.

Our webapp included a JAR called rt4.jar in WEB-INF/lib, and after some search,
this JAR contained the java.util.Map interface !!! This interface was used to
compile the JSP (strange that it was used against the standard Map from the
API), and finally generate the output.

Thanks everybody for your help, and sorry to report a false bug.

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40070] - APR causes JVM to crashon SEGV

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40070


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2006-07-24 09:34 ---
Is there any related bug report or document/web page I can read to figure out 
exactly what to do? I can certain write a bypassing output stream wrapper, but 
it doesn't seem to do any good if I just simply pass every call to the 
underlying output stream given by Tomcat.

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Releasing Tomcat Connectors 1.2.18

[Rainer Jung]

Hello to all Tomcat project members,

after 2 unsuccessful release attempts for mod_jk it looks like 1.2.18 
doesn't get any bug reports. All known bugs related to 1.2.16 and 1.2.17 
have been fixed in 1.2.18. About 20 users downloaded 1.2.16 and 1.2.17 
each, and 11 downloads happened for 1.2.18 (until yesterday). I think we 
got good feedback from the community.


Although I announced the availability of the 1.2.18 release candidate 
only 4 days ago (see 
http://marc.theaimsgroup.com/?l=tomcat-dev&m=115336261231270&w=2 ), I 
would like to start a release vote. Somehow I partially count the days 
of 1.2.16 and 1.2.17 testing, because changes for 1.2.18 have been very 
small.


If you want to take a look, the source distribution can be downloaded from:

http://tomcat.apache.org/dev/dist/

The updated documentation can be found at

http://tomcat.apache.org/dev/docs/tomcat-connectors-1.2.18/

Please see

http://tomcat.apache.org/dev/docs/tomcat-connectors-1.2.18/changelog.html

for a complete list of changes.

So here's the vote, which will be open until Friday July 28th, 24:00 GMT.

Apache Tomcat Connectors 1.2.18 is:
[ ] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are

Thank you,

Rainer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Mladen Turk]

Rainer Jung wrote:

Apache Tomcat Connectors 1.2.18 is:
[X] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are



BTW, excellent job Rainer!

--
Mladen.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Henri Gomez]

Stable

2006/7/24, Mladen Turk <[EMAIL PROTECTED]>:

Rainer Jung wrote:
> Apache Tomcat Connectors 1.2.18 is:
> [X] Stable - no major issues, no regressions
> [ ] Beta - at least one significant issue -- tell us what it is
> [ ] Alpha - multiple significant issues -- tell us what they are
>

BTW, excellent job Rainer!

--
Mladen.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Peter Rossbach]

Stable,

really cool community driven release. :-)

Peter

Am 24.07.2006 um 12:13 schrieb Mladen Turk:


Rainer Jung wrote:

Apache Tomcat Connectors 1.2.18 is:
[X] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Mohan Wickramasinghe]

Please tell what the issue was with 1.2.17 ?
Have being using it in linux from time of release.

Thanks

On Mon, 2006-07-24 at 13:07 +0200, Peter Rossbach wrote:
> Stable,
> 
> really cool community driven release. :-)
> 
> Peter
> 
> Am 24.07.2006 um 12:13 schrieb Mladen Turk:
> 
> > Rainer Jung wrote:
> >> Apache Tomcat Connectors 1.2.18 is:
> >> [X] Stable - no major issues, no regressions
> >> [ ] Beta - at least one significant issue -- tell us what it is
> >> [ ] Alpha - multiple significant issues -- tell us what they are
> >
> 
-- 
Mohan Wickramasinghe <[EMAIL PROTECTED]>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Rainer Jung]

In case of further questions, please start a new thread, this one is 
only for the voting.


In short: 1.2.17 had a subtle build problem e.g. on AS400 platform. 
There is no known trouble on Linux. Glad to hear it also worked for you, 
but you should nevertheless take the next opportunity and move to the 
official release. 1.2.17 will never be officially released. Furthermore 
1.2.18 added a new minor enhancement, the recovery time is now allowed 
below 60 seconds.


Rainer

Mohan Wickramasinghe wrote:

Please tell what the issue was with 1.2.17 ?
Have being using it in linux from time of release.

Thanks

On Mon, 2006-07-24 at 13:07 +0200, Peter Rossbach wrote:


Stable,

really cool community driven release. :-)

Peter

Am 24.07.2006 um 12:13 schrieb Mladen Turk:



Rainer Jung wrote:


Apache Tomcat Connectors 1.2.18 is:
[X] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r425034 - /tomcat/connectors/trunk/jk/native/common/jk_map.c

[rjung]

Author: rjung
Date: Mon Jul 24 06:01:06 2006
New Revision: 425034

URL: http://svn.apache.org/viewvc?rev=425034&view=rev
Log:
Enable '*' token separator, e.g. when
using multi-line balance_workers etc.

Modified:
tomcat/connectors/trunk/jk/native/common/jk_map.c

Modified: tomcat/connectors/trunk/jk/native/common/jk_map.c
URL: 
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/common/jk_map.c?rev=425034&r1=425033&r2=425034&view=diff
==
--- tomcat/connectors/trunk/jk/native/common/jk_map.c (original)
+++ tomcat/connectors/trunk/jk/native/common/jk_map.c Mon Jul 24 06:01:06 2006
@@ -283,10 +283,10 @@
  * strtok also by a "*"
  */
 #if defined(AS400) || defined(_REENTRANT)
-for (p = strtok_r(v, " \t,", &lasts);
- p; p = strtok_r(NULL, " \t,", &lasts))
+for (p = strtok_r(v, " \t,*", &lasts);
+ p; p = strtok_r(NULL, " \t,*", &lasts))
 #else
-for (p = strtok(v, " \t,"); p; p = strtok(NULL, " \t,"))
+for (p = strtok(v, " \t,*"); p; p = strtok(NULL, " \t,*"))
 #endif
 
 {



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5 and HostConfig

[Henri Gomez]

I've got some problems on some of our production servers, running Suse
SLES 9 / IBM SDK 1.4.2 SR5 with webapp loading order.


From what I saw in org.apache.catalina.startup.HostConfig, the

deployApps method make use of File.list() which is not guaranteed to
return the list of String in any particular order :

*  There is no guarantee that the name strings in the resulting array
* will appear in any specific order; they are not, in particular,
* guaranteed to appear in alphabetical order.
*

What about using a simple Arrays.sort to have the list sorted in
alphabetical order and so have something coherent between JDK and
implementations ?

Here is the 'modified' deployApps method.

   /**
* Deploy applications for any directories or WAR files that are found
* in our "application root" directory.
*/
   protected void deployApps() {

   File appBase = appBase();
   File configBase = configBase();
   // Deploy XML descriptors from configBase
   String [] list = configBase.list();
   Arrays.sort(list);
   deployDescriptors(configBase, list);
   // Deploy WARs, and loop if additional descriptors are found
   list = appBase.list();
   Arrays.sort(list);
   deployWARs(appBase, list);
   // Deploy expanded folders
   deployDirectories(appBase, list);

   }


Regards

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Yoav Shapira]

Hi,


So here's the vote, which will be open until Friday July 28th, 24:00 GMT.

Apache Tomcat Connectors 1.2.18 is:
[ X ] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are


I did much more limited testing than other people, but it seems to
compile and run fine (under light load) on Fedora Core 5.

Also great job Rainer steering this through.

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Releasing Tomcat Connectors 1.2.18

[Jean-frederic Clere]

Stable.

Cheers

Jean-Frederic


Rainer Jung wrote:


Hello to all Tomcat project members,

after 2 unsuccessful release attempts for mod_jk it looks like 1.2.18 
doesn't get any bug reports. All known bugs related to 1.2.16 and 
1.2.17 have been fixed in 1.2.18. About 20 users downloaded 1.2.16 and 
1.2.17 each, and 11 downloads happened for 1.2.18 (until yesterday). I 
think we got good feedback from the community.


Although I announced the availability of the 1.2.18 release candidate 
only 4 days ago (see 
http://marc.theaimsgroup.com/?l=tomcat-dev&m=115336261231270&w=2 ), I 
would like to start a release vote. Somehow I partially count the days 
of 1.2.16 and 1.2.17 testing, because changes for 1.2.18 have been 
very small.


If you want to take a look, the source distribution can be downloaded 
from:


http://tomcat.apache.org/dev/dist/

The updated documentation can be found at

http://tomcat.apache.org/dev/docs/tomcat-connectors-1.2.18/

Please see

http://tomcat.apache.org/dev/docs/tomcat-connectors-1.2.18/changelog.html

for a complete list of changes.

So here's the vote, which will be open until Friday July 28th, 24:00 GMT.

Apache Tomcat Connectors 1.2.18 is:
[ ] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are

Thank you,

Rainer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40104] New: - Jasper picking up incorrect file in JspServletWrapper.java context dump

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40104

   Summary: Jasper picking up incorrect file in
JspServletWrapper.java context dump
   Product: Tomcat 5
   Version: 5.5.17
  Platform: Other
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


org.apache.jasper.JasperException: Exception in JSP: 
/WEB-INF/template/debug.jspf:4

1: <%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8" isErrorPage="true"%>
2: <%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %>
3: <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt"; prefix="fmt" %>
4: <%@ taglib prefix="g" uri="http://domain.com/taglibs/generic-0.1"; %>
5: 
6: 
7: 

Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
...SNIP...


The exception correctly reports the point of the error:
/WEB-INF/template/debug.jspf:4

But the 7 lines of context are actually from the file
/WEB-INF/template/errorpage.jsp


jasper/jasper2/src/share/org/apache/jasper/servlet/JspServletWrapper.java:471 
uses:

  // Read both files in, so we can inspect them
  String[] jspLines = readFile
  (this.ctxt.getResourceAsStream(this.ctxt.getJspFile()));

  String[] javaLines = readFile
  (new FileInputStream(this.ctxt.getServletJavaFileName()));

Is that correctly picking up the context from the exception information ?

The page debuig.jspf is added to a master page with:

<%@ include file="/WEB-INF/template/debug.jspf" %>


The exception looks like it created here:

return new JasperException(
   "Exception in JSP: " +
detail.getJspFileName() + ":" +
   jspLineNumber + "\n\n" + buffer +
"\n\nStacktrace:", ex);

That uses detail.getJspFileName() not this.ctxt.getServletJavaFileName().

I'm thinking both cases should use detail.getJspFileName().


I have ErrorPages setup to /WEB-INF/template/errorpage.jsp.

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40104] - Jasper picking up incorrect file in JspServletWrapper.java context dump

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40104





--- Additional Comments From [EMAIL PROTECTED]  2006-07-24 17:13 ---
Opps not this.ctxt.getServletJavaFileName().

I meant to say I think this.ctxt.getJspFile() should be detail.getJspFileName()
(or the equalvalent of)

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mod_jk 1.2.17+ Recover time

[David Rees]

On 7/19/06, Rainer Jung <[EMAIL PROTECTED]> wrote:

David Rees wrote:
> Thanks that should work around my issue quite nicely. I'll check out
> SVN and give a whirl (unless a new tag is to be rolled again shortly?)

Try 1.2.18.


1.2.18 works much better, thanks!

-Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40107] New: - JK should handle EAGAIN in jk_is_socket_connected()

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40107

   Summary: JK should handle EAGAIN in jk_is_socket_connected()
   Product: Tomcat 5
   Version: 5.5.17
  Platform: HP
OS/Version: HP-UX
Status: NEW
  Severity: normal
  Priority: P2
 Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


I am using mod_jk 1.2.14 with SUN ONE web server 6.1 on HP-UX.

I found that this error message on mod_jk log file.
---
[화 7월 19 15:27:55 2006] [16718:0016] [info]  jk_ajp_common.c 
(1178): Socket 35
is not connected any more (errno=11)
[화 7월 19 15:27:55 2006] [16718:0016] [info]  jk_ajp_common.c 
(1202): Error
sending request. Will try another pooled connection
[화 7월 19 15:27:55 2006] [16718:0016] [info]  jk_ajp_common.c 
(1178): Socket 34
is not connected any more (errno=11)
[화 7월 19 15:27:55 2006] [16718:0016] [info]  jk_ajp_common.c 
(1202): Error
sending request. Will try another pooled connection
[화 7월 19 15:27:55 2006] [16718:0016] [info]  jk_ajp_common.c 
(1225): All
endpoints are disconnected or dead
-

Digging into mod_jk source code, jk_is_socket_connected() in jk_connect.c seems
 to have a problem.

In HP-UX, non-blocking read() would fail with errno 11 (EAGAIN) instead of
EWOULDBLOCK.

Reviewing errno.h and related files in several platforms, I found that
EWOULDBLOCK is same as EAGAIN in Linux, but NOT in HP-UX.
I feel that EAGAIN should be treated same as EWOULDBLOCK in
jk_is_socket_connected(). 

-- Jongjin

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40107] - JK should handle EAGAIN in jk_is_socket_connected()

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40107





--- Additional Comments From [EMAIL PROTECTED]  2006-07-25 05:00 ---
For the unenlightened what are the semantic differences ?  Is EAGAIN used for
read/accept operations and EWOULDBLOCK used for write/connect operations ?

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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 40107] - JK should handle EAGAIN in jk_is_socket_connected()

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40107





--- Additional Comments From [EMAIL PROTECTED]  2006-07-25 05:11 ---
Darryl, 
I don't know exactly what the difference is between EAGAIN and EWOULDBLOCK. 
As a quick google search result, I got following link : 
http://www.codecomments.com/archive286-2005-10-641948.html

That may be helpful. Thanks for your interest.





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

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]