Error while deploying a simple MDB

[Rakesh Rajagopalan]

Hi All,

Im getting org.jboss.deployers.spi.DeploymentException while trying to deploy a simple MDB in JBoss 5. The code of the bean and the client are as follows:

1. jbossmq-RakeshQueue-service.xml:
----------------------------------------------

  <server> 
<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination: service=Queue, name=RakeshQueue"> 
<depends optional-attribute-name="MessageConsumer">jboss.mq:service=MessageConsumer</depends>
</mbean> 
</server> 
   

2. MDB Class:
----------------

  
package mdbtest;

import javax.ejb.*;
import javax.jms.*;

@MessageDriven(name = "MessageConsumer", activationConfig = {
		@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
		@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
		@ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/RakeshQueue") })
public class MessageConsumer implements MessageListener {

	public void onMessage(Message arg0) {
		TextMessage message = (TextMessage) arg0;
		System.out.println("The message is: ========>>>>>>" + message);
	}

}
  

3. Client:
-----------

 
package mdbtest;

import javax.annotation.Resource;
import javax.jms.*;

public class MessageProducer {
	@Resource(name = "jms/QueueConnectionFactory")
	private ConnectionFactory connectionFactory;
	@Resource(name = "jms/RakeshQueue")
	private Destination destination;

	public MessageProducer() {
		try {
			Connection connection = connectionFactory.createConnection();
			Session session = connection.createSession(true,
					Session.AUTO_ACKNOWLEDGE);
			javax.jms.MessageProducer producer = session
					.createProducer(destination);
			ObjectMessage message = session.createObjectMessage();
			message.setObject("Hello World");
			producer.send(message);
			session.close();
			connection.close();
		} catch (Exception ex) {
			ex.printStackTrace();
		}
	}

	public static void main(String[] args) {
		new MessageProducer();
	}
	
}

4. The stack trace:
----------------------

00:14:28,031 ERROR [STDERR] [Fatal Error] jbossmq-RakeshQueue-service.xml:1:1: Content is not allowed in prolog.
00:14:28,031 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/D:/jboss-5.0.0/server/default/deploy/jbossmq-RakeshQueue-service.xml state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/D:/jboss-5.0.0/server/default/deploy/jbossmq-RakeshQueue-service.xml
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
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 org.jboss.deployers.vfs.spi.deployer.JAXPDeployer.doParse(JAXPDeployer.java:196)
	at org.jboss.deployers.vfs.spi.deployer.JAXPDeployer.parse(JAXPDeployer.java:167)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
	at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239)
	at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:336)
	... 27 more
00:14:28,031 WARN  [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** CONTEXTS IN ERROR: Name -> Error

vfsfile:/D:/jboss-5.0.0/server/default/deploy/jbossmq-RakeshQueue-service.xml -> org.xml.sax.SAXParseException: Content is not allowed in prolog.


	at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
    

I request you to point out the steps I need to follow to get this corrected.

Kind Regards,
Rakesh.R

[Adrien Ruffie]

Hello Rakesh,

Sometimes the "org.xml.sax.SAXParseException: Content is not allowed in prolog." mean the error occured in the xml file
here: jbossmq-RakeshQueue-service.xml


jbossmq-RakeshQueue-service.xml:1:1: Content is not allowed in prolog.

This mean you can have a error at the first line & first column off you xml file.

1) if you have a tab or whitespace before <server> at line 1, remove the whitespace or the caracter.
2) after check & validate the xml with jboss DTD or XSD, if <server> is the root element xml, if code attribute is allowed in mbean...
3) check if you Queue / Destination are present and available in your JBoss App.
4) check the mapping



best regards,

Adrien

[Adrien Ruffie]

For the deployement of JMS resources (it is for GlassFish but you can "inspire" for many parameters) with this :


http://adrien-ruffie.blogspot.com/2009/01/auto-jms-resources-deployement-in.html

I say "inspire" because GlasshFish is not JBoss

[Rakesh Rajagopalan]

Adrien,

Its working now.. Thanks for your help

Regards,
Rakesh.R