WARNINGS and minor ERROR during startup
Added by Attila Mészáros 142 days ago
Hi,
I've started playing with roda on the preferred ubuntu 8.04.
The install finished without any errors, but the startup produces exceptions at some points:
- RODA WUI seems to work, a few units were stored in fedora
- but weired exceptions occur even later... they may be related to original ones.
So can I ignore these errors, or shall i hount them down?
thanx
Attila
The errors of the startup:
1. first 3 lines of a horrible exception trace in the activemq configuration:
13:02:59,350 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=activemq
13:02:59,359 WARN [ServiceController] Problem starting service persistence.units:unitName=activemq
java.lang.RuntimeException: You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: activemq
this one causes at the end of the jboss boot:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: persistence.units:unitName=activemq
State: FAILED
Reason: java.lang.RuntimeException: You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: activemq
2. another one during the deployment of php5servlet:
13:03:05,203 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../tmp/deploy/tmp1976492821174510003ROOT-exp.war/
13:03:05,647 ERROR / StandardWrapper.Throwable
java.lang.UnsatisfiedLinkError: no php5servlet in java.library.path, no libphp5servlet in java.library.path(/usr/local/roda/libs/php5servlet-linux-i686-1.0.3/PHP/lib)
3. during the log4j config:
13:03:05,707 INFO [TomcatDeployer] deploy, ctxPath=/fedora, warUrl=.../deploy/fedora.war/
13:03:09,372 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
13:03:09,372 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
13:03:09,372 ERROR [STDERR] log4j:ERROR [WebappClassLoader
4. there are approximately 10-15 exceptions like this one. (really a WARN-ing, )
13:03:28,316 INFO [TomcatDeployer] deploy, ctxPath=/roda-migrator, warUrl=.../tmp/deploy/tmp6903424465547956234roda-migrator-exp.war/
13:03:31,149 WARN [JARDeployer] Failed to add deployable jar: file:/usr/local/roda/jboss-4.2.3.GA/server/default/tmp/deploy/tmp7041688224833285887README
java.util.zip.ZipException: error in opening zip file
5. there are hundreds of files waiting for deployment, like this one:
13:03:31,488 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@59e31c7e { url=file:/usr/local/roda/jboss-4.2.3.GA/server/default/deploy/fedora/META-INF/MANIFEST.MF }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/usr/local/roda/jboss-4.2.3.GA/server/default/deploy/fedora/META-INF/MANIFEST.MF
Replies
RE: WARNINGS and minor ERROR during startup - Added by Attila Mészáros 141 days ago
Hi,
One possible consequence of the first exception (activemq)
1. first 3 lines of a horrible exception trace in the activemq configuration: 13:02:59,350 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:unitName=activemq 13:02:59,359 WARN [ServiceController] Problem starting service persistence.units:unitName=activemq java.lang.RuntimeException: You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: activemq
RODA WUI search does not work.
the recently stored units are in the fedora database, but the search does not show them up. (gsearch was initiated as described in the doc)
related logs:
roda-viewlog-fedora: (FilterSetup) can't process filter()
roda-viewlog-fedoragsearch: Updater properties were not loaded so no update listeners were created. Update messages will not be received or processed
Attila
RE: WARNINGS and minor ERROR during startup - Added by Luís Faria 138 days ago
You can ignore exception in 1). This is an JBoss configuration problem that we where to lazy to remove, but it gives no problems later.
Exception in 2) relates to a problem in the PHP5 servlet for JBoss, that is used for the database viewer. This problem was already found by the development team, and is because the current deployed installation doesn't have the 32bit binaries (only the 64bit). We are working on resolving this problem and will follow up later.
Exception in 3) is quite strange, but it seems to only affect logging.
Exceptions in 4) are quite troublesome, you seem to have a problem deploying the system, are you starting JBoss as root?
You can also ignore exception in 5).
Use luke (http://www.getopt.org/luke/) to check your Lucene index.
If the index is empty, monitor the roda-core log (/usr/local/roda/logs/roda-core.log) while changing the metadata of an object in the WUI, and paste the log excerpt here.
Best,
RE: WARNINGS and minor ERROR during startup - Added by Attila Mészáros 135 days ago
Hi Luis,
Thanx.
- yes, I've started as root, starting as an unprivileged user definitely seemed to help.
- luke is great. i was playing with barefoot lucene 4 years ago. it's much easier this way.
- after re-setting rights on existing files, and restarting as ubuntu user, re-creating and refreshing the indicees had helped.
now some of the flash statistics are hanging... (mozilla 3.05, flash 9.0)
- I can not deliberately reproduce the bug, but I will report it in details as soon, as I can.
Attila
RE: WARNINGS and minor ERROR during startup - Added by Attila Mészáros 131 days ago
Hi Luis,
Here are the more detailed reports of the experienced problems:
Error during editing the timespan of the statistics graphs:
- severity is minor
- after clicking the edit icon all we get is an inactive layer without editor dialog
- after clicking back button on the browser we get the working editing dialog
- after clicking apply on the dialog, the statistics layer does not refresh,
- to view the modified result first we have to close and reopen the certain statistics
Error during adding representation to java RODA-in:
- severity is serious
- stack overflow exception with firePropertyChange and setDate in its core
- this exception stops the creation of any package
- maybe locale settings were incorrect, but setting pt_PT to en_US or en have not helped
- unreasonable and automagical date rewrites on tab and validation events:
-- setting sole initial date results: initial date - approx half year !!!
-- setting sole final date results: initial date = final date - [8..14] years !!!
Attila