| Summary: | EclipseLink DBWS does not provide details on eclipselink-dbws-sessions.xml load failure | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Evgeny <forrestline> | ||||||||||||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||||
| Severity: | normal | ||||||||||||||||||
| Priority: | P3 | CC: | david.mccann, michael.norman | ||||||||||||||||
| Version: | unspecified | ||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Hardware: | PC | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Evgeny
Created attachment 191720 [details]
Exception trace
Evgeny:
I looked at the exception trace and it shows in XRServiceFactory (line ~226)
the specific DBWSException for the above situation ("Could not locate file").
What app server are you deploy the Web service to?
Could you attach the jar file as well as the dbws-builder.xml file?
Thanks in advance,
Mike Norman
I have tried :
Weblogic 10.3.0 (wls options)
JBoss 5.1.0 (jboss option)
Standalone (javase option)
I have a feeling that a dependency might be missing or something else that prevents
{{{
try {
found = loader.load(sessionManager, projectLoader);
}
catch (RuntimeException e) { /* ignore */
}
from working out correctly. Yet the RuntimeException is suppressed.
Attaching WebLogic .WAR and the standalone .JAR.
Created attachment 191806 [details]
Deployment generated for WebLogic
Created attachment 191807 [details]
Standalone package
Evgeny: The root-cause is the <property name="logLevel">DEBUG</property> - DEBUG is not one of the accepted values: off, severe, warning, info, config, fine, finer, finest, all However, you are right - this fact is 'swallowed-up' by the logic in 'loader.load(sessionManager, projectLoader)' and all we get is 'cannot locate eclipselink-dbws-sessions.xml' which isn't quite true. If it is alright by you, I'll use this bug to track this issue, ok? Mike Norman Thanks a lot for the solution! And, of cause, use the bug as you please. Created attachment 198414 [details]
Proposed fix.
Created attachment 198415 [details]
Supporting test cases.
Created attachment 198476 [details]
Proposed fix v2 (use statics from SessionLog for log levels)
Created attachment 198477 [details]
Supporting test cases.
Reviewed by: michael.norman@oracle.com Tests: n/a Revision: 9612 Ignore previous commit comments! Reviewed by: michael.norman@oracle.com Tests: dbws/testing/loglevelvalidation/LogLevelValidationTestSuite; all unit tests pass as expected Revision: 9613 Ignore this! (In reply to comment #12) > Reviewed by: michael.norman@oracle.com > Tests: n/a > Revision: 9612 Note that our resolution of this issue only addresses the DBWS builder portion, not the runtime. Bug 350164 (DBWS: Better runtime validation and error handling required) has been opened to track changes to the DBWS runtime. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |