Sonar 8.3 XML parsing error on Tibco files

SonarQube Server / Community Build
1

We are using tibco bw built for scanning our bw6 projects through Sonar 8.3 as part of our build pipeline.

But Sonar is treating files as XML and failing to scan and giving below error.

[WARNING] Not able to handle this file as XML [MANIFEST.MF] 
org.sonarsource.analyzer.commons.xml.ParseException: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
	at org.sonarsource.analyzer.commons.xml.XmlParser.<init>(XmlParser.java:73)
	at org.sonarsource.analyzer.commons.xml.XmlFile.create(XmlFile.java:90)
	at com.tibco.sonar.plugins.bw6.source.XmlSource.<init>(XmlSource.java:22)
	at com.tibco.sonar.plugins.bw6.sensor.ProcessRuleSensor.checkCustom(ProcessRuleSensor.java:472)
	at com.tibco.sonar.plugins.bw6.sensor.ProcessRuleSensor.execute(ProcessRuleSensor.java:306)
	at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:48)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:85)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1(ModuleSensorsExecutor.java:59)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy(ModuleSensorsExecutor.java:77)
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:59)
	at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:82)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)
	at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:386)
	at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:382)
	at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:351)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)
	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:141)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)
	at org.sonar.batch.bootstrapper.Batch.doExecute(Batch.java:72)
	at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:66)
	at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:46)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)
	at com.sun.proxy.$Proxy25.execute(Unknown Source)
	at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:185)
	at org.sonarsource.scanner.api.EmbeddedScanner.execute(EmbeddedScanner.java:137)
	at org.sonarsource.scanner.maven.bootstrap.ScannerBootstrapper.execute(ScannerBootstrapper.java:65)
	at org.sonarsource.scanner.maven.SonarQubeMojo.execute(SonarQubeMojo.java:104)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at java.xml/javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:122)
	at org.sonarsource.analyzer.commons.xml.XmlParser.<init>(XmlParser.java:62)
	... 55 common frames omitted

Let me know how to fix this or is there a work around to handle such errors during code scanning.

2

Hi,

Welcome to the community!

You can handle this with file extensions. Configure XML to not recognize/treat your bw6 files as XML. (Project Settings -> General Settings -> Languages -> XML)

 
HTH,
Ann

3

Where can i find this option in sonar 8.3?

4

Hi,

You need to be a project admin to see the Project Settings option on your project homepage.

 
Ann

5

I can see the Administration tab, where do i go from there?

“Project Settings -> General Settings” this menu is not avlble though.

6

Hi,

If you don’t see “Project Settings”

Selection_999(148)

Then you’re not a project admin. But with access to the global Administration menu you can grant yourself that priv if you like.

 
Ann

7

I don’t have bw6 files treated as xml files under the project settings. How come those are treated as xml files?
Moreover i was looking to control these settings from Quality Profiles levels not from individual project level. Because i have hundreds of bw6 projects which use 1 quality profile.

image
image891×409 4.73 KB

8

Hi,

Since you’re talking about setting this globally, then you can attack it from the global Administration menu and set it once there for all projects.

Setting that aside, is your screenshot above from the project on which you got the initially reported error (about Manifest.MF)?

 
Ann

9

yes, this screenshot is from the same project.

10

image
image1042×557 16.3 KB

Is this the section i need to modify? It has already prepopulated values set and it seems good.
What all details i need to modify?

11

Based on the stacktrace, it seems to me that the problem comes from a Tibco plugin which tries to parse MANIFEST.MF as an XML file. This Tibco plugin is not developed by SonarSource.