The following configuration solved the problem for me:

in $FEDORA_HOME/server/config/spring/web/web.properties,

set

security.ssl.api.management=ANY_CHANNEL

Found after a full day of inspecting the source code, because the  
error message was too unspecific. Why doesn't it tell me what kind of  
connection failed? When I try to ingest using http on port 80 (or  
8080), am I supposed to guess that an https connection to port 8433  
fails???

--Jörg Knappen


Zitat von Jörg Knappen <j.knap...@mx.uni-saarland.de>:

> Hallo,
>
> I have the following issue with ./fedora-ingest-demos.sh
>
> The general setup is:
>
> fedora-commons 3.5 is installed on existing Apache-Tomcat 7.0.25
> The database is mysql  Ver 14.12 Distrib 5.0.67, for suse-linux-gnu  
> (x86_64) using readline 5.2
> The database connection works fine (I can create objects and upload  
> datastreams for test objects)
>
> Apache-Tomcat is listening to port 8080 (only available from  
> localhost due to firewall setting)
> Apache-Tomcat is connected to an Apache-httpd-2.2.22 (brand new!)  
> via mod_proxy and ajp protocol to port 8009
> Apache-httpd is listening to port 80.
>
> java -version
> java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
>
> I watch the following behaviour:
>
> 1. Using Apache Tomcat on localhost directly:
> Correct password: ./fedora-ingest-demos.sh localhost 8080  
> fedoraAdmin ******** http fedora
> Failure with log file in client/logs as described below.
> Nothing is written to the server logs server/logs/fedora.log
>
> Wrong password ./fedora-ingest-demos.sh localhost 8080 fedoraAdmin  
> wrongpassword http fedora
> Failure with log file in client/logs, containing (401)Unauthorized
> 41 lines written to server/logs/fedora.log looking like
> ERROR 2012-01-31 17:15:57.755 [http-bio-8080-exec-13]  
> (AuthFilterJAAS) Anmeldefehler: Alle Module werden ignoriert
>
> 2. Using the indirection via Apache httpd:
> Correct password: ./fedora-ingest-demos.sh localhost 80 fedoraAdmin  
> ******** http fedora
> Failure with Segmentation Fault (Speicherzugriffsverletzung)
> Nothing is written to the server logs server/logs/fedora.log
>
> Wrong password ./fedora-ingest-demos.sh localhost 80 fedoraAdmin  
> wrongpassword http fedora
> Failure with log file in client/logs, containing (401)Unauthorized
> 41 lines written to server/logs/fedora.log looking like
> ERROR 2012-02-01 11:54:48.781 [ajp-bio-8009-exec-8] (AuthFilterJAAS)  
> Anmeldefehler: Alle Module werden ignoriert
>
> The operating system is SLES 11 (Suse Linux Enterpise Server) and --  
> as you can see -- issues error messages in german language.
>
> Google showed me that the isue has appeared several times before,  
> but I could not find a cure for the problem.
>
> Jörg Knappen
>
>> WARNING: 41 of 41 objects failed.  Check log.
>>
>> The log file in client/logs has
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <ingest-from-dir>
>> <failed  
>> file="/usr/local/fedora-commons/client/demo/foxml/local-server-demos/d
>> ocument-transform-demo/demo_XML_TO_HTMLDOC.xml">
>>   ; nested exception is:
>>       java.net.ConnectException: Connection refused
>> </failed>
>>
>
> Output from test with intentionally wrong password:
>> <ingest-from-dir>
>> <failed  
>> file="/usr/local/fedora-commons/client/demo/foxml/local-server-demos/d
>> ocument-transform-demo/demo_XML_TO_HTMLDOC.xml">
>>   (401)Unauthorized
>> </failed>
>>
>>
>
>




------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to