Aron,

I hate to take advantage of your good nature, but I continue to have
problems with the Collective Space install.  Three messages are in the
catalina file.  The first two are from Nuxeo:

2013-06-19 11:38:35,997 ERROR [main]
[org.nuxeo.runtime.osgi.OSGiRuntimeService:529] Nuxeo EP Started

---====
= Nuxeo EP Started

---====
= Component Loading Errors:

• Unknown component 'OSGI-INF/layouts-contrib.xml' referenced by bundle
  'org.collectionspace.publicitem'

---====
= Component Loading Status: Pending: 1 / Unstarted: 0 / Total: 206

• service:org.nuxeo.ecm.platform.picture.web.preview.adapter.contrib
  requires [service:org.nuxeo.ecm.platform.preview.adapter.contrib]

---====

The third seems to be from Collection Space, but it may be associated with a
configuration error on my part:

2013-06-19 11:38:41,520 ERROR [main]
[org.collectionspace.services.common.config.ConfigUtils:51] No domain name
was specified on call to getRepositoryName() method.

Two identical ones are in the localhost log:

2013-06-19 11:42:56,294 ERROR [http-8180-1]
[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/collections
pace].[TenantServlet]:281] Servlet.service() for servlet TenantServlet threw
exception
java.lang.IllegalStateException
at
org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:4
07)

I also have errors in the initial resets (here is for core):
UnderlyingStorageException Service layer exceptionBad request during
identifier cache map update: status not 200 is 401

So, still slogging along but getting discouraged.  Any help would be
welcome.

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf Of Aron
Roberts
Sent: Wednesday, June 19, 2013 7:47 AM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: Collection Space Question

Hi Fred,

On Wed, Jun 19, 2013 at 6:45 AM, Fred Warren FWarren574@aol.com wrote:

That's terrific!

There are far too many (IMO) warning and error messages routinely emitted
during CollectionSpace startup, which can make it difficult to decipher
those which are exceptional, and hence meaningful.
Coincidentally, I was noticing this again yesterday, and will make a
'cleanup' JIRA issue for us to address this.

My understanding of the message you cited, "Could not retrieve a lifecycle
transition definition list from: idgenerators," is that it signifies that
records of CollectionSpace's ID service - a service which includes a
REST-addressable resource named "idgenerators" - do not have lifecycle
states.  That means those records can't be transitioned between 'active' and
'soft deleted' (marked as deleted but still archived) states, for instance,
in the manner that many other CollectionSpace records can be.

More on workflow states in CollectionSpace:

http://wiki.collectionspace.org/display/collectionspace/Common+Services+REST
+API+documentation#CommonServicesRESTAPIdocumentation-Readworkflowstateofano
bject%2Fprocedure%2Frecordinstance

Thanks, Fred!  Am sharing your message with the project Talk list, for
others' follow-up comments on this, if any.

Aron

On Wed, Jun 19, 2013 at 6:45 AM, Fred Warren FWarren574@aol.com wrote:

stumped.

Regarding those errors:

The first error:

That's a non-harmful error: this means there is no Nuxeo layout file

• one that would be used to display a forms-based record viewer/editor
  within a Nuxeo web-based console - for the Publicitem service.  That's
  expected, as this service simply provides public (unauthenticated)
  access to records which may potentially be of any type, that have been
  'published' so as to become public.  As such, no single web form would
  make sense for that service.

The second error:

On normally functioning systems, we routinely see multiple instances
of that error in startup logs; - I spotted 15 such entries in one log.
At a first glance, this could potentially be because six AuthN/AuthZ
services don't have a repository domain specified via a
service:repositoryDomain element in CollectionSpace's Services
("tenant bindings") configuration, as they do not use Nuxeo as a
back-end repository but rather maintain their own data in the
database, via Hibernate or JDBC calls.  (As such, this could well be
another case where our code should not be logging those events at
ERROR level.)  However, I haven't looked into this sufficiently to
confirm this.  Regardless, you can safely ignore those errors for now.

The third error (combined):

and

This combination of errors is likely of significance.

A first question: is CollectionSpace's Services layer working?  That
is, can you access lists of records via the Services REST APIs?  A
sample URL you can visit in a web browser, via 'curl', etc.;
substitute your own hostname for 'localhost' below if appropriate:

http://localhost:8180/cspace-services/collectionobjects

When prompted by a browser dialog, or via command line arguments to
curl, you can enter 'admin@core.collectionspace.org' as the username
and 'Administrator' as the password.  This command should return an
XML payload, consisting of a list of zero or more summaries of
CollectionObject (aka Cataloging) records.

If so, we can proceed on the assumption that - working from the
inside out, much like passing through layers of an onion, that the
back-end functionality in your CollectionSpace instance: database -
Nuxeo, and Services layer - is likely working properly.  The next
place to check is the front-end functionality, consisting of the
Application and UI layers.

The errors you cited are likely in the Application layer; the
TenantServlet and UnderlyingStorageException classes, both mentioned
in that third pair of error messages, are present in that layer.  For
example, you can view the first of those classes in the project's
source code repository for that layer:

https://github.com/collectionspace/application/blob/master/tomcat-main/src/main/java/org/collectionspace/chain/controller/TenantServlet.java

I have some very old notes on the only time I saw that
ResponseFacade error; those notes may or may not pertain to your
current error.  They suggest that a context.xml file might be missing
from the deployed .war file for the Application layer, in part due to
an error during deployment (copying of files into the Tomcat server
folder) of artifacts for that layer.  In turn, that might have been
due to a deployment of that layer at a time when the CATALINA_HOME
environment variable hadn't been set, or had been set to a value
different than that of the JEE_SERVER_HOME environment variable.

Does that help at all?  If so, and if you haven't yet made any
customizations, by changing configuration or code, to the Application
layer, you could a) set the value of that CATALINA_HOME environment
variable and verify that it exists in your environment; b) shut down
the CollectionSpace server; c) in %CATALINA_HOME%\webapps, delete both
the 'collectionspace.war' file and the 'collectionspace' folder; d)
check out the Application layer source code for your relevant version
of CollectionSpace (e.g. 3.2.2), if you haven't already:

http://wiki.collectionspace.org/display/DOC/How+to+check+out+the+Application+layer+source+code

and e) from the top-level of its folder (e.g. a directory listing
should show 'tomcat-main' and 'war-entry' subdirectories, among
others), re-deploy the Application layer with the command:

mvn clean install -DskipTests

Aron

On Wed, Jun 19, 2013 at 12:08 PM, Fred Warren FWarren574@aol.com wrote:

Aron,

I hate to take advantage of your good nature, but I continue to have
problems with the Collective Space install.  Three messages are in the
catalina file.  The first two are from Nuxeo:

2013-06-19 11:38:35,997 ERROR [main]
[org.nuxeo.runtime.osgi.OSGiRuntimeService:529] Nuxeo EP Started

---====
= Nuxeo EP Started

---====
= Component Loading Errors:

• Unknown component 'OSGI-INF/layouts-contrib.xml' referenced by
  bundle 'org.collectionspace.publicitem'

---====
= Component Loading Status: Pending: 1 / Unstarted: 0 / Total: 206

• service:org.nuxeo.ecm.platform.picture.web.preview.adapter.contrib
  requires [service:org.nuxeo.ecm.platform.preview.adapter.contrib]

---====

The third seems to be from Collection Space, but it may be associated
with a configuration error on my part:

2013-06-19 11:38:41,520 ERROR [main]
[org.collectionspace.services.common.config.ConfigUtils:51] No domain
name was specified on call to getRepositoryName() method.

Two identical ones are in the localhost log:

2013-06-19 11:42:56,294 ERROR [http-8180-1]
[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/colle
ctions pace].[TenantServlet]:281] Servlet.service() for servlet
TenantServlet threw exception java.lang.IllegalStateException
at
org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.
java:4
07)

I also have errors in the initial resets (here is for core):
UnderlyingStorageException Service layer exceptionBad request during
identifier cache map update: status not 200 is 401

So, still slogging along but getting discouraged.  Any help would be
welcome.

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf
Of Aron Roberts
Sent: Wednesday, June 19, 2013 7:47 AM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: Collection Space Question

Hi Fred,

On Wed, Jun 19, 2013 at 6:45 AM, Fred Warren FWarren574@aol.com wrote:

That's terrific!

There are far too many (IMO) warning and error messages routinely
emitted during CollectionSpace startup, which can make it difficult to
decipher those which are exceptional, and hence meaningful.
Coincidentally, I was noticing this again yesterday, and will make a
'cleanup' JIRA issue for us to address this.

My understanding of the message you cited, "Could not retrieve a
lifecycle transition definition list from: idgenerators," is that it
signifies that records of CollectionSpace's ID service - a service
which includes a REST-addressable resource named "idgenerators" - do
not have lifecycle states.  That means those records can't be
transitioned between 'active' and 'soft deleted' (marked as deleted
but still archived) states, for instance, in the manner that many other

More on workflow states in CollectionSpace:

http://wiki.collectionspace.org/display/collectionspace/Common+Service
s+REST
+API+documentation#CommonServicesRESTAPIdocumentation-Readworkflowstat
+API+eofano
bject%2Fprocedure%2Frecordinstance

Thanks, Fred!  Am sharing your message with the project Talk list,
for others' follow-up comments on this, if any.

Aron

On Wed, Jun 19, 2013 at 6:45 AM, Fred Warren FWarren574@aol.com wrote:

stumped.

Aron,

I have CC'd the talk list on this message and hope that you or one of your
colleagues can continue to help me dig out of my install issues.  I tried
your suggestion to access the cspace-services/collectionobjects and got the
following:

List request failed: org.nuxeo.ecm.core.api.ClientException: Failed to
execute query: ERROR: operator does not exist: character varying = bigint
Hint: No operator matches the given name and argument type(s). You might
need to add explicit type casts.
Position: 192

Since the your initial test turned up a problem, I am assuming that the fix
is very high up the food chain.

I hope to continue to press on until I get a successful install.

Thanks!

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf Of Aron
Roberts
Sent: Wednesday, June 19, 2013 1:02 PM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: Collection Space Question

Hi Fred,

Thanks for these follow-up problem reports.  This is a reminder that
CollectionSpace's project team and peer support is accessible via the
project's Talk list, and questions like yours below are best be posted to
that list.

Regarding those errors:

The first error:

That's a non-harmful error: this means there is no Nuxeo layout file

• one that would be used to display a forms-based record viewer/editor
  within a Nuxeo web-based console - for the Publicitem service.  That's
  expected, as this service simply provides public (unauthenticated) access to
  records which may potentially be of any type, that have been 'published' so
  as to become public.  As such, no single web form would make sense for that
  service.

The second error:

On normally functioning systems, we routinely see multiple instances of
that error in startup logs; - I spotted 15 such entries in one log.
At a first glance, this could potentially be because six AuthN/AuthZ
services don't have a repository domain specified via a
service:repositoryDomain element in CollectionSpace's Services ("tenant
bindings") configuration, as they do not use Nuxeo as a back-end repository
but rather maintain their own data in the database, via Hibernate or JDBC
calls.  (As such, this could well be another case where our code should not
be logging those events at ERROR level.)  However, I haven't looked into
this sufficiently to confirm this.  Regardless, you can safely ignore those
errors for now.

The third error (combined):

and

This combination of errors is likely of significance.

A first question: is CollectionSpace's Services layer working?  That is,
can you access lists of records via the Services REST APIs?  A sample URL
you can visit in a web browser, via 'curl', etc.; substitute your own
hostname for 'localhost' below if appropriate:

http://localhost:8180/cspace-services/collectionobjects

When prompted by a browser dialog, or via command line arguments to curl,
you can enter 'admin@core.collectionspace.org' as the username and
'Administrator' as the password.  This command should return an XML payload,
consisting of a list of zero or more summaries of CollectionObject (aka
Cataloging) records.

If so, we can proceed on the assumption that - working from the inside
out, much like passing through layers of an onion, that the back-end
functionality in your CollectionSpace instance: database - Nuxeo, and
Services layer - is likely working properly.  The next place to check is the
front-end functionality, consisting of the Application and UI layers.

The errors you cited are likely in the Application layer; the
TenantServlet and UnderlyingStorageException classes, both mentioned
in that third pair of error messages, are present in that layer.  For
example, you can view the first of those classes in the project's source
code repository for that layer:

https://github.com/collectionspace/application/blob/master/tomcat-main/src/m
ain/java/org/collectionspace/chain/controller/TenantServlet.java

I have some very old notes on the only time I saw that ResponseFacade
error; those notes may or may not pertain to your current error.  They
suggest that a context.xml file might be missing from the deployed .war file
for the Application layer, in part due to an error during deployment
(copying of files into the Tomcat server
folder) of artifacts for that layer.  In turn, that might have been due to a
deployment of that layer at a time when the CATALINA_HOME environment
variable hadn't been set, or had been set to a value different than that of
the JEE_SERVER_HOME environment variable.

Does that help at all?  If so, and if you haven't yet made any
customizations, by changing configuration or code, to the Application layer,
you could a) set the value of that CATALINA_HOME environment variable and
verify that it exists in your environment; b) shut down the CollectionSpace
server; c) in %CATALINA_HOME%\webapps, delete both the 'collectionspace.war'
file and the 'collectionspace' folder; d) check out the Application layer
source code for your relevant version of CollectionSpace (e.g. 3.2.2), if
you haven't already:

http://wiki.collectionspace.org/display/DOC/How+to+check+out+the+Application
+layer+source+code

and e) from the top-level of its folder (e.g. a directory listing should
show 'tomcat-main' and 'war-entry' subdirectories, among others), re-deploy
the Application layer with the command:

mvn clean install -DskipTests

Aron

On Wed, Jun 19, 2013 at 12:08 PM, Fred Warren FWarren574@aol.com wrote:

CollectionSpace records can be.

our

on.

our

on.

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Aron,

I have CC'd the talk list on this message and hope that you or one of
your colleagues can continue to help me dig out of my install issues.
I tried your suggestion to access the
cspace-services/collectionobjects and got the
following:

List request failed: org.nuxeo.ecm.core.api.ClientException: Failed to
execute query: ERROR: operator does not exist: character varying = bigint
Hint: No operator matches the given name and argument type(s). You
might need to add explicit type casts.
Position: 192

Since the your initial test turned up a problem, I am assuming that
the fix is very high up the food chain.

I hope to continue to press on until I get a successful install.

Thanks!

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf
Of Aron Roberts
Sent: Wednesday, June 19, 2013 1:02 PM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: Collection Space Question

Hi Fred,

Thanks for these follow-up problem reports.  This is a reminder that
CollectionSpace's project team and peer support is accessible via the
project's Talk list, and questions like yours below are best be posted
to that list.

Regarding those errors:

The first error:

That's a non-harmful error: this means there is no Nuxeo layout file

• one that would be used to display a forms-based record viewer/editor
  within a Nuxeo web-based console - for the Publicitem service.  That's
  expected, as this service simply provides public (unauthenticated)
  access to records which may potentially be of any type, that have been
  'published' so as to become public.  As such, no single web form would
  make sense for that service.

The second error:

On normally functioning systems, we routinely see multiple instances
of that error in startup logs; - I spotted 15 such entries in one log.
At a first glance, this could potentially be because six AuthN/AuthZ
services don't have a repository domain specified via a
service:repositoryDomain element in CollectionSpace's Services
("tenant
bindings") configuration, as they do not use Nuxeo as a back-end
repository but rather maintain their own data in the database, via
Hibernate or JDBC calls.  (As such, this could well be another case
where our code should not be logging those events at ERROR level.)
However, I haven't looked into this sufficiently to confirm this.
Regardless, you can safely ignore those errors for now.

The third error (combined):

and

This combination of errors is likely of significance.

A first question: is CollectionSpace's Services layer working?  That
is, can you access lists of records via the Services REST APIs?  A
sample URL you can visit in a web browser, via 'curl', etc.;
substitute your own hostname for 'localhost' below if appropriate:

http://localhost:8180/cspace-services/collectionobjects

When prompted by a browser dialog, or via command line arguments to
curl, you can enter 'admin@core.collectionspace.org' as the username
and 'Administrator' as the password.  This command should return an
XML payload, consisting of a list of zero or more summaries of
CollectionObject (aka
Cataloging) records.

If so, we can proceed on the assumption that - working from the
inside out, much like passing through layers of an onion, that the
back-end functionality in your CollectionSpace instance: database -
Nuxeo, and Services layer - is likely working properly.  The next
place to check is the front-end functionality, consisting of the

file and the 'collectionspace' folder; d) check out the Application
layer source code for your relevant version of CollectionSpace (e.g.
3.2.2), if you haven't already:

http://wiki.collectionspace.org/display/DOC/How+to+check+out+the+Appli
cation
+layer+source+code

and e) from the top-level of its folder (e.g. a directory listing
should show 'tomcat-main' and 'war-entry' subdirectories, among
others), re-deploy the Application layer with the command:

mvn clean install -DskipTests

Aron

On Wed, Jun 19, 2013 at 12:08 PM, Fred Warren FWarren574@aol.com wrote:

CollectionSpace records can be.

our

on.

our

on.

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio
nspace.org

Aron and the talk team,

I reviewed the troubleshooting information about creating casts in Postgre
and ran the appropriate script.  Things are now different.  When I access
http://localhost:8180/cspace-services/collectionobjects I get the following
instead of a login screen:

This XML file does not appear to have any style information associated with
it. The document tree is shown below.

ns2:abstract-common-list<pageNum>0</pageNum><pageSize>40</pageSize><itemsI nPage>0</itemsInPage><totalItems>0</totalItems><fieldsReturned>csid|uri|refN
ame|updatedAt|workflowState|objectNumber|objectName|title|responsibleDepartm
ent</fieldsReturned></ns2:abstract-common-list>

I suppose this is progress, but I'm not home yet.  I guess I still need more
help.

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf Of Aron
Roberts
Sent: Wednesday, June 19, 2013 3:11 PM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Collection Space Question

Hi Fred,

That one's fortunately a known issue, easily resolved:

http://wiki.collectionspace.org/display/DOC/Troubleshooting+Installation+Pro
blems#TroubleshootingInstallationProblems-Selectedservicesfunctionalityisfai
ling%3Arequestinglists%2Csearching%2Csorting%28ordering%29

The corresponding installation step is at:

http://wiki.collectionspace.org/display/DOC/PostgreSQL+Installation+-+Window
s%2C+Mac+OS+X%2C+Generic+Linux
(under the section header "Set up datatype casts")

Best,
Aron

On Wed, Jun 19, 2013 at 2:55 PM, Fred Warren FWarren574@aol.com wrote:

Application and UI layers.

'collectionspace.war'

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Aron and the talk team,

I reviewed the troubleshooting information about creating casts in
Postgre and ran the appropriate script.  Things are now different.
When I access http://localhost:8180/cspace-services/collectionobjects
I get the following instead of a login screen:

This XML file does not appear to have any style information associated
with it. The document tree is shown below.

ns2:abstract-common-list<pageNum>0</pageNum><pageSize>40</pageSize><
itemsI
nPage>0</itemsInPage><totalItems>0</totalItems><fieldsReturned>csid|ur
nPage>i|refN
ame|updatedAt|workflowState|objectNumber|objectName|title|responsibleD
ame|updatedAt|workflowState|objectNumber|objectName|title|epartm
ent</fieldsReturned></ns2:abstract-common-list>

I suppose this is progress, but I'm not home yet.  I guess I still
need more help.

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf
Of Aron Roberts
Sent: Wednesday, June 19, 2013 3:11 PM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Collection Space Question

Hi Fred,

That one's fortunately a known issue, easily resolved:

http://wiki.collectionspace.org/display/DOC/Troubleshooting+Installati
on+Pro
blems#TroubleshootingInstallationProblems-Selectedservicesfunctionalit
yisfai
ling%3Arequestinglists%2Csearching%2Csorting%28ordering%29

The corresponding installation step is at:

http://wiki.collectionspace.org/display/DOC/PostgreSQL+Installation+-+
Window
s%2C+Mac+OS+X%2C+Generic+Linux
(under the section header "Set up datatype casts")

Best,
Aron

On Wed, Jun 19, 2013 at 2:55 PM, Fred Warren FWarren574@aol.com wrote:

Application and UI layers.

'collectionspace.war'

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio
nspace.org

Hi Aron,

Definitely progress!  I can login to Collection Space as the administrator
and I see forms that can be filled out for the various collection steps.
The only thing that still seems to be a problem is that when I put in a name
for someone (say on an Accession record) I get a spinning Collection Space
icon and no response although I can fill other fields out.  Is there
something I need to know about setting up name lists?  What does the
spinning icon imply?

The good news is that the system looks great and probably would work for our
organization.  Well worth my work so far and I am deeply appreciative of
your help.

Fred Warren

-----Original Message-----
From: aronroberts@gmail.com [mailto:aronroberts@gmail.com] On Behalf Of Aron
Roberts
Sent: Wednesday, June 19, 2013 5:25 PM
To: Fred Warren
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Collection Space Question

Hi Fred,

You're making steady progress.  The XML payload you received, below, is
what you'll see when successfully querying the CollectionSpace services
layer for a list of CollectionObjects, and receiving an empty list in the
response, signifying that zero such records currently exist.

A next step might be to try logging in via the UI; e.g. at
http://localhost:8180/collectionspace/ui/core/html/index.html, and seeing if
you can successfully login with username 'admin@core.collectionspace.org'
and password 'Administrator'.  If not, you might look for recent error
messages in the cspace-app.log and cspace-services.log logfiles, in
%CSPACE_JEESERVER_HOME%\logs

Aron

On Wed, Jun 19, 2013 at 4:51 PM, Fred Warren FWarren574@aol.com wrote:

bigint

bigint

one log.

a

a

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

and password 'Administrator'.  If not, you might look for recent error
messages in the cspace-app.log and cspace-services.log logfiles, in
%CSPACE_JEESERVER_HOME%\logs

Aron

On Wed, Jun 19, 2013 at 4:51 PM, Fred Warren FWarren574@aol.com wrote:

bigint

bigint

one log.

a

a

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio
nspace.org