Nabble - GORDA Community

Ws. on Dependable Distributed Data Management

2009-01-19T03:14:00Z

[We apologise if you receive multiple copies of this message. Please
forward this mail to anyone interested.]

*** Deadline extended: February 2, 2009 ***

Third Workshop on Dependable Distributed Data Management (WDDDM'2008)
affiliated with EuroSys 2009 Conference
March 31, 2009, Nuremberg, Germany

http://gsd.di.uminho.pt/wdddm09/

ABOUT

The goal of the workshop is to bring together researchers and practitioners
from systems, database and dependability communities to discuss the current
state of the art, pending challenges and trends, and novel solutions in the
design, implementation and deployment of distributed and dependable data
management systems.

SCOPE

Relational databases have been for a long time the keystone of information
systems' dependability. Database management systems offer a uniform
approach to data integrity, durability, and availability, using tried and
tested techniques based on a set of unanimously accepted and well
understood assumptions.

There is however a growing call for unprecedented levels of scalability
that challenges traditional data management architectures, namely, to cope
with cloud computing and peer-to-peer systems. A common principle in all
such emerging proposals, with a profound impact in dependability, is that
large scale distribution is a core assumption in their design. This
translates in very large number of nodes, wide area geographical
distribution, diverse administrative domains, and pervasive heterogeneity.
The current trend of specialized systems for social networking
applications, text indexing, data warehousing, stream processing, and
highly flexible data storage further push the envelope for radically
different data management solutions.

It is thus desirable to reevaluate time tested assumptions that underly the
dependability mechanisms in data management systems and explore different
performance and functionality tradeoffs, and the consequences on complex
information systems built on them.

TOPICS

The workshop targets research on databases systems, dependable, distributed
and mobile computing, distributed storage, management and security. Namely,
we seek contributions that tackle the following perceived challenges:

* Novel application scenarios, interface abstractions and consistency
requirements
* Scaling-out to very large number of nodes of data management
architectures and systems
* Software engineering for tailor-made data management
* Distributed and complex event processing systems
* System assumptions for dependability and performance
* Diversity and software reliability
* Self organizing data management systems

FORMAT

The workshop welcomes Short Position Papers with early and/or controversial
ideas that foster discussion but are not (yet) fully developed. Submissions
will not be refereed. They will be screened by the organizers for
relevance and accepted according to available presentation slots. The
maximum size is 4 pages in the ACM Conference Proceedings style.

Since submissions must strictly adhere to ACM Conference Proceedings style,
submitters are strongly encouraged to use the ACM SIG Proceedings
Templates. In order to get included in the EuroSys 2009 proceedings CD,
accepted contributions must be presented at the workshop and comply with
the ACM Copyright Policy.

IMPORTANT DATES

* Paper submission: February 2, 2009 (EXTENDED)
* Author notification: February 16, 2009
* Camera-ready due: March 2, 2009
* Workshop date: March 31, 2009

ORGANIZATION

Workshop Chairs:

* Calton Pu (Georgia Institute of Technology, USA)
* Martin Kersten (CWI, Netherlands)
* Rui Oliveira (U. Minho, Portugal)
* Paul Murray (HP Labs, UK)

Organizing Chair:

* José Pereira (U. Minho, Portugal)

ADDITIONAL INFORMATION

For more information visit the workshop web site or contact the
organizers at wdddm@....

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

replicate postgreSQL

2008-07-03T22:35:33Z

hi I am Jaimini Tiwari can any one tell me how to replicate data. I am using PostgreSQL 8.3 and Slony 1.2 i am new in postgreSQL.Please tell me in detail what packages should we install with postgreSQL for replication of database I am using Java in frontend please reply as soon as possible with tnx in advance

escada derby quickstart question

2008-04-23T01:43:56Z

hi

I tried to run escada derby example on windows xp but it didn't work.

>create-sample-databases.bat
Starting configuration for replica 1
eq was unexpected at this time.

Deadline extended: WDDDM (with EuroSys 2008)

2008-02-04T03:01:37Z

[We apologise if you receive multiple copies of this message. Please forward
this mail to anyone interested.]

Second Workshop on Dependable Distributed Data Management (WDDDM'2008)
affiliated with EuroSys 2008 Conference
March 31, 2008, Glasgow, Scotland

http://gorda.di.uminho.pt/wdddm08/

***** DEADLINE EXTENDED: Feburary 11, 2008 *****

ABOUT

The goal of the workshop is to bring together researchers and practitioners
from systems, database and dependability communities to discuss the current
state of the art, pending challenges and trends, and novel solutions in the
design, implementation and deployment of distributed and dependable data
management systems.

SCOPE

Relational databases have been for a long time the keystone of information
systems' dependability. Database management systems (DBMS) offer a uniform
approach to data integrity, durability, and availability, using tried and
tested techniques based on a set of unanimously accepted and well understood
assumptions.

However, the expectations on the DBMS itself are changing and there is an
unprecedented call for a complete rewrite: The general purpose relational DBMS
architecture dating back from the 70's is being convincingly challenged by a
number of specialized systems for text indexing, data warehousing, stream
processing, and array storage. Most strikingly, the winds of change are felt
even within the common enterprise data center, where the widespread need for
practical scale-out and near zero downtime translates to an increased appetite
for cheap and efficient consistent replication and for shared-nothing clusters
built on commodity hardware and software.

Novel peer-to-peer applications, grid computing, and the emergence of cloud
computing further push the envelope for radically different data management
solutions. A major trend in all such emerging proposals, with a profound
impact in dependability, is that large scale distribution is a core assumption
in their design. This translates in very large number of nodes, wide area
geographical distribution, diverse administrative domains, and pervasive
heterogeneity.

It is thus desirable to reevaluate time tested assumptions that underly the
dependability mechanisms in database management systems and explore different
performance and functionality tradeoffs. And explore the consequences on
complex information systems built on them.

TOPICS

Topics of interest to the workshop include, but are not limited to:

* System assumptions for dependability and performance
* Novel application scenarios and consistency requirements
* Scaling-out to very large number of nodes: peer-to-peer databases and
the data grid
* Autonomic versus orchestrated central control
* Diversity and software reliability

FORMAT

The workshop welcomes two kinds of contributions:

* Short position papers with early and/or controversial ideas that foster
discussion but are not (yet) fully developed. The maximum size is 4 pages
in the ACM Conference Proceedings style.

* Research papers which present mature original work. The maximum size
is 10 pages in the ACM Conference Proceedings style.

Since submissions must strictly adhere to ACM Conference Proceedings style,
submitters are strongly encouraged to use the ACM SIG Proceedings Templates.
In order to get included in the EuroSys 2008 proceedings CD, accepted
contributions must be presented at the workshop and comply with the ACM
Copyright Policy.

IMPORTANT DATES

* Paper submission: February 11, 2008 (extended)
* Author notification: February 25, 2008
* Camera-ready due: March 15, 2008
* Workshop date: March 31, 2008

ORGANIZATION

Program Chairs:

* Calton Pu (Georgia Institute of Technology, USA)
* Martin Kersten (CWI, Netherlands)
* Rui Oliveira (U. Minho, Portugal)

Organizing Chair:

* José Pereira (U. Minho, Portugal)

Programme Committee:

* Gustavo Alonso (ETHZ, Switzerland)
* Enrique Armendariz (U. P. Navarra, Spain)
* Ken Birman (U. Cornell, USA)
* Andrea Bondavalli (U. Firenzi, Italy)
* Emmanuel Cecchet (EPFL, Switzerland)
* Alan Fekete (U. Sidney, Australia)
* Roy Friedman (Technion, Israel)
* Karl Goeschka (Vienna Institute of Technology, Austria)
* Ricardo Jiménez-Peris (U. P. Madrid, Spain)
* Flávio Junqueira (Yahoo!, Spain)
* Raimundo Macêdo (U. F. Bahia, Brazil)
* Henrique Madeira (U. Coimbra, Portugal)
* Fernando Pedone (U. Lugano, Switzerland)
* Luís Rodrigues (IST, Portugal)
* Antony Rowstron (Microsoft, UK)
* Doug Terry (Microsoft, USA)
* Patrick Valduriez (U. Nantes, France)
* Maarten Van Steen (Vrije U., Netherlands)
* Haruo Yokota (Tokyo Institute of Technology, Japan)

ADDITIONAL INFORMATION

For more information visit the workshop web site or contact the organizers at
wdddm@....

--
Jose Orlando Pereira

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re: getting escada-0.5-quickstart-derby demo to work

2008-01-17T10:12:45Z

Hi,

sorry about the late response.

Try using this connection command in the ij console:

ij> connect 'jdbc:derby://localhost:1527/test';

where 1527 is the derby connection port of one of the replicas.

Cheers,
nuno

On Jan 14, 2008, at 5:42 PM, buzz lightyear wrote:

>
> Hi Nuno
>
> I've installed and created replication instances.
>
> I've started the instances with startNetworkServer.ksh pb
>
> With all of the instances running, I've tried to use ij but always
> get the following error ....
>
> replica-1$ ij.ksh
> ij> connect 'jdbc:derby:test';
> ERROR XJ040: Failed to start database 'test', see the next exception
> for details.
> ERROR XSDB6: Another instance of Derby may have already booted the
> database /home/nick/tmp/escada-0.5-quickstart-derby/replica-1/test.
>
>
> One other thing - the install script for the test doesn't update the
> jmx and servlet ports for the additional instances. I updated
> (incremented) these by hand but I don't know if this is the reason
> for ij failing?
>
> Sorry for all of these beginner issues!
>
> Cheers
> Nick
> _________________________________________________________________
> Who's friends with who and co-starred in what?
> http://www.searchgamesbox.com/celebrityseparation.shtml

Nuno Carvalho

INESC-ID/IST
http://www.gsd.inesc-id.pt/~nonius/

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

CFP: Ws. Dependable Distributed Data Management (with EuroSys 2008)

2008-01-15T06:09:30Z

[We apologise if you receive multiple copies of this message. Please forward
this mail to anyone interested.]

Second Workshop on Dependable Distributed Data Management (WDDDM'2008)
affiliated with EuroSys 2008 Conference
March 31, 2008, Glasgow, Scotland

http://gorda.di.uminho.pt/wdddm08/

ABOUT

The goal of the workshop is to bring together researchers and practitioners
from systems, database and dependability communities to discuss the current
state of the art, pending challenges and trends, and novel solutions in the
design, implementation and deployment of distributed and dependable data
management systems.

SCOPE

Relational databases have been for a long time the keystone of information
systems' dependability. Database management systems (DBMS) offer a uniform
approach to data integrity, durability, and availability, using tried and
tested techniques based on a set of unanimously accepted and well understood
assumptions.

However, the expectations on the DBMS itself are changing and there is an
unprecedented call for a complete rewrite: The general purpose relational DBMS
architecture dating back from the 70's is being convincingly challenged by a
number of specialized systems for text indexing, data warehousing, stream
processing, and array storage. Most strikingly, the winds of change are felt
even within the common enterprise data center, where the widespread need for
practical scale-out and near zero downtime translates to an increased appetite
for cheap and efficient consistent replication and for shared-nothing clusters
built on commodity hardware and software.

Novel peer-to-peer applications, grid computing, and the emergence of cloud
computing further push the envelope for radically different data management
solutions. A major trend in all such emerging proposals, with a profound
impact in dependability, is that large scale distribution is a core assumption
in their design. This translates in very large number of nodes, wide area
geographical distribution, diverse administrative domains, and pervasive
heterogeneity.

It is thus desirable to reevaluate time tested assumptions that underly the
dependability mechanisms in database management systems and explore different
performance and functionality tradeoffs. And explore the consequences on
complex information systems built on them.

TOPICS

Topics of interest to the workshop include, but are not limited to:

* System assumptions for dependability and performance
* Novel application scenarios and consistency requirements
* Scaling-out to very large number of nodes: peer-to-peer databases and
the data grid
* Autonomic versus orchestrated central control
* Diversity and software reliability

FORMAT

The workshop welcomes two kinds of contributions:

* Short position papers with early and/or controversial ideas that foster
discussion but are not (yet) fully developed. The maximum size is 4 pages
in the ACM Conference Proceedings style.

* Research papers which present mature original work. The maximum size
is 10 pages in the ACM Conference Proceedings style.

Since submissions must strictly adhere to ACM Conference Proceedings style,
submitters are strongly encouraged to use the ACM SIG Proceedings Templates.
In order to get included in the EuroSys 2008 proceedings CD, accepted
contributions must be presented at the workshop and comply with the ACM
Copyright Policy.

IMPORTANT DATES

* Paper submission: February 1, 2008
* Author notification: February 25, 2008
* Camera-ready due: March 15, 2008
* Workshop date: March 31, 2008

ORGANIZATION

Program Chairs:

* Calton Pu (Georgia Institute of Technology, USA)
* Martin Kersten (CWI, Netherlands)
* Rui Oliveira (U. Minho, Portugal)

Organizing Chair:

* José Pereira (U. Minho, Portugal)

Programme Committee:

* Gustavo Alonso (ETHZ, Switzerland)
* Enrique Armendariz (U. P. Navarra, Spain)
* Ken Birman (U. Cornell, USA)
* Andrea Bondavalli (U. Firenzi, Italy)
* Emmanuel Cecchet (EPFL, Switzerland)
* Alan Fekete (U. Sidney, Australia)
* Roy Friedman (Technion, Israel)
* Karl Goeschka (Vienna Institute of Technology, Austria)
* Ricardo Jiménez-Peris (U. P. Madrid, Spain)
* Flávio Junqueira (Yahoo!, Spain)
* Raimundo Macêdo (U. F. Bahia, Brazil)
* Henrique Madeira (U. Coimbra, Portugal)
* Fernando Pedone (U. Lugano, Switzerland)
* Luís Rodrigues (IST, Portugal)
* Antony Rowstron (Microsoft, UK)
* Doug Terry (Microsoft, USA)
* Patrick Valduriez (U. Nantes, France)
* Maarten Van Steen (Vrije U., Netherlands)
* Haruo Yokota (Tokyo Institute of Technology, Japan)

ADDITIONAL INFORMATION

For more information visit the workshop web site or contact the organizers at
wdddm@....

--
Jose Orlando Pereira

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re: escada recovery mode for derby

2008-01-14T12:56:54Z

Sorry about the previous email.
Please, ignore it.

Best regards
Alfranio.

> Essa atividade estava com o Miguel.
> Nao sei dizer como ficou mas na terca olhamos isso tambem.
>

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re: escada recovery mode for derby

2008-01-14T12:52:07Z

Essa atividade estava com o Miguel.
Nao sei dizer como ficou mas na terca olhamos isso tambem.

>
> I cannot commit on a date right now, but we will meet soon and we will
> discuss when these things will be implemented and integrated.
> We can give some new after.
>
> Thanks for your interest in the GORDA project,
> Nuno
>
> On Jan 14, 2008, at 3:07 PM, buzz lightyear wrote:
>
>>
>> Hi Nuno
>>
>> Do you have any idea whether you guys will be implementing recovery
>> support for derby in escada .... the README in the escada-dergy-
>> quickstart (0.5) states that this is one of the current limitations
>>
>> Cheers
>>
>> Nick
>> _________________________________________________________________
>> Telly addicts unite!
>> http://www.searchgamesbox.com/tvtown.shtml
>> -----------------------------------------------------------------------
>> List info/archive at: http://www.nabble.com/GORDA-Community-
>> f25582.html
>> GORDA software and documentation: http://gorda.di.uminho.pt
>>
>>
>
>
> -----------------------------------------------------------------------
> List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
> GORDA software and documentation: http://gorda.di.uminho.pt
>
>

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re: escada recovery mode for derby

2008-01-14T10:59:35Z

Hi,

I cannot commit on a date right now, but we will meet soon and we will
discuss when these things will be implemented and integrated.
We can give some new after.

Thanks for your interest in the GORDA project,
Nuno

On Jan 14, 2008, at 3:07 PM, buzz lightyear wrote:

>
> Hi Nuno
>
> Do you have any idea whether you guys will be implementing recovery
> support for derby in escada .... the README in the escada-dergy-
> quickstart (0.5) states that this is one of the current limitations
>
> Cheers
>
> Nick
> _________________________________________________________________
> Telly addicts unite!
> http://www.searchgamesbox.com/tvtown.shtml
> -----------------------------------------------------------------------
> List info/archive at: http://www.nabble.com/GORDA-Community-
> f25582.html
> GORDA software and documentation: http://gorda.di.uminho.pt
>
>

getting escada-0.5-quickstart-derby demo to work

2008-01-14T09:42:25Z

Hi Nuno

I've installed and created replication instances.

I've started the instances with startNetworkServer.ksh pb

With all of the instances running, I've tried to use ij but always get the following error ....

replica-1$ ij.ksh
ij> connect 'jdbc:derby:test';
ERROR XJ040: Failed to start database 'test', see the next exception for details.
ERROR XSDB6: Another instance of Derby may have already booted the database /home/nick/tmp/escada-0.5-quickstart-derby/replica-1/test.

One other thing - the install script for the test doesn't update the jmx and servlet ports for the additional instances. I updated (incremented) these by hand but I don't know if this is the reason for ij failing?

Sorry for all of these beginner issues!

Cheers
Nick
_________________________________________________________________
Who's friends with who and co-starred in what?
http://www.searchgamesbox.com/celebrityseparation.shtml
-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

escada recovery mode for derby

2008-01-14T07:07:15Z

Hi Nuno

Do you have any idea whether you guys will be implementing recovery support for derby in escada .... the README in the escada-dergy-quickstart (0.5) states that this is one of the current limitations

Cheers

Nick
_________________________________________________________________
Telly addicts unite!
http://www.searchgamesbox.com/tvtown.shtml
-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re:

2008-01-14T02:33:54Z

Hi Nick,

the maximum payload size is just imposed by the underlying
implementation, not the interface. The Appia (and I think JGroups
also) do not impose a maximum size, but Spread has a maximum message
size.

Cheers,
Nuno

On Jan 14, 2008, at 9:34 AM, buzz lightyear wrote:

>
> Hi Nuno
>
> Just a quick question about jgcs .... is there a maximum payload
> size for net.sf.jgcs.Message. I have a maximum payload size of 16k
> bytes for the binding I'm writing. If the payload can be greater
> than this, is there any way of defining a limit on the message size?
> (I'm currently writing this for escada, perhaps escada is able to
> set this limit?)
>
> Cheers
> Nick
> _________________________________________________________________
> Free games, great prizes - get gaming at Gamesbox.
> http://www.searchgamesbox.com

Re: Escada Quickstart Howto (Updated - version 0.5)

2007-12-10T10:01:35Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear all,

Actually the Howto posted is the full howto to the escada
replicator, and we decided to place it under the main wiki page, under
the section "ESCADA Howto":
* http://escada.wiki.sourceforge.net/

The howto on the quickstart is available at the original location:
* http://escada.sourceforge.net/quickstart.html

Regards,
Luís

On 2007/12/10, at 16:53, Luís Soares wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Dear all,
>
> you may find an updated howto on escada quickstart (0.5 version -
> derby quickstart) at:
> * http://escada.wiki.sourceforge.net/Apache+Derby
>
> Regards,
> Luís
>
> - ---
> Luís Soares
> * los@... * http://gsd.di.uminho.pt/members/los *
> * gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 *
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
>
> iD8DBQFHXW79GXhsZeZ4wiMRAq66AJ9t6d+tvWrLMYIXGMG/dBUVLhMXQQCeL43B
> D/fB4MAa/9RdBHMt0Inxv/Q=
> =bf8w
> -----END PGP SIGNATURE-----
>
> -----------------------------------------------------------------------
> List info/archive at: http://www.nabble.com/GORDA-Community-
> f25582.html
> GORDA software and documentation: http://gorda.di.uminho.pt
>

- ---
Luís Soares
* los@... * http://gsd.di.uminho.pt/members/los *
* gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 *

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHXX7/GXhsZeZ4wiMRAmQrAJwOsb7PuxEtW5itMHgj/ALLqYy1ZwCdHJLA
FRPErLAILGfeo/h3GECNv2E=
=w/oU
-----END PGP SIGNATURE-----

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Escada Quickstart Howto (Updated - version 0.5)

2007-12-10T08:53:17Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear all,

you may find an updated howto on escada quickstart (0.5 version -
derby quickstart) at:
* http://escada.wiki.sourceforge.net/Apache+Derby

Regards,
Luís

- ---
Luís Soares
* los@... * http://gsd.di.uminho.pt/members/los *
* gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 *

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHXW79GXhsZeZ4wiMRAq66AJ9t6d+tvWrLMYIXGMG/dBUVLhMXQQCeL43B
D/fB4MAa/9RdBHMt0Inxv/Q=
=bf8w
-----END PGP SIGNATURE-----

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

ESCADA Replication Server 0.5 released

2007-12-07T10:11:00Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are pleased to announce that release 0.5 of the ESCADA Replication
Server is now available at:

http://escada.sourceforge.net

This is still an alpha release and no significant features have been
introduced since 0.4. However:

* JMX interfaces to monitor/administer ESCADA are now much improved
and available through a regular jconsole instance;

* performance was improved;

* several bugs were fixed;

* basic web management console using embedded jetty and wicket web
framework.

The next release is scheduled for the 1Q of 2008, including
propagation of DDL statements as well as WICE and ACARA replication
protocols.

Best regards,
Luís

- ---
Luís Soares
* los@... * http://gsd.di.uminho.pt/members/los *
* gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 *

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHWYy0GXhsZeZ4wiMRAh89AKCpgAn+PDaDv45Rjw569EPcmLYXoACgqDXA
Zlkw/dMU2NNmWflw5h3Euh0=
=/Po5
-----END PGP SIGNATURE-----

-----------------------------------------------------------------------
List info/archive at: http://www.nabble.com/GORDA-Community-f25582.html
GORDA software and documentation: http://gorda.di.uminho.pt

Re: derby demos

2007-12-04T06:02:38Z

Hi Nick,

yes, actually, the 0.3 version does not contain the demos, since
escada is already very stable and became a demo it self and the simple
demos should not be implementation specific. This contains only the
derby implementation of gapi.

Thanks for letting us know about the broken link. It will be solved
ASAP.

The release announcement will be made through the mailing list. Please
stay tuned :-)

Thanks for your feedback,
Nuno

On Dec 4, 2007, at 12:05 PM, buzz lightyear wrote:

>
> Hi Nuno
>
> Thanks for the reply.
>
> Actually, the demo code isn't available via your links or gorda web
> pages. I finally found some old examples by going directly to http://gorda.di.uminho.pt/community/download
> and downloading an old derby-g-0.2.tgz and the gorda-
> interfaces-0.3.zip. The gorda-interfaces-0.3.zip had the gorda demos
> and the derby-g-0.2.tgz contained the derby related demo code. The
> 'tutorial examples' link from http://gorda.di.uminho.pt/community/gapi
> (http://gorda.di.uminho.pt/download/gapi-demos-0.4.tar.gz) doesn't
> exist.
>
> I'm certainly looking forward to your next release. My work starts
> on this tomorrow after I've finished up with my transaction
> processor - I hope that I will be able to plug this in to gorda
>
> Thanks again
>
> Nick
>
> ----------------------------------------
>> CC: community@...
>> From: nonius@...
>> To: buzzheavyyear@...
>> Subject: Re: derby demos
>> Date: Tue, 4 Dec 2007 11:22:59 +0000
>>
>> Hi Nick,
>>
>> sorry about the late response. The source code of derby/G is
>> available
>> here:
>> http://gorda.di.uminho.pt/community/derbyg/
>>
>> we are working on a new version that includes the upgrade to derby
>> 10.3 and transactions with priorities. It will be available in
>> January. Your feedback is welcome.
>>
>> regards,
>> Nuno
>>
>> On Nov 30, 2007, at 3:26 PM, buzzc4nfw wrote:
>>
>>>
>>> It really has been a long week - I have found the compiled classes
>>> in the
>>> gapi interfaces which come with escada
>>> :gapi-derby-10.2.2.0-20070731.172038-1.jar and the examples are in
>>> gorda.reflector.derby.demo
>>>
>>> But no source.
>>>
>>> Is there any chance that someone could make the demo sources
>>> available?
>>>
>>> Thanks
>>>
>>> Nick
>>>
>>>
>>>
>>> buzzc4nfw wrote:
>>>>
>>>> Sorry - the demos are in the interfaces package - it's been a long
>>>> week!
>>>>
>>>> Have a good weekend
>>>>
>>>> Nick
>>>>
>>>>
>>>>
>>>>
>>>> buzzc4nfw wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Finally managed to get back to this!
>>>>>
>>>>> I've been reading the howto-derbyG.pdf - the demos that are
>>>>> mentioned are
>>>>> not in derby-g-0.3.zip.
>>>>>
>>>>> Is there any way I can get my hands on them? Perhaps the next
>>>>> release
>>>>> will contain them?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Nick
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/derby-demos-tf4914532s25582.html#a14072083
>>> Sent from the GORDA Community mailing list archive at Nabble.com.
>>>
>>>
>>> -----------------------------------------------------------------------
>>> List info/archive at: http://www.nabble.com/GORDA-Community-
>>> f25582.html
>>> GORDA software and documentation: http://gorda.di.uminho.pt
>>>
>>>
>>
>
> _________________________________________________________________
> The next generation of MSN Hotmail has arrived - Windows Live Hotmail
> http://www.newhotmail.co.uk

Re: derby demos

2007-12-04T03:22:59Z

Hi Nick,

sorry about the late response. The source code of derby/G is available
here:
http://gorda.di.uminho.pt/community/derbyg/

we are working on a new version that includes the upgrade to derby
10.3 and transactions with priorities. It will be available in
January. Your feedback is welcome.

regards,
Nuno

On Nov 30, 2007, at 3:26 PM, buzzc4nfw wrote:

>
> It really has been a long week - I have found the compiled classes
> in the
> gapi interfaces which come with escada
> :gapi-derby-10.2.2.0-20070731.172038-1.jar and the examples are in
> gorda.reflector.derby.demo
>
> But no source.
>
> Is there any chance that someone could make the demo sources
> available?
>
> Thanks
>
> Nick
>
>
>
> buzzc4nfw wrote:
>>
>> Sorry - the demos are in the interfaces package - it's been a long
>> week!
>>
>> Have a good weekend
>>
>> Nick
>>
>>
>>
>>
>> buzzc4nfw wrote:
>>>
>>> Hi
>>>
>>> Finally managed to get back to this!
>>>
>>> I've been reading the howto-derbyG.pdf - the demos that are
>>> mentioned are
>>> not in derby-g-0.3.zip.
>>>
>>> Is there any way I can get my hands on them? Perhaps the next
>>> release
>>> will contain them?
>>>
>>> Thanks
>>>
>>> Nick
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/derby-demos-tf4914532s25582.html#a14072083
> Sent from the GORDA Community mailing list archive at Nabble.com.
>
>
> -----------------------------------------------------------------------
> List info/archive at: http://www.nabble.com/GORDA-Community-
> f25582.html
> GORDA software and documentation: http://gorda.di.uminho.pt
>
>

Re: derby demos

2007-11-30T07:26:32Z

It really has been a long week - I have found the compiled classes in the gapi interfaces which come with escada :gapi-derby-10.2.2.0-20070731.172038-1.jar and the examples are in gorda.reflector.derby.demo

But no source.

Is there any chance that someone could make the demo sources available?

Thanks

Nick

Sorry - the demos are in the interfaces package - it's been a long week!

Have a good weekend

Nick

buzzc4nfw wrote:

Hi

Finally managed to get back to this!

I've been reading the howto-derbyG.pdf - the demos that are mentioned are not in derby-g-0.3.zip.

Is there any way I can get my hands on them? Perhaps the next release will contain them?

Thanks

Nick

Re: derby demos

2007-11-30T07:09:15Z

Sorry - the demos are in the interfaces package - it's been a long week!

Have a good weekend

Nick

buzzc4nfw wrote:

Hi

Finally managed to get back to this!

I've been reading the howto-derbyG.pdf - the demos that are mentioned are not in derby-g-0.3.zip.

Is there any way I can get my hands on them? Perhaps the next release will contain them?

Thanks

Nick

derby demos

2007-11-30T06:52:59Z

Hi

Finally managed to get back to this!

I've been reading the howto-derbyG.pdf - the demos that are mentioned are not in derby-g-0.3.zip.

Is there any way I can get my hands on them? Perhaps the next release will contain them?

Thanks

Nick

RE: escada and jgcs

2007-09-21T09:25:58Z

Hi Jose

If you are saying what I think you are saying then it's certainly fine by me. All that needs to be known is that works running on top of escada won't be subject to patent or copyright issues.

Thanks

Cheers
Nick

.. and thanks for mentioning the safe mode.

> From: jop@...
> To: buzzheavyyear@...
> Subject: Re: escada and jgcs
> Date: Fri, 21 Sep 2007 16:11:05 +0100
> CC: community@...; nunomrc@...
>
> On Friday 21 September 2007, buzz lightyear wrote:
> > Thanks for the reference to the paper - when using jxta I'm having to take
> > into account node failure and clients are generally aware of which nodes
> > have the database - jxta is pretty good at discovery. This idea is to
> > ensure that clients connect to the 'best' connection at the time an
> > operation is invoked. The 'load balancing' is effectively taking place on
> > the client side.
>
> I understand. You should definitely take a look at the paper and think about
> the best solution for you: Enforcing some client affinity or using ESCADA in
> the proposed safe mode, which does however have an impact in read only
> transactions.
>
> > The license is an issue do to the fact that customers may construct
> > standalone applications using my libraries, your libraries and all the
> > other libraries which they might pass onto their clients. Some customers
> > may not not want to make public the source of their application. Other
> > customers may be overlook the gpl issue, distribute an application without
> > source and be unaware that they are contravening escadas license terms, and
> > as a consequence be liable. All of the libraries I'm using, including my
> > own (once they are ready), hibernate, jboss, jxta, derby etc have at worst
> > the lgpl license, and at best the apache license.
> >
> > I dearly hope we can resolve this licensing issue.
>
> IANAL, but the client application cannot be considered a derived work from
> ESCADA and thus is exempt from any licensing restrictions imposed by ESCADA.
> Let me try to explain this.
>
> Actually, this is a _major_advantage_ of the GORDA approach: replication is
> implemented by intercepting requests within the DBMS and not within the
> client application. This allows the client application (ditto JBoss,
> hibernate) to link to the original unmodified JDBC driver. No linking to
> ESCADA code is done. Besides technically interesting this should also solve
> any licensing issues.
>
> Licensing issues might arise only when linking ESCADA to the DBMS, since the
> resulting replicated DBMS is a derived work from both ESCADA and the DBMS.
> This is why we chose GPLv3, which unlike GPLv2 is compatible with Apache 2.0
> license, hence with Derby or Sequoia. There are also no problems when linking
> GPLv3 with modified-BSD licenses, hence with PostgreSQL.
>
> Moreover, like Apache License 2.0, GPLv3 should also be safer when
> redistributing code for money regarding possible patent claims.
>
> I hope this clears the licensing issue,
>
> --
> Jose Orlando Pereira

The next generation of MSN Hotmail has arrived - Windows Live Hotmail

Re: escada and jgcs

2007-09-21T09:11:05Z

On Friday 21 September 2007, buzz lightyear wrote:
> Thanks for the reference to the paper - when using jxta I'm having to take
> into account node failure and clients are generally aware of which nodes
> have the database - jxta is pretty good at discovery. This idea is to
> ensure that clients connect to the 'best' connection at the time an
> operation is invoked. The 'load balancing' is effectively taking place on
> the client side.

I understand. You should definitely take a look at the paper and think about
the best solution for you: Enforcing some client affinity or using ESCADA in
the proposed safe mode, which does however have an impact in read only
transactions.

> The license is an issue do to the fact that customers may construct
> standalone applications using my libraries, your libraries and all the
> other libraries which they might pass onto their clients. Some customers
> may not not want to make public the source of their application. Other
> customers may be overlook the gpl issue, distribute an application without
> source and be unaware that they are contravening escadas license terms, and
> as a consequence be liable. All of the libraries I'm using, including my
> own (once they are ready), hibernate, jboss, jxta, derby etc have at worst
> the lgpl license, and at best the apache license.
>
> I dearly hope we can resolve this licensing issue.

IANAL, but the client application cannot be considered a derived work from
ESCADA and thus is exempt from any licensing restrictions imposed by ESCADA.
Let me try to explain this.

Actually, this is a _major_advantage_ of the GORDA approach: replication is
implemented by intercepting requests within the DBMS and not within the
client application. This allows the client application (ditto JBoss,
hibernate) to link to the original unmodified JDBC driver. No linking to
ESCADA code is done. Besides technically interesting this should also solve
any licensing issues.

Licensing issues might arise only when linking ESCADA to the DBMS, since the
resulting replicated DBMS is a derived work from both ESCADA and the DBMS.
This is why we chose GPLv3, which unlike GPLv2 is compatible with Apache 2.0
license, hence with Derby or Sequoia. There are also no problems when linking
GPLv3 with modified-BSD licenses, hence with PostgreSQL.

Moreover, like Apache License 2.0, GPLv3 should also be safer when
redistributing code for money regarding possible patent claims.

I hope this clears the licensing issue,

--
Jose Orlando Pereira

smime.p7s (2K) Download Attachment

RE: escada and jgcs

2007-09-21T08:43:27Z

Hi Jose

Thanks for the reference to the paper - when using jxta I'm having to take into account node failure and clients are generally aware of which nodes have the database - jxta is pretty good at discovery. This idea is to ensure that clients connect to the 'best' connection at the time an operation is invoked. The 'load balancing' is effectively taking place on the client side.

The license is an issue do to the fact that customers may construct standalone applications using my libraries, your libraries and all the other libraries which they might pass onto their clients. Some customers may not not want to make public the source of their application. Other customers may be overlook the gpl issue, distribute an application without source and be unaware that they are contravening escadas license terms, and as a consequence be liable. All of the libraries I'm using, including my own (once they are ready), hibernate, jboss, jxta, derby etc have at worst the lgpl license, and at best the apache license.

I dearly hope we can resolve this licensing issue.

As for the client node and load balancing, I think that this is going to need some more thought.

Cheers
Nick

> From: jop@...
> To: community@...
> Subject: Re: Fwd: escada and jgcs
> Date: Fri, 21 Sep 2007 13:54:08 +0100
> CC: nunomrc@...; buzzheavyyear@...
>
> On Friday 21 September 2007, Nuno Carvalho wrote:
> > From: buzz lightyear <buzzheavyyear@...>
> > Date: September 21, 2007 1:25:47 PM GMT+02:00
> > To: Nuno Carvalho <nunomrc@...>
> > Subject: RE: escada and jgcs
> >
> > My problem still exists with the gpl license, though. Unless someone is
> > able to change this to lgpl then I'm stuck.
>
> Can you elaborate on this? Do you a specific license compatibility problem?
>
> > Incedently, did you have any thoughts re. hibernates second level cache and
> > gorda/escada?
>
> Using a DBMS replicated with ESCADA should not cause any trouble for an
> application level cache that wouldn't exist with a single non-replicated DBMS
> backend. The only requirement is that you enforce client affinity: the same
> client should not use more than one replica unless a server fails. This
> shouldn't be an issue unless you use some sort of load balancer in between.
> For more details check this paper:
>
> http://portal.acm.org/citation.cfm?id=1141277.1141442
>
> Regards,
>
> --
> Jose Orlando Pereira

Are you the Quizmaster? Play BrainBattle with a friend now!

Re: Fwd: escada and jgcs

2007-09-21T06:54:08Z

On Friday 21 September 2007, Nuno Carvalho wrote:
> From: buzz lightyear <buzzheavyyear@...>
> Date: September 21, 2007 1:25:47 PM GMT+02:00
> To: Nuno Carvalho <nunomrc@...>
> Subject: RE: escada and jgcs
>
> My problem still exists with the gpl license, though. Unless someone is
> able to change this to lgpl then I'm stuck.

Can you elaborate on this? Do you a specific license compatibility problem?

> Incedently, did you have any thoughts re. hibernates second level cache and
> gorda/escada?

Using a DBMS replicated with ESCADA should not cause any trouble for an
application level cache that wouldn't exist with a single non-replicated DBMS
backend. The only requirement is that you enforce client affinity: the same
client should not use more than one replica unless a server fails. This
shouldn't be an issue unless you use some sort of load balancer in between.
For more details check this paper:

http://portal.acm.org/citation.cfm?id=1141277.1141442

Regards,

--
Jose Orlando Pereira

smime.p7s (2K) Download Attachment

Fwd: escada and jgcs

2007-09-21T06:41:47Z

(resent to be stored in the archives mailing list)

Begin forwarded message:

From: buzz lightyear <buzzheavyyear@...>
Date: September 21, 2007 1:25:47 PM GMT+02:00
To: Nuno Carvalho <nunomrc@...>
Subject: RE: escada and jgcs

Hi Nuno

Apologies - my misunderstanding - yes, jxta would simply be another protocol under jGCS.

My problem still exists with the gpl license, though. Unless someone is able to change this to lgpl then I'm stuck.

Incedently, did you have any thoughts re. hibernates second level cache and gorda/escada?

One last thing - I got a failure notice when I tried to email to community@...

Cheers
Nick
CC: community@...; jop@...
From: nunomrc@...
Subject: Re: escada and jgcs
Date: Fri, 21 Sep 2007 12:15:02 +0200
To: buzzheavyyear@...

Hi Nick,

On Sep 19, 2007, at 11:52 , buzz lightyear wrote:

I have just gone over what I was trying to do in July and realise that it will be much easier to implement any replication with jxta via tcp streams, and then stream over jxta ..... there are so many ways to configure jxta that coming up with an escada framework for jxta might just frustrate many users

I don't know JXTA very well, but I got the impression that it is a communication infrastructure. Escada is more than that, it uses a communication infrastructure (through jGCS) and does database replication using also the GAPI interface on the databases. It contains protocols such as primary-backup and DBSM, recovery, etc.

I'm not sure what do you want to do, but JXTA and Escada are not comparable.

At the beginning of the week I tried to build derby-g-0.3 and was unable to do it. I followed the instructions and ran into problems via a unix shell - I have posted this issue to your forum and hope that someone might be able to respond.

I just answered that email. Sorry for the delay, we were all traveling for a demo of the GORDA project.

I also tried to build via netbeans which showed further problems of requiring xalan in the the gorda reflection api - xalan, I think, isn't mentioned in the build instructions.

I can build with eclipse... and I do not remember for the need for xalan on the derby implementation of GAPI. xalan is needed by Derby and not by the GORDA patch to implement GAPI (gorda reflection interface). The docs only refer to the things needed by this patch.

One last thing - is there any possibility that the escada interface might be set as an apache license instead of gnu - I am unable to use gnu, and consequently escada. If just the interface was set as apache then I would be able to do my own implementation.

Are you talking about the jGCS interface or the GAPI interface?
I do not manage this king of issues, I added José Pereira on Cc to clarify us about that.

Kind regards,

nuno

From: Nuno Carvalho <nunomrc@...>
To: buzz lightyear <buzzheavyyear@...>
CC: alfranio correia <alfranio@...>,José Orlando Pereira <jop@...>
Subject: Re: escada and jgcs
Date: Fri, 6 Jul 2007 13:27:54 +0100

Hi Nick,

On Jul 6, 2007, at 11:34 , buzz lightyear wrote:

I don't know if you/others have investigated Jxta as a possible jgcs binding - the current code doesn't make it easy for Jxta to be implemented.

No, not yet.

However, if SocketAddress is somehow embedded in a (for example) 'Member' interface then the Jxta IDs - there are two primary user types for peer and peergroup - can also be embedded within a Member interface, as jxta does reference sockets directly.

I'm not sure if you need this.

Since SocketAddress is an abstract class, you can do something like this:

public class JxtaPeer extends SocketAddress {
Member id;
}

The addresses in Spread are Strings and it works perfectly. You can take a look at the Spread binding (available for download in the SF) to see how we handle this. jGCS is supposed to be as generic as possible, so we use Java standard interfaces and abstract where possible.

With jGCS you should also be able to reuse native classes of the toolkit that you want to use for implementing jGCS. For example, the Appia binding does something like this:

public class AppiaMessage extends appia.Message implements jgcs.Message {
(...)
}

The messages are created and sent directly to the toolkit without any conversion overhead.

I suspect that I will press ahead soon and modify a local version of escada/jgcs. Would you be interested in me sending you anything I do? I would be unable to update and verify the jgroups and other bindings as I don't know them. However, the abstraction of SocketAddress into a Member class should make this relatively easy for all bindings.

Great! You are welcome to send anything that you have. You can also expect our help on problems and/or questions you may have.

Hope this helps,
--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

_________________________________________________________________
The next generation of Hotmail is here! http://www.newhotmail.co.uk

--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

Do you know a place like the back of your hand? Share local knowledge with BackOfMyHand.com

Nuno Carvalho

University of Lisbon, Portugal

http://lasige.di.fc.ul.pt/~ncarvalho

Fwd: escada and jgcs

2007-09-21T06:40:41Z

(resent to be stored in the archives mailing list)

Begin forwarded message:

From: buzz lightyear <buzzheavyyear@...>
Date: September 21, 2007 12:53:30 PM GMT+02:00
To: Nuno Carvalho <nunomrc@...>
Cc: <community@...>, José Orlando Pereira <jop@...>
Subject: RE: escada and jgcs

Hi Nuno - thanks for getting back to me

I'm trying to build a replication service using gorda. Escada exists and provides this service but the licence is gpl and consequently I need to develop my own replication service.

The Escada project has both a set of interfaces and an implementation. It looks as though it's very good and just what we need. Because of the license issues, I need to do develop my own implementation. If Escada had a lgpl license, I would be able to use Escada and I would be able to contribute to the project. If you guys are unable/unwilling to change the license to lgpl, then I will have to write another original work (and use Escada for inspiration!).

Jxta is a peer to peer framework, similar to jGCS - relatively easy to find peers and set up messaging and stream-based contexts between them. So, as far as gorda/escada is concerned, the intention was to use jxta as the way of wiring together the different database nodes. So, at the end of the day, I would be implementing gorda/escada over jxta instead of jGCS.

Hope this makes sense - this seemed to be the perfect solution for us until I saw the Escada license.

I'll try compiling derby-g again - it looks as though the problem is that I'm driving ant with java 6, even though I've defined .... oops, typo in the ant.properties -> embarrassed!

Thanks for your input and getting back to me

Cheers
Nick

CC: community@...; jop@...
From: nunomrc@...
Subject: Re: escada and jgcs
Date: Fri, 21 Sep 2007 12:15:02 +0200
To: buzzheavyyear@...

Hi Nick,

On Sep 19, 2007, at 11:52 , buzz lightyear wrote:

I have just gone over what I was trying to do in July and realise that it will be much easier to implement any replication with jxta via tcp streams, and then stream over jxta ..... there are so many ways to configure jxta that coming up with an escada framework for jxta might just frustrate many users

I don't know JXTA very well, but I got the impression that it is a communication infrastructure. Escada is more than that, it uses a communication infrastructure (through jGCS) and does database replication using also the GAPI interface on the databases. It contains protocols such as primary-backup and DBSM, recovery, etc.

I'm not sure what do you want to do, but JXTA and Escada are not comparable.

At the beginning of the week I tried to build derby-g-0.3 and was unable to do it. I followed the instructions and ran into problems via a unix shell - I have posted this issue to your forum and hope that someone might be able to respond.

I just answered that email. Sorry for the delay, we were all traveling for a demo of the GORDA project.

I also tried to build via netbeans which showed further problems of requiring xalan in the the gorda reflection api - xalan, I think, isn't mentioned in the build instructions.

I can build with eclipse... and I do not remember for the need for xalan on the derby implementation of GAPI. xalan is needed by Derby and not by the GORDA patch to implement GAPI (gorda reflection interface). The docs only refer to the things needed by this patch.

One last thing - is there any possibility that the escada interface might be set as an apache license instead of gnu - I am unable to use gnu, and consequently escada. If just the interface was set as apache then I would be able to do my own implementation.

Are you talking about the jGCS interface or the GAPI interface?
I do not manage this king of issues, I added José Pereira on Cc to clarify us about that.

Kind regards,

nuno

From: Nuno Carvalho <nunomrc@...>
To: buzz lightyear <buzzheavyyear@...>
CC: alfranio correia <alfranio@...>,José Orlando Pereira <jop@...>
Subject: Re: escada and jgcs
Date: Fri, 6 Jul 2007 13:27:54 +0100

Hi Nick,

On Jul 6, 2007, at 11:34 , buzz lightyear wrote:

I don't know if you/others have investigated Jxta as a possible jgcs binding - the current code doesn't make it easy for Jxta to be implemented.

No, not yet.

However, if SocketAddress is somehow embedded in a (for example) 'Member' interface then the Jxta IDs - there are two primary user types for peer and peergroup - can also be embedded within a Member interface, as jxta does reference sockets directly.

I'm not sure if you need this.

Since SocketAddress is an abstract class, you can do something like this:

public class JxtaPeer extends SocketAddress {
Member id;
}

The addresses in Spread are Strings and it works perfectly. You can take a look at the Spread binding (available for download in the SF) to see how we handle this. jGCS is supposed to be as generic as possible, so we use Java standard interfaces and abstract where possible.

With jGCS you should also be able to reuse native classes of the toolkit that you want to use for implementing jGCS. For example, the Appia binding does something like this:

public class AppiaMessage extends appia.Message implements jgcs.Message {
(...)
}

The messages are created and sent directly to the toolkit without any conversion overhead.

I suspect that I will press ahead soon and modify a local version of escada/jgcs. Would you be interested in me sending you anything I do? I would be unable to update and verify the jgroups and other bindings as I don't know them. However, the abstraction of SocketAddress into a Member class should make this relatively easy for all bindings.

Great! You are welcome to send anything that you have. You can also expect our help on problems and/or questions you may have.

Hope this helps,
--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

_________________________________________________________________
The next generation of Hotmail is here! http://www.newhotmail.co.uk

--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

Play Movie Mash-up and win BIG prizes!

Nuno Carvalho

University of Lisbon, Portugal

http://lasige.di.fc.ul.pt/~ncarvalho

Fwd: escada and jgcs

2007-09-21T06:39:25Z

(resent to be stored in the archives mailing list)

Begin forwarded message:

From: Nuno Carvalho <nunomrc@...>
Date: September 21, 2007 12:15:02 PM GMT+02:00
To: buzz lightyear <buzzheavyyear@...>
Cc: community@..., José Orlando Pereira <jop@...>
Subject: Re: escada and jgcs

Hi Nick,

On Sep 19, 2007, at 11:52 , buzz lightyear wrote:

I have just gone over what I was trying to do in July and realise that it will be much easier to implement any replication with jxta via tcp streams, and then stream over jxta ..... there are so many ways to configure jxta that coming up with an escada framework for jxta might just frustrate many users

I don't know JXTA very well, but I got the impression that it is a communication infrastructure. Escada is more than that, it uses a communication infrastructure (through jGCS) and does database replication using also the GAPI interface on the databases. It contains protocols such as primary-backup and DBSM, recovery, etc.

I'm not sure what do you want to do, but JXTA and Escada are not comparable.

At the beginning of the week I tried to build derby-g-0.3 and was unable to do it. I followed the instructions and ran into problems via a unix shell - I have posted this issue to your forum and hope that someone might be able to respond.

I just answered that email. Sorry for the delay, we were all traveling for a demo of the GORDA project.

I also tried to build via netbeans which showed further problems of requiring xalan in the the gorda reflection api - xalan, I think, isn't mentioned in the build instructions.

I can build with eclipse... and I do not remember for the need for xalan on the derby implementation of GAPI. xalan is needed by Derby and not by the GORDA patch to implement GAPI (gorda reflection interface). The docs only refer to the things needed by this patch.

One last thing - is there any possibility that the escada interface might be set as an apache license instead of gnu - I am unable to use gnu, and consequently escada. If just the interface was set as apache then I would be able to do my own implementation.

Are you talking about the jGCS interface or the GAPI interface?
I do not manage this king of issues, I added José Pereira on Cc to clarify us about that.

Kind regards,

nuno

From: Nuno Carvalho <nunomrc@...>
To: buzz lightyear <buzzheavyyear@...>
CC: alfranio correia <alfranio@...>,José Orlando Pereira <jop@...>
Subject: Re: escada and jgcs
Date: Fri, 6 Jul 2007 13:27:54 +0100

Hi Nick,

On Jul 6, 2007, at 11:34 , buzz lightyear wrote:

I don't know if you/others have investigated Jxta as a possible jgcs binding - the current code doesn't make it easy for Jxta to be implemented.

No, not yet.

However, if SocketAddress is somehow embedded in a (for example) 'Member' interface then the Jxta IDs - there are two primary user types for peer and peergroup - can also be embedded within a Member interface, as jxta does reference sockets directly.

I'm not sure if you need this.

Since SocketAddress is an abstract class, you can do something like this:

public class JxtaPeer extends SocketAddress {
Member id;
}

The addresses in Spread are Strings and it works perfectly. You can take a look at the Spread binding (available for download in the SF) to see how we handle this. jGCS is supposed to be as generic as possible, so we use Java standard interfaces and abstract where possible.

With jGCS you should also be able to reuse native classes of the toolkit that you want to use for implementing jGCS. For example, the Appia binding does something like this:

public class AppiaMessage extends appia.Message implements jgcs.Message {
(...)
}

The messages are created and sent directly to the toolkit without any conversion overhead.

I suspect that I will press ahead soon and modify a local version of escada/jgcs. Would you be interested in me sending you anything I do? I would be unable to update and verify the jgroups and other bindings as I don't know them. However, the abstraction of SocketAddress into a Member class should make this relatively easy for all bindings.

Great! You are welcome to send anything that you have. You can also expect our help on problems and/or questions you may have.

Hope this helps,
--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

_________________________________________________________________
The next generation of Hotmail is here! http://www.newhotmail.co.uk

--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

Nuno Carvalho

http://www.gsd.inesc-id.pt/~nonius/

Fwd: compiling derby-g-0.3

2007-09-21T06:38:40Z

(resent to be stored in the archives mailing list)

Begin forwarded message:

From: Nuno Carvalho <nunomrc@...>
Date: September 21, 2007 11:44:39 AM GMT+02:00
To: community@...
Cc: buzzc4nfw <buzzheavyyear@...>
Subject: Re: compiling derby-g-0.3

Hi Nick,

This is probably a CLASSPATH and/or JAVA_HOME definition problem.

Make sure that the properties j13lib and j14lib are well defined. This is ususally the JAVA_1.3_HOME/jre/lib and JAVA_1.4.2_HOME/jre/lib.
Another thing that you should check is the JAVA version that ant is using. you have to set the JAVA_HOME to your jdk version 1.4. Check it using the command: ant -diagnostics

Hope this helps,
nuno

On Sep 17, 2007, at 11:17 , buzzc4nfw wrote:

Hi

I'm having some trouble in compiling derby. I've followed the install
instructions, adding all of the jdks, jce etc.

The first 13 files get compiled, then the next one fails.

I keep getting the following error -

init:
[mkdir] Created dir: derby-g-0.3/classes

ensuresanitystate:

setissane:

showenv:

   [echo] Ant environment:
   [echo] Base Directory: derby-g-0.3
   [echo] Build output: derby-g-0.3/classes
   [echo] Compiler: modern
   [echo] Sane = false
   [echo] Proceed = no

getstate:

state:

shared:

compile:
[javac] Compiling 11 source files to /derby-g-0.3/classes
[javac] Compiling 1 source file to /derby-g-0.3/classes
[javac] Fatal Error: Unable to locate package java.lang in classpath or
bootclasspath

BUILD FAILED
derby-g-0.3/build.xml:347: The following error occurred while executing this
line:
derby-g-0.3/java/shared/build.xml:89: Compile failed; see the compiler error
output for details.

Total time: 1 second

Any ideas?

Thanks

Nick

--
View this message in context: http://www.nabble.com/compiling-derby-g-0.3-tf4465400s25582.html#a12732104
Sent from the GORDA Community mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@...
For additional commands, e-mail: community-help@...

--
Nuno Carvalho
University of Lisbon, Portugal
http://lasige.di.fc.ul.pt/~ncarvalho

Nuno Carvalho

http://www.gsd.inesc-id.pt/~nonius/

Re: escada and jgcs

2007-09-21T06:22:37Z

Hi,

On Sep 21, 2007, at 1:25 , buzz lightyear wrote:

My problem still exists with the gpl license, though. Unless someone is able to change this to lgpl then I'm stuck.

Lets wait for an answer from José Pereira.

Incedently, did you have any thoughts re. hibernates second level cache and gorda/escada?

I'm not sure if I understand how are you going to glue hibernate/escada/derby. Can you elaborate on this?

One last thing - I got a failure notice when I tried to email to community@...

Yes, we are solving this problem right now. Thanks for warning about this.

Cheers,

Nuno Carvalho

University of Lisbon, Portugal

http://lasige.di.fc.ul.pt/~ncarvalho

compiling derby-g-0.3

2007-09-17T03:17:45Z

Hi

I'm having some trouble in compiling derby. I've followed the install instructions, adding all of the jdks, jce etc.

The first 13 files get compiled, then the next one fails.

I keep getting the following error -

init:
[mkdir] Created dir: derby-g-0.3/classes

ensuresanitystate:

setissane:

showenv:

[echo] Ant environment:
[echo] Base Directory: derby-g-0.3
[echo] Build output: derby-g-0.3/classes
[echo] Compiler: modern
[echo] Sane = false
[echo] Proceed = no

getstate:

state:

shared:

compile:
[javac] Compiling 11 source files to /derby-g-0.3/classes
[javac] Compiling 1 source file to /derby-g-0.3/classes
[javac] Fatal Error: Unable to locate package java.lang in classpath or bootclasspath

BUILD FAILED
derby-g-0.3/build.xml:347: The following error occurred while executing this line:
derby-g-0.3/java/shared/build.xml:89: Compile failed; see the compiler error output for details.

Total time: 1 second

Any ideas?

Thanks

Nick

ESCADA Replication Server 0.4 released

2007-08-10T11:53:42Z

Release 0.4 of the ESCADA Replication Server is now available at:

http://escada.sourceforge.net

This is still an alpha release and no significant features have been
introduced since 0.3. However:

* A "quickstart" binary package using Derby allows you to get it up and
running with minimal effort.

* The server has been refactored and is now based on the Spring Framework.

* Protocols have been upgraded to GAPI 0.4, making it compatible with Apache
Derby, PostgreSQL and MySQL (through Sequoia 3.0 wrapper).

* Moved to Sourceforge.

The next release is scheduled for September, including propagation of DDL
statements and much improved stability under load.

Best regards,

--
Jose Orlando Pereira

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@...
For additional commands, e-mail: community-help@...

GORDA Community moved to Nabble

2007-08-10T11:39:01Z

The GORDA Community list archive has just moved to the excellent service at
Nabble.com, under Software / Database. The direct link is:

http://www.nabble.com/GORDA-Community-f25582.html

Best regards,

--
Jose Orlando Pereira

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@...
For additional commands, e-mail: community-help@...

Replication hooks for PostgreSQL

2006-10-02T07:23:13Z

Hi,

The PostgreSQL community has created a mailing list to discuss replication
hooks. More information at:

http://archives.postgresql.org/pgsql-hackers/2006-09/msg02330.php

--
Jose Orlando Pereira

smime.p7s (2K) Download Attachment

Bug in PostgreSQL patched code

2006-09-20T06:48:16Z

The following code change submitted in your patch for PostgreSQL is incorrect.
File: src/backend/utils/init/postinit.c

...
static void
ShutdownPostgres(int code, Datum arg)
{
if (!IsBootstrapProcessingMode() && code == 0) {
shutdownTrigger = true;
StartTransactionCommand();
ExecTriggerSpecial(TRIGGER_TYPE_SHUTDOWN);
CommitTransactionCommand();
}
...

The reason it is incorrect is that during a shut down of the backend via a
FATAL or PANIC failure, the user will almost certainly be in a transaction of
some sort and therefore "StartTransactionCommand();" fails with message:
"StartTransactionCommand: unexpected state STARTED".

I am not sure of the correct solution here but I assume you are expecting no
transaction abort state when "code == 0". I think a better solution would be:

if (!IsBootstrapProcessingMode() && code == 0 &&
!IsTransactionOrTransactionBlock()) {

Regards
Donald Fraser.

ESCADA Replication Server

2006-08-25T12:07:49Z

We are happy to announce that version 0.2 of the Escada Replication
Server was released.

The ESCADA Replication Server is a modular protocol based on group
communication that can be configured to
accommodate multiple reliability, performance, and applicability tradeoffs.
It is aimed at clusters, for performance and scalability, as well as at
disaster recovery in wide area networks.

You can download it from http://gorda.di.uminho.pt/community/escada/

We would like to hear your comments, feel free to send any feedback
using our community mailing list.

Best regards,

Alfranio Junior.