5:08 a.m.
Do we have any plans to capture cryptic error messages experienced while
working with AS7 so we can review if there are better ways the problem
can be reported?
Over the past week I have experienced the two errors at the end of this
e-mail.
The first of these errors was reported because a subsystem had not read
all of it's configuration but the reported error gives the impression
there may be a problem with the actual XML.
The second error although claiming an extension could not be found was
actually because the extension could not be loaded as the module
containing a class used by the extension was not referenced from the
module.xml.
Regards,
Darran Lofthouse.
===== 1 =====
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[142,91]
Message: Unexpected element '{urn:jboss:domain:osgi:1.0}configuration'
encountered
at
org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:61)
at
org.jboss.as.controller.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:383)
===== 2 =====
10:35:08,866 ERROR [org.jboss.msc] MSC-00001: Failed to start service
jboss.as.server-controller: org.jboss.msc.service.StartException in
service jboss.as.server-controller: Failed to start service
at
org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1207)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_23]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: java.util.ServiceConfigurationError:
org.jboss.as.controller.NewExtension: Provider
org.jboss.as.webservices.NewWSExtension not found
at java.util.ServiceLoader.fail(ServiceLoader.java:214) [:1.6.0_23]
at java.util.ServiceLoader.access$400(ServiceLoader.java:164) [:1.6.0_23]
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:350)
[:1.6.0_23]
5:59 a.m.
On 02/03/2011 05:08 AM, Darran Lofthouse wrote:
Do we have any plans to capture cryptic error messages experienced
while
working with AS7 so we can review if there are better ways the problem
can be reported?
Capture, no - but when they're encountered we should fix them.
Over the past week I have experienced the two errors at the end of
this
e-mail.
The first of these errors was reported because a subsystem had not read
all of it's configuration but the reported error gives the impression
there may be a problem with the actual XML.
Well, a bug in the XML parser will almost always look like an XML
parsing error. The only fix for that is to just not have any XML
parsing bugs.
The second error although claiming an extension could not be found
was
actually because the extension could not be loaded as the module
containing a class used by the extension was not referenced from the
module.xml.
This one is due to java.util.ServiceLoader - it eats exceptions instead
of chaining them so you can't see the underlying cause. I'm thinking
about ways to fix that.
--
- DML
6:06 a.m.
On 02/03/2011 11:59 AM, David M. Lloyd wrote:
On 02/03/2011 05:08 AM, Darran Lofthouse wrote:
> The first of these errors was reported because a subsystem had not read
> all of it's configuration but the reported error gives the impression
> there may be a problem with the actual XML.
Well, a bug in the XML parser will almost always look like an XML
parsing error. The only fix for that is to just not have any XML
parsing bugs.
I am wondering for this one if there is any way we can detect that a
subsystem did not read all of the elements under it's subsystem element
- if we could do that we may be able to report an error along the lines
of reporting that a specific subsystem has not read all the child content.
Regards,
Darran Lofthouse.
12:08 p.m.
On 2/3/11 6:06 AM, Darran Lofthouse wrote:
On 02/03/2011 11:59 AM, David M. Lloyd wrote:
> On 02/03/2011 05:08 AM, Darran Lofthouse wrote:
>> The first of these errors was reported because a subsystem had not read
>> all of it's configuration but the reported error gives the impression
>> there may be a problem with the actual XML.
>
> Well, a bug in the XML parser will almost always look like an XML
> parsing error. The only fix for that is to just not have any XML
> parsing bugs.
I am wondering for this one if there is any way we can detect that a
subsystem did not read all of the elements under it's subsystem element
- if we could do that we may be able to report an error along the lines
of reporting that a specific subsystem has not read all the child content.
I think that should be doable, just by calling XMLStreamReader.getName()
and validating that it returns the QName for the <profile> element.
Regards,
Darran Lofthouse.
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
3:40 a.m.
On 02/03/2011 12:59 PM, David M. Lloyd wrote:
On 02/03/2011 05:08 AM, Darran Lofthouse wrote:
...
> The second error although claiming an extension could not be found was
> actually because the extension could not be loaded as the module
> containing a class used by the extension was not referenced from the
> module.xml.
This one is due to java.util.ServiceLoader - it eats exceptions instead
of chaining them so you can't see the underlying cause. I'm thinking
about ways to fix that.
I wrote http://community.jboss.org/thread/162032 for
ServiceLoader failures.
Carlo
12:11 p.m.
On 2/3/11 5:08 AM, Darran Lofthouse wrote:
Do we have any plans to capture cryptic error messages experienced
while
working with AS7 so we can review if there are better ways the problem
can be reported?
Anytime you find this kind of thing, create a JIRA for it.
--
Jason T. Greene
JBoss, a division of Red Hat
5045
days inactive
5046
days old
5 comments
5 participants
participants (5)
-
Brian Stansberry -
Carlo de Wolf -
Darran Lofthouse -
David M. Lloyd -
Jason T. Greene