Created: (DTACLOUD-4) JSON gem as of version 1.4.6 is causing server errors

Cached stream file deletion causing file not found errors

Server Generating Incorrect URLs When Running At Non-Root Context

start-server -b fails with errors about unbound beans

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Ben Browning updated DTACLOUD-2:

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Ben Browning updated DTACLOUD-2:

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Ben Browning updated DTACLOUD-2:

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Ben Browning updated DTACLOUD-2:

I kept running into the stop-the-world GC during batch import of data into
hbase.  The configuration of a node in the 8-node cluster is as follows.

* 4-core
* 64-bit JVM
* 8 GB of memory
* CDH2 for hadoop and 0.20.5 for hbase
* TT: 128 MB
* DN: 128 MB
* 2 Mappers at 512 MB each
* 2 Reducer at 512 MB each
* 1 regionserver at 4096 MB

The import job was a mapper only job so that only TT, DN, 2 mappers and
regionserver were running.  Below is the JMX output for the dead
regionserver.

Time:
2010-07-29 12:25:47
Used:
   224,949 kbytes
Committed:
   670,728 kbytes
Max:
 4,185,792 kbytes
GC time:
     5 minutes on ParNew (2,126 collections)
 0.000 seconds on ConcurrentMarkSweep (0 collections)

Clearly the regionserver was spent all GC time on ParNew, which was not
surprising as I was imported tons of data.  But I could not figure out why
the same GC that usually take way less than a second, took 299 secs at
line
3.  Any enlightenment is greatly appreciated.

I will change ParNew to 6M as documented in Performance Tuning page and
gave
it another shot.

010-07-28T12:06:57.249-0700: 2406.986: [GC 2406.986: [ParNew:
17786K->755K(19136K), 0.0015410 secs] 348288K->331394K(620416K)
icms_dc=27 ,
0.0016330 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2010-07-28T12:06:57.268-0700: 2407.004: [GC 2407.004: [ParNew:
17580K->761K(19136K), 0.0016710 secs] 348154K->331343K(620416K)
icms_dc=27 ,
0.0017610 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2010-07-28T12:06:57.288-0700: 2407.024: [GC 2407.088: [ParNew:
17564K->757K(19136K), 299.1513910 secs] 348081K->331283K(620416K)
icms_dc=27
, 299.1515120 secs] [Times: user=0.17 sys=0.04, real=299.23 secs]
2010-07-28T12:11:56.558-0700: 2706.294: [GC 2706.294: [ParNew:
17735K->925K(19136K), 0.0094600 secs] 348197K->331458K(620416K)
icms_dc=27 ,
0.0095670 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
2010-07-28T12:11:56.606-0700: 2706.343: [GC 2706.343: [ParNew:
17940K->932K(19136K), 0.0085750 secs] 348473K->331474K(620416K)
icms_dc=27 ,
0.0086710 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]

Dear List,

It appears that when mod_disk_cache reads server side includes to create
its final cached web page, it sometimes corrupts the included file.

I think the issue may be that the included file is getting DEFLATEd and
Apache is intermittently forgetting to ungzip it prior to putting it into
the parent page.

Any other thoughts?

Thanks,

http://www.t1shopper.com/

Details: The parent web page is called "index.shtml" and the child file is
getting included like this:
<!--#include virtual="/dir/include/my_html_file.html" -->

Everything else on the page looks fine but where the my_html_file.html
should be we see binary output in the source code like this:
í\énÛHþÜ|á]åâu?-SìA½¡!ŸÄoÿ›IÅÇsØß'±"’ÿ
¼ñ*dLXúIpV.n§Œ ©äÉb®H&Ùˆð˜I

If I restart Apache, the problem remains. But the problem goes away if I
delete the cache on the web server. So the cache must have gotten
corrupted. I can refresh the page many times after that and the page is
fine. This good page is kept in cache for about 30 days because of the
config settings (below).


LoadModule deflate_module modules/mod_deflate.so
DeflateCompressionLevel 1
DeflateMemLevel 9
DeflateWindowSize 15
SetEnvIfNoCase Request_URI \
\.(?:gif|jpe?g|png|ico)$ no-gzip dont-vary
#Header append Vary User-Agent env=!dont-vary


LoadModule disk_cache_module modules/mod_disk_cache.so
CacheRoot /var/httpd/proxy/
CacheEnable disk /
CacheDisable /i
CacheMaxFileSize 500000
CacheMinFileSize 1000
CacheDirLevels 2
CacheDirLength 2
CacheIgnoreCacheControl Off
CacheIgnoreNoLastMod On
CacheIgnoreHeaders Set-Cookie
CacheLastModifiedFactor 0.1
CacheMaxExpire 172800
CacheDefaultExpire 86400 

http://mail-archives.apache.org/mod_m..### @rabbithill>

Hi,

we're using Apache CXF 2.2.9 to access a webservice. The service is served
on a tomcat-server (using the cxf-servlet, but this is not important here)
and protected by requiring http basic auth. When supplying correct
username/password-data in our client this works as expected when using the
following code:

JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
        factory.setServiceClass( IReferenceManagerImpl.class);
        factory.setAddress( wsAddress.toString());
        factory.setUsername( horus_user);
        factory.setPassword( horus_password);

        IReferenceManagerImpl implementation = ( IReferenceManagerImpl)
factory.create();
//afterwards we're setting allowChunking to false for our
http-client-policy
since chunking gives us some problem with oracle webcache, but this isn't
the point here...

However, when the user supplied a wrong password, things go wrong. Instead
of CXF to give me a HTTP 401 Exception code it tries for many times to
authenticate against the server (20 times I think) and finally gives me
the
following exception:

Caused by: java.net.ProtocolException: Server redirected too many  times
(20)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2165)


This is fatal for us, since after so much error-nous tries our ldap-server
locks the user that provide a wrong password.

I tracked down the issue and found out that the Sun HttpURLConnection asks
the default Authenticator for username/password when getting 401. This
repeats in a loop for I think 20 times. Unfortunately, CXF set the default
Authenticator to CXFAuthenticator wich provides the username/password on
every consecuting try.

For me there are two possible workarounds:
1) I can set Authenticator.setDefault(null) after CXF set it to
CXFAuthenticator
2) I can do httpConduit.setAuthorization(null) on my HttpConduit.

This doesn't prevent from authorization to work since it seems that CXF
sets
the right HTTP-Authorization-Request on the HttpUrlConnection before the
initial try. But when providing wrong credentials I'm getting the HTTP
401-Exception I would excpect.

I'm quite sure this was the default behavior on older cxf-versions. (we
startet with 2.2.2)

Isn't it bad style to try to authenticate over and over again with the
same
credentials? What is that CXFAuthenticator actually good for? And wich of
my
workarounds is actually "better"? Do they have side-effects I cannot see
at
the moment?


Best regards
Johannes

New Feature: support array request param types with ability to specify type
of array elements

Hi,

After building the Geronimo 3.0 trunk, I see some errors shown in Eclipse
when I import the projects into workspace. The following are few such.

1)
Error: The blank final field parameterTypes may not have been initialized
Source location: Line 82 in
geronimo-kernel/src/main/java/org/apache/geronimo/gbean/runtime/GBeanOperation.java

The source line is
                private String[] types = (String[])
parameterTypes.toArray(new String[parameterTypes.size()]);

Examining the source indicates that the field parameterTypes is very much
initialized. Also, there is no build error while building the project
using
maven.

2)
Error: The method getAllAppenders() is undefined for the type Logger
Source location: Line 342 in
geronimo-pax-logging/src/main/java/org/apache/geronimo/logging/impl/Log4jService.java

The source line is
        for (Enumeration e = Logger.getRootLogger().getAllAppenders();
e.hasMoreElements();) {

A similar error is shown with 7 other source lines in the same file

Any idea how to get rid of these errors shown in Eclipse?
I am using Eclipse Platform Version: 3.4.1 Build id: M20080911-1700 on
Windows XP SP3, with Sun JDK 1.6.0_20.

Hi there,

this is probably a real noob problem but I am experiencing an issue 
where whenever I try to create a document on CouchDB using curl, I get 
an "Invalid UTF-8 JSON" error. The example I am trying to use is 
actually from O'Reilly's book "CouchDB: The Definitive Guide" and I am 
pretty sure that I have tried it before and got it to work. Here's the 
command:

|curl-X PUT
http://username:pass### @127.0.0.1:59...e54cc05947f18c8af
-d '{"title":"There is Nothing Left to Lose","artist":"Foo Fighters"}'
|

The database albums exists and the username and password are correct. I 
have checked this with JSONLint and the JSON is valid and I am at a loss 
... presumably there is an issue with the CouchDB server itself but it 
appears to be running correctly ... any ideas? This is driving me nuts!

I am running CouchDB 0.11 on Windows 7. curl is installed and working 
correctly as far as I can tell. Sofa is working correctly and I can 
create documents via Sofa with no issues.

Thanks,

Andrew

.gitignore files being placed in test warehouse directories causing build
failure

JSON UDTF function

unmarshalling the JSON of a subclass fails when a field value is null

[Rumen] Do Not Store CDFs in Output JSON Files

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Felix Meschberger updated SLING-1132:

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Felix Meschberger resolved SLING-1132.

    [
https://issues.apache.org/jira/browse...0#action_12896020
] 

Michal Fojtik commented on DTACLOUD-1: