You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michelle Caisse (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 05:01:49 UTC
[jira] [Created] (JDO-706) No enhancer log output with maven 2
No enhancer log output with maven 2
-----------------------------------
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Craig L Russell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233182#comment-13233182 ]
Craig L Russell commented on JDO-706:
-------------------------------------
>From reading the log4j code, there are two places that log4j looks for the log4j.properties: the loader that loaded log4j itself; and the context class loader.
We might have to look into the context class loader as the source for the log4j.properties.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255701#comment-13255701 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
Andy's guess that the issues on Windows have to do with its limitation on command length appears to be a good one. With a web search I find this, for example:
"When I launch our application in Eclipse on Windows I receive the following error:
Exception occured executing command line.
Cannot run program .. : CreateProcess error=87, The parameter is incorrect
I've solved this in the past by shortening the CLASSPATH.
I've now come to a point where I can no longer shorten the CLASSPATH, and would like to know if there are any other workarounds.
http://support.microsoft.com/kb/830473 seems to indicate that the max command prompt line length in windows xp is 8191 characters, and the only solution is to shorten folder names, reduce depth of folder trees, using parameter files, etc."
exectck displays the command line for each test, so we can check that and see what might be truncated for the failing tests.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: jdo706.patch
With the attached patch, all configurations and tests run on Windows, but there are still errors:
Total tests run: 1798. Failures: 2, Errors: 12.
4 of 117 configurations failed.
I wonder if these have to do with the file separator character.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by Andy Jefferson <an...@datanucleus.org>.
> *> Running tests for pm.conf with datastoreidentity on 'derby' mapping= ...
> Exception on command [java, -cp,
> /D:/users/michael/.m2/repository/org/apache/jdo/jdo-exectck/1.0-SNAPSHOT/j
> do-exectck-1.0-SNAPSHOT.jar;/D:/users/michael/.m2/repository/junit/junit/3.
> 8.1/junit-3.8.1.jar;... These tests do not occur in TCK-results.txt and
> there are no log files for these tests.
>
> Any idea what is different on Windows?
I don't use Windows, but a guess would be the command line used by the
invocation is too long for Windows archaic limitations? Obviously the actual
exception ("CreateProcess error=87" perhaps) would confirm that. Obviously it
may also be something completely different :-)
--
Andy
DataNucleus (http://www.datanucleus.org)
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michael Bouschen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255005#comment-13255005 ]
Michael Bouschen commented on JDO-706:
--------------------------------------
I can run jdo-706.patch on Mac w/o any errors:
Total tests run: 1798.
All (117) configurations passed.
However, on Windows I also see errors on pmf test and other test configurations.
For some reason not all test configurations are executed. The summary at the bottom of the TCK-results.txt file lists less tests and less configurations:
Total tests run: 1417. Failures: 0, Errors: 8.
2 of 82 configurations failed.
During the mvn install run I see errors on the commad line:
*> Running tests for pm.conf with datastoreidentity on 'derby' mapping= ... Exception on command [java, -cp, /D:/users/michael/.m2/repository/org/apache/jdo/jdo-exectck/1.0-SNAPSHOT/jdo-exectck-1.0-SNAPSHOT.jar;/D:/users/michael/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar;...
These tests do not occur in TCK-results.txt and there are no log files for these tests.
Any idea what is different on Windows?
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: (was: jdo706.patch)
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274484#comment-13274484 ]
Andy Jefferson commented on JDO-706:
------------------------------------
Perhaps you should also remove connection pooling jar(s) from top-level pom.xml and put them into the "lib/jdori" area too? After all they are for use with the RI.
All works on Linux
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: 20120410-211429.zip
I get the same errors with java 1.6.0_25. Error log files attached.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233168#comment-13233168 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
The approach suggested to solving this problem is to manually add the log4j jar file to the class loader used to invoke JdoHelper.getEnhancer(ClassLoader) and to remove it from the project dependencies, so that log4j.properties file will be found in the root directory of the class loader used to load log4j. I have been able to make this approach work in a test environment; however, it entails removing springframework from the dependencies as well, since it has log4j as a transitive dependency. (To verify this, run mvn -X jdo-exectck:enhance.) I need input on how to proceed.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: (was: jdo706.patch)
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Craig L Russell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234145#comment-13234145 ]
Craig L Russell commented on JDO-706:
-------------------------------------
Can you try creating a class loader that has the log4j.properties (nothing else) and set it as the context class loader? I don't think anything else in the enhancer depends on the context class loader. The exectck creates a class loader from which to load the enhancer implementation, and then exectck passes another class loader to the enhancer implementation that contains the classes and metadata to enhance. So replacing the context class loader should be innocuous in this context.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274375#comment-13274375 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
The patch (with some modifications) has been checked in, along with changes to AbstractGetPMF to fix the test errors due to mismatched file separator characters. To run the TCK, you must place the following files (or latest versions thereof) in the top-level lib/jdori:
asm-3.0.jar
datanucleus-core-3.0.9.jar
log4j-1.2.13.jar
datanucleus-api-jdo-3.0.7.jar
datanucleus-enhancer-3.0.1.jar
log4j.properties
datanucleus-api-jpa-3.0.8.jar
datanucleus-rdbms-3.0.8.jar
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: jdo-706.patch
Patch removes connection pooling jars from maven dependencies, updates README.html
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253570#comment-13253570 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
Running with correct versions of jars in top level lib/jdori/ resolves most, but not all test errors.
asm-3.0.jar, datanucleus-core-3.0.9.jar, log4j-1.2.13.jar. datanucleus-api-jdo-3.0.7.jar, datanucleus-enhancer-3.0.1.jar, log4j.properties,datanucleus-api-jpa-3.0.8.jar datanucleus-rdbms-3.0.8.jar
Still observer errors on pmf test, failure on jdoql test.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278715#comment-13278715 ]
Andy Jefferson commented on JDO-706:
------------------------------------
Works fine with that patch. Thx.
Before commit I would suggest the README.html is updated further to remove the "commons-dbcp", "commons-pool" jars since the "jdori-pmf.properties" (and the other two equivalents in src/conf) has selected C3P0 as the connection pool in use for the RI, so DBCP (commons-dbcp, commons-pool) is not needed at all
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279397#comment-13279397 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
Modified patch checked in.
The issue remains open in the hope of finding a way to make it easier for users to obtain the jars that now must be manually copied to lib/jdori.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: jdo706.patch
Uploading a patch for safekeeping. This doesn't yet work, but I think it's close.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Attachments: jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-706:
--------------------------------
Attachment: jdo706.patch
Runs with errors. 11/91 configurations fail. 7 failures, 34 errors out of 1724 tests. Repeated error:
>> Error moving implementation log file Failed to delete original file 'C:\jdo_newest\datanucleus.txt' after copy to 'C:\jdo_newest\tck\target\logs\...-jdori.txt'
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Attachments: jdo706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (JDO-706) No enhancer log output with maven
2
Posted by Michelle Caisse <mc...@sonic.net>.
The context class loader contains tck/target/classes and either
lib/jdori or lib/iut, which is the location of log4j.properties works
for enhancement. The enhancer seems to need the ASM jar file in the same
loader as the classes to be enhanced. So at this point, I'm only using
one classloader both to get the enhancer and to configure the enhancer.
So far, so good, but more testing is needed.
-- Michelle
On 3/25/2012 9:42 AM, Craig L Russell wrote:
> Very Cool!
>
> So what is the class loader configuration that makes it all work? Is
> the solution "portable" to iut?
>
> Craig
>
> On Mar 24, 2012, at 5:28 PM, Michelle Caisse (Commented) (JIRA) wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237742#comment-13237742
>> ]
>>
>> Michelle Caisse commented on JDO-706:
>> -------------------------------------
>>
>> I have enhancement working with no errors or warnings now. I need to
>> include tck/target/classes on the classpath. Without it, log4j
>> complains that it can't find org.apache.jdo.tck.util.TCKFileAppender
>> and the ri enhancer complains that it can't find
>> org/apache/jdo/tck/util/DeepEquality.
>>
>>> No enhancer log output with maven 2
>>> -----------------------------------
>>>
>>> Key: JDO-706
>>> URL: https://issues.apache.org/jira/browse/JDO-706
>>> Project: JDO
>>> Issue Type: Bug
>>> Components: tck
>>> Affects Versions: JDO 3 maintenance release 1 (3.1)
>>> Reporter: Michelle Caisse
>>> Assignee: Michelle Caisse
>>>
>>> No log output for enhancement is produced. The following warnings
>>> are issued:
>>> [INFO] [jdo-exectck:enhance {execution: default-cli}]
>>> log4j:WARN No appenders could be found for logger
>>> (DataNucleus.Enhancer).
>>> log4j:WARN Please initialize the log4j system properly.
>>> Enhancing classes for identity type datastoreidentity
>>> The classpath available to the enhancer does not provide access to
>>> the log properties file.
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators:
>> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>> For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
Re: [jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by Craig L Russell <cr...@oracle.com>.
Very Cool!
So what is the class loader configuration that makes it all work? Is
the solution "portable" to iut?
Craig
On Mar 24, 2012, at 5:28 PM, Michelle Caisse (Commented) (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237742
> #comment-13237742 ]
>
> Michelle Caisse commented on JDO-706:
> -------------------------------------
>
> I have enhancement working with no errors or warnings now. I need to
> include tck/target/classes on the classpath. Without it, log4j
> complains that it can't find org.apache.jdo.tck.util.TCKFileAppender
> and the ri enhancer complains that it can't find org/apache/jdo/tck/
> util/DeepEquality.
>
>> No enhancer log output with maven 2
>> -----------------------------------
>>
>> Key: JDO-706
>> URL: https://issues.apache.org/jira/browse/JDO-706
>> Project: JDO
>> Issue Type: Bug
>> Components: tck
>> Affects Versions: JDO 3 maintenance release 1 (3.1)
>> Reporter: Michelle Caisse
>> Assignee: Michelle Caisse
>>
>> No log output for enhancement is produced. The following warnings
>> are issued:
>> [INFO] [jdo-exectck:enhance {execution: default-cli}]
>> log4j:WARN No appenders could be found for logger
>> (DataNucleus.Enhancer).
>> log4j:WARN Please initialize the log4j system properly.
>> Enhancing classes for identity type datastoreidentity
>> The classpath available to the enhancer does not provide access to
>> the log properties file.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237742#comment-13237742 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
I have enhancement working with no errors or warnings now. I need to include tck/target/classes on the classpath. Without it, log4j complains that it can't find org.apache.jdo.tck.util.TCKFileAppender and the ri enhancer complains that it can't find org/apache/jdo/tck/util/DeepEquality.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269273#comment-13269273 ]
Michael Bouschen commented on JDO-706:
--------------------------------------
I get different results when running the latest patch on WIndows. Only pmf.conf is failing for applicationidentity and datastoreidentity:
Total tests run: 1798. Failures: 0, Errors: 8.
2 of 117 configurations failed.
When running on mac all configurations pass.
It looks like with the patch the datanucleus log file is generate with the expected filename (e.g. app-jdoql-datanucleus.txt). I think this is the reason for the error messages:
Error moving implementation log file Source '/Users/mbouschen/Projects/JDO/workspace/jdo/trunk/datanucleus.txt' does not exist
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279131#comment-13279131 ]
Michael Bouschen commented on JDO-706:
--------------------------------------
I could successfully run the patch on Mac and on Windows:
Total tests run: 1798.
All (117) configurations passed.
I do not see any errors when running the query tests on Windows.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JDO-706) No enhancer log output with maven 2
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-706.
----------------------------------
Resolution: Fixed
I checked in the patch adding a new module copyjdorijars.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234066#comment-13234066 ]
Michelle Caisse commented on JDO-706:
-------------------------------------
log4j: Trying to find [log4j.xml] using context classloader org.codehaus.classworlds.RealmClassLoader@143d2a58.
log4j: Trying to find [log4j.xml] using org.codehaus.classworlds.RealmClassLoader@143d2a58 class loader.
log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context classloader org.codehaus.classworlds.RealmClassLoader@143d2a58.
log4j: Trying to find [log4j.properties] using org.codehaus.classworlds.RealmClassLoader@143d2a58 class loader.
log4j: Trying to find [log4j.properties] using ClassLoader.getSystemResource().
log4j: Could not find resource: [null].
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
Posted by "Michael Bouschen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-706:
---------------------------------
Fix Version/s: JDO 3 maintenance release 1 (3.1)
> No enhancer log output with maven 2
> -----------------------------------
>
> Key: JDO-706
> URL: https://issues.apache.org/jira/browse/JDO-706
> Project: JDO
> Issue Type: Bug
> Components: tck
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo706.patch, jdo706.patch
>
>
> No log output for enhancement is produced. The following warnings are issued:
> [INFO] [jdo-exectck:enhance {execution: default-cli}]
> log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
> log4j:WARN Please initialize the log4j system properly.
> Enhancing classes for identity type datastoreidentity
> The classpath available to the enhancer does not provide access to the log properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira