Return-Path: X-Original-To: apmail-syncope-user-archive@www.apache.org Delivered-To: apmail-syncope-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED2D2E2EC for ; Sat, 16 Feb 2013 11:14:25 +0000 (UTC) Received: (qmail 84647 invoked by uid 500); 16 Feb 2013 11:14:25 -0000 Delivered-To: apmail-syncope-user-archive@syncope.apache.org Received: (qmail 84483 invoked by uid 500); 16 Feb 2013 11:14:20 -0000 Mailing-List: contact user-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@syncope.apache.org Delivered-To: mailing list user@syncope.apache.org Received: (qmail 84443 invoked by uid 99); 16 Feb 2013 11:14:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2013 11:14:19 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [88.149.128.33] (HELO smtpi3.ngi.it) (88.149.128.33) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2013 11:14:10 +0000 Received: from [192.168.1.2] (78-134-111-69.v4.ngi.it [78.134.111.69]) by smtpi3.ngi.it (Postfix) with ESMTP id 2EA1F318212 for ; Sat, 16 Feb 2013 12:13:49 +0100 (CET) Message-ID: <511F69EC.3010909@apache.org> Date: Sat, 16 Feb 2013 12:13:48 +0100 From: =?UTF-8?B?RnJhbmNlc2NvIENoaWNjaGlyaWNjw7I=?= User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: user@syncope.apache.org Subject: Re: Run Syncope in embedded mode References: <511C99D8.7030209@apache.org> <511DCEAF.7050108@apache.org> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050902050803080200070407" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------050902050803080200070407 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 15/02/2013 20:49, Ömer Faruk AK wrote: > Thank you for information. > > Now i'm trying to run on ubuntu server at Apache Tomcat. I completed > your wiki exactly. But when i deploy syncope-console always gives > session expired error and for syncope application, tomcat web > application manager says /FAIL - Application at context path /syncope > could not be started/ When you say "your wiki", I guess you are referring to [1]. I'd suggest to first deploy syncope.war, and to take a look at Tomcat log files (mainly catalina.out) while deploying in order to catch the first exception during WAR deployment and provide necessary action. Problems in deploying Syncope core are often due to missing JDBC driver (did you put mysql-connector-java-XXXX.jar or the JDBC driver for your DBMS in Tomcat's classpath, e.g. under $CATALINA_HOME/lib, *before* starting Tomcat for deploying Syncope?) but can vary across many reasons. The error related to Syncope console is instead due to the fact that it cannot contact the Syncope core - in this case it could very well be because the Syncope core is just not available. Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments > If you can look my war files can be downloadable from this links; > > http://omerfarukak.com/syncope.war > http://omerfarukak.com/syncope-console.war -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/ --------------050902050803080200070407 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 15/02/2013 20:49, Ömer Faruk AK wrote:
Thank you for information.

Now i'm trying to run on ubuntu server at Apache Tomcat. I completed your wiki exactly. But when i deploy syncope-console always gives session expired error and for syncope application, tomcat web application manager says FAIL - Application at context path /syncope could not be started

When you say "your wiki", I guess you are referring to [1].

I'd suggest to first deploy syncope.war, and to take a look at Tomcat log files (mainly catalina.out) while deploying in order to catch the first exception during WAR deployment and provide necessary action.

Problems in deploying Syncope core are often due to missing JDBC driver (did you put mysql-connector-java-XXXX.jar or the JDBC driver for your DBMS in Tomcat's classpath, e.g. under $CATALINA_HOME/lib, *before* starting Tomcat for deploying Syncope?) but can vary across many reasons.

The error related to Syncope console is instead due to the fact that it cannot contact the Syncope core - in this case it could very well be because the Syncope core is just not available.

Regards.

[1] https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments

If you can look my war files can be downloadable from this links;

-- 
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/ 
--------------050902050803080200070407--