Re: [Opaltoolkit-users] Problem installing Opal 2.X

[Sriram K. <sr...@sd...>]

Note that version 1.9.5 didn't use Hibernate and HSQL - all Opal state  
was stored in memory, which was lost when Tomcat was restarted.

The HSQL files should be in $CATALINA_HOME/webapps/opal2/WEB-INF/ 
data/. Does that exist for you?

A good test would be install this in a fresh version of Tomcat. I just  
downloaded an Opal installation from SourceForge and installed it  
inside a fresh version of Tomcat 5.5.28, and did the exact same  
changes you did, and everything worked fine. It is possible that there  
may be some conflicts with other web applications deployed inside your  
Tomcat instance. If you can't get Opal installed on a vanilla fresh  
Tomcat, we can help you debug that.

Thanks,
Sriram

On Feb 4, 2010, at 4:31 PM, Conrad Huang wrote:

> I did not touch etc/hibernate-opal.cfg.xml.  The only two files from  
> the standard 2.2 distribution that I modified were etc/ 
> opal.properties and build.properties.  In opal.properties, the only  
> item I changed was "tomcat.url", which I set to be the same as on  
> 1.9.5.  The build.properties file for 1.9.5 and 2.2 are the same  
> except for "version".
>
> I guess I'm unclear on where the HSQL databases are for 1.9.5 and  
> 2.2 are.  On 1.9.5, in etc/opal.properties, I have
>
>  database.use=false
>
> On 2.2, in etc/hibernate-opal.cfg.xml, I have
>
>  <property name="connection.url">jdbc:hsqldb:file:data/opaldb</ 
> property>
>
> Where on the file system should these databases live, given these  
> settings?
>
> Thanks.
>
> Conrad
>
> On 2/4/10 4:08 PM, Sriram Krishnan wrote:
>> Hi Conrad,
>>
>> Just to elaborate on Jane's question - did you modify the
>> etc/hibernate-opal.cfg.xml as well? I would recommend default the
>> default configuration (i.e. using the HSQL database) first, and  
>> checking
>> if everything works out of the box.
>>
>> Once that works, you can try connecting to another database. Also  
>> note
>> that the database schemas for Opal 1.9.5 and Opal 2.X are  
>> different. So
>> if you are using the same database instance, please use a different
>> database name in the "connection.url".
>>
>> Let us know if that helps.
>> Sriram
>>
>> On Feb 4, 2010, at 3:19 PM, Jane Ren wrote:
>>
>>> Hi Conrad,
>>>
>>> Are you using the default database?
>>>
>>> Jane
>>> ________________________________________
>>> From: Conrad Huang [co...@cg...]
>>> Sent: Thursday, February 04, 2010 2:34 PM
>>> To: opa...@li...
>>> Subject: [Opaltoolkit-users] Problem installing Opal 2.X
>>>
>>> I've been using Opal 1.9.5 for a while and it works very well for  
>>> us.
>>> Now that 2.2 is out, I'd like to migrate to the newer version while
>>> keeping the old one up and running for legacy users. Following the
>>> instructions, I managed to get through "edit etc/opal.properties and
>>> build.properties" and "ant install", but starting tomcat at that  
>>> point
>>> generates the attached error log. The old 1.9.5 services are working
>>> fine, but services deployed for 2.2 generate similar exceptions  
>>> about
>>> "Connections could not be acquired from the underlying database!"  
>>> Can
>>> someone please point me towards where I went wrong? Thanks.
>>>
>>> Conrad
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> The Planet: dedicated and managed hosting, cloud storage, colocation
>>> Stay online with enterprise data centers and the best network in the
>>> business
>>> Choose flexible plans and management services without long-term  
>>> contracts
>>> Personal 24x7 support from experience hosting pros just a phone call
>>> away.
>>> http://p.sf.net/sfu/theplanet-com
>>> _______________________________________________
>>> Opaltoolkit-users mailing list
>>> Opa...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opaltoolkit-users
>>