Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 481280 - Performance tests say "can not create log"
Summary: Performance tests say "can not create log"
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 454921
  Show dependency tree
 
Reported: 2015-11-02 21:15 EST by David Williams CLA
Modified: 2020-03-24 11:44 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2015-11-02 21:15:11 EST
This occurs during the 
org.eclipse.jface.tests.performance.JFacePerformanceSuite 

tests. 

The initial Error message is 

!MESSAGE Internal Error
!STACK 0
java.sql.SQLNonTransientConnectionException: A network protocol error was encountered and the connection has been terminated: The requested command encountered an unarchitected and implementation-specific condition for which there was no architected message (additional information may be available in the derby.log file on the server).
	at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
	at org.apache.derby.client.am.ClientConnection.commit(Unknown Source)
	at org.eclipse.test.internal.performance.db.DB.internalStore(DB.java:917)
	at org.eclipse.test.internal.performance.db.DB.store(DB.java:279)
	at org.eclipse.test.internal.performance.InternalPerformanceMeter.commit(InternalPerformanceMeter.java:90)
	at org.eclipse.ui.tests.performance.PerformanceTester.commitMeasurements(PerformanceTester.java:65)
	at org.eclipse.ui.tests.performance.BasicPerformanceTest.commitMeasurements(BasicPerformanceTest.java:171)
[...] 

And, then later says 

Caused by: ERROR 08006: A network protocol error was encountered and the connection has been terminated: The requested command encountered an unarchitected and implementation-specific condition for which there was no architected message (additional information may be available in the derby.log file on the server).
	at org.apache.derby.client.net.NetConnectionReply.parseCMDCHKRM(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.parseCommitError(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.parseRDBCMMreply(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.readLocalCommit(Unknown Source)
	at org.apache.derby.client.net.ConnectionReply.readLocalCommit(Unknown Source)
	at org.apache.derby.client.net.NetConnection.readLocalCommit_(Unknown Source)
	at org.apache.derby.client.am.ClientConnection.readCommit(Unknown Source)
	at org.apache.derby.client.am.ClientConnection.flowCommit(Unknown Source)
	... 56 more
Caused by: ERROR XSLAQ: DERBY SQL error: ERRORCODE: 45000, SQLSTATE: XSLAQ, SQLERRMC: Cannot create log file at directory /data/shared/eclipse/databases/perfDB/log.
	... 64 more
Comment 1 David Williams CLA 2015-11-02 21:35:22 EST
(In reply to David Williams from comment #0)

> Caused by: ERROR XSLAQ: DERBY SQL error: ERRORCODE: 45000, SQLSTATE: XSLAQ,
> SQLERRMC: Cannot create log file at directory
> /data/shared/eclipse/databases/perfDB/log.
> 	... 64 more

I will note, there is a directory at 
/data/shared/eclipse/databases/perfDB/log

... all owned by the same userid that is running the database and tests, so, not sure what this error means. 

I am sure it means something .. perhaps some other file under that directory? That might "be busy"?
Comment 2 David Williams CLA 2015-11-02 21:41:09 EST
I should note, this is on my local test machine. 

Should confirm on build.eclipse.org machine.
Comment 3 Eclipse Genie CLA 2020-03-24 11:44:26 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.