[JBoss Messaging] - Integrating Websphere MQ with JBoss
by ejb3workshop
I have deployed the JCA Resource Adaptor for Websphere MQ on JBoss and able to pull messages of a queue. However currently the MQ hostname is configured either via annotations as shown below. Since I also specify these setting in the wmq.jmsra-ds.xml file (see below) I was hoping to proxy the MQQueue and access it as an standard jms destination. This would allow me to keep my code and descriptors separate from the MQ configuration (Queue Manager, Hostname, Port etc). However trying this I got
anonymous wrote :
| java.lang.ClassCastException: com.ibm.mq.jms.MQQueue cannot be cast to org.jboss.jms.destination.JBossDestination
| at org.jboss.jms.client.container.SessionAspect.handleCreateConnectionConsumer(SessionAspect.java:737)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect1.invoke(SessionAspect1.java)
After adding the reference to the resource adaptor used (wmq.jmsra.rar) back in, this problem disappeared, but it ask for the MQ configuration again. Ideally I would like to configure the MQ Queue / ConnectionFactory in the application server and access it from my application as a standard JMS destination. This would allow me to keep my code portable.
If you have any suggestion on how this can be achieved, please let me know.
Thanks in advance
Alex
| @MessageDriven(name = "MQRequestListener", activationConfig = {
| @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
| @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "10"),
| @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "Non-Durable"),
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
| @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/thunderhead/MQRequests")
| @ActivationConfigProperty(propertyName = "channel", propertyValue = "SYSTEM.DEF.SVRCONN"),
| @ActivationConfigProperty(propertyName = "hostName", propertyValue = "zeta"),
| @ActivationConfigProperty(propertyName = "port", propertyValue = "5001"),
| })
| @org.jboss.annotation.ejb.ResourceAdapter(value="wmq.jmsra.rar")
|
or in the deployment descriptor :
| ...
| <activation-config-property>
| <activation-config-property-name>destinationType</activation-config-property-name>
| <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>destination</activation-config-property-name>
| <activation-config-property-value>WASQueue1</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>channel</activation-config-property-name>
| <activation-config-property-value>SYSTEM.DEF.SVRCONN</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>hostName</activation-config-property-name>
| <activation-config-property-value>zeta</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>port</activation-config-property-name>
| <activation-config-property-value>5001</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>queueManager</activation-config-property-name>
| <activation-config-property-value>QM_Thunderhead</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>transportType</activation-config-property-name>
| <activation-config-property-value>CLIENT</activation-config-property-value>
| </activation-config-property>
| ...
|
WebSphere MQ adaptor configuration
| <?xml version="1.0" encoding="UTF-8"?>
|
| <connection-factories>
|
| <!-- mbeans defining JCA administered objects -->
| <mbean code="org.jboss.resource.deployment.AdminObject" name="jboss.jca:service=WASDestination,name=MQRequests">
|
| <!-- Bind this AdminObject with the JNDI name IVTQueue -->
| <attribute name="JNDIName">queue/thunderhead/MQRequests</attribute>
|
| <!-- this MBean depends on the WebSphere MQ resource adapter -->
| <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'</depends>
|
| <!-- this admin object is a javax.jms.Queue -->
| <attribute name="Type">javax.jms.Queue</attribute>
|
| <!--
| Configuration for Queue TEST.QUEUE on queue manager ExampleQM. All messages sent
| to this queue will have their expiry time overridden so that messages never expire
| -->
| <attribute name="Properties">
| baseQueueManagerName=QM_Thunderhead
| baseQueueName=WASQueue1
| </attribute>
| </mbean>
|
| <!-- JCA Connection factory definitions -->
| <tx-connection-factory>
|
| <!-- Bind this ConnectionFactory with the JNDI name IVTCF -->
| <jndi-name>MQConnectionFactory</jndi-name>
|
| <!-- Indicate that the connection factory supports XA transactions -->
| <xa-transaction />
|
| <!-- rar-name is the actual RAR file name, in this case wmq.jmsra.rar -->
| <rar-name>wmq.jmsra.rar</rar-name>
|
| <!-- connection-definition is the ConnectionFactory interface
| defined in the ra.xml -->
| <connection-definition>javax.jms.ConnectionFactory</connection-definition>
|
| <!--
| Configuration for the ConnectionFactory. This defines the channel, hostname, port,
| queueManager, and transportType properties for a client (TCP/IP) connection to WMQ
| -->
| <config-property name="channel" type="java.lang.String">SYSTEM.DEF.SVRCONN</config-property>
| <config-property name="hostName" type="java.lang.String">zeta</config-property>
| <config-property name="port" type="java.lang.String">5001</config-property>
| <config-property name="queueManager" type="java.lang.String">QM_Thunderhead</config-property>
| <config-property name="transportType" type="java.lang.String">CLIENT</config-property>
|
| <!-- define security domain -->
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| </tx-connection-factory>
| </connection-factories>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173910#4173910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173910
17 years, 7 months
[Security & JAAS/JBoss] - Re: Dynamic login config broken in JBoss 5 Beta4
by jaikiran
I tried this on JBoss-5 CR1 and even JBoss-5 Beta4. Looks like something changed between Beta 4 and CR1. The application that works on Beta 4, does not work on CR1. However, i could get the application to work on CR1 too by placing the xml at a different location.
Here are the details. I have an EAR file which has a test-jboss-service.xml, a dynamic-login-config.xml, a jboss-app.xml and a WAR file. For JBoss-5 Beta 4, here's the EAR contents:
| ZEJB3Persistence.ear
| |
| |--- META-INF
| | |
| | |--- application.xml
| | |
| | |--- jboss-app.xml
| |
| |
| |--- test-jboss-service.xml
| |
| |
| |--- MyApp.war
| | |
| | |--- WEB-INF
| | | |
| | | |--- classes
| | | | |
| | | | |--- dynamic-login-config.xml
|
|
|
The dynamic-login-config.xml was in the EAR/WAR/WEB-INF/classes folder. The jboss-app.xml pointed to the service file:
| <jboss-app>
|
| <module>
| <service>test-jboss-service.xml</service>
| </module>
| </jboss-app>
The test-jboss-service.xml looks like:
<server>
| <mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
| name="jboss:service=DynamicLoginConfig">
| <attribute name="AuthConfig">dynamic-login-config.xml</attribute>
| <depends optional-attribute-name="LoginConfigService">jboss.security:service=XMLLoginConfig</depends>
| <depends optional-attribute-name="SecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
| </mbean>
| </server>
|
This worked without any issues in Beta 4. I could see this in the server.log:
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.system.ServiceConfigurator] AuthConfig set to dynamic-login-config.xml in jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.system.ServiceConfigurator] LoginConfigService set to jboss.security:service=XMLLoginConfig in jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.system.ServiceConfigurator] SecurityManagerService set to jboss.security:service=JaasSecurityManager in jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Creating jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Created jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,733 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Starting jboss:service=DynamicLoginConfig
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Using JAAS AuthConfig: vfsfile:/D:/jboss-5.0.0.Beta4/server/jaikiran/deploy/ZEJB3Persistence.ear/myapp.war/WEB-INF/classes/dynamic-login-config.xml
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=vfsfile:/D:/jboss-5.0.0.Beta4/server/jaikiran/deploy/ZEJB3Persistence.ear/myapp.war/WEB-INF/classes/dynamic-login-config.xml
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@f7b18, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@f7b18, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Loaded config: simple-security-domain
| 2008-09-03 15:00:55,858 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Started jboss:service=DynamicLoginConfig
|
This same application fails with the following exception on JBoss 5 CR1:
| 15:24:02,470 ERROR [AbstractKernelController] Error installing to Start: name=jboss:service=DynamicLoginConfig state=Create mode=Manual requiredState=Installed
| org.jboss.deployment.DeploymentException: Failed to find authConf as resource: dynamic-login-config.xml
| at org.jboss.security.auth.login.DynamicLoginConfig.startService(DynamicLoginConfig.java:236)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
| at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
| at $Proxy35.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:271)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:664)
| at org.jboss.system.ServiceController.start(ServiceController.java:436)
| at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
| at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:279)
| at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
| at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1326)
| at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1293)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:793)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:624)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:442)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:88)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:46)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:991)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:257)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:135)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:544)
| at java.lang.Thread.run(Thread.java:595)
"anil.saldhana(a)jboss.com" wrote : For an ear, if you have a war underneath the resource(xml file) can be under WEB-INF/classes. If not, you can have ear/lib/somejar/xyz.xml or you will need to use the manifest to define classpath entries.
|
| For an ear, the classpath will not include the root of the ear. Hence META-INF/xyz.xml will not be detected. ear->lib, ear->war->WEB-INF/classes are on the classpath.
In CR1, i then moved the dynamic-login-config.xml to the EAR/lib folder. Even that did not work. Failed with the same error.
Finally, to get this working, i moved the dynamic-login-config.xml to the root of the EAR:
| ZEJB3Persistence.ear
| |
| |--- META-INF
| | |
| | |--- application.xml
| | |
| | |--- jboss-app.xml
| |
| |
| |--- test-jboss-service.xml
| |
| |--- dynamic-login-config.xml
| |
| |
| |--- MyApp.war
| | |
| | |--- WEB-INF
| | | |
| | | |--- classes
|
This worked in CR1. Here are the logs which show that the dynamic-login-config.xml got picked up from the root of the EAR:
2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=DynamicLoginConfig with code: org.jboss.security.auth.login.DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceCreator] Created mbean: jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceConfigurator] AuthConfig set to dynamic-login-config.xml in jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceConfigurator] LoginConfigService set to jboss.security:service=XMLLoginConfig in jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceConfigurator] SecurityManagerService set to jboss.security:service=JaasSecurityManager in jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Creating jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Created jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,958 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Starting jboss:service=DynamicLoginConfig
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Using JAAS AuthConfig: vfsfile:/D:/jboss-5.0.0.CR1/server/jaikiran/deploy/ZEJB3Persistence.ear/dynamic-login-config.xml
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=vfsfile:/D:/jboss-5.0.0.CR1/server/jaikiran/deploy/ZEJB3Persistence.ear/dynamic-login-config.xml
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@14d25c6, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@14d25c6, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Loaded config: simple-security-domain
| 2008-09-03 15:27:12,974 DEBUG [org.jboss.security.auth.login.DynamicLoginConfig] Started jboss:service=DynamicLoginConfig
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173909#4173909
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173909
17 years, 7 months
[JBossWS] - schemavalidation: fault not returned to calling client
by ljgp
Hi,
I am using JBoss 4.2.2 and
I was expecting that a schemavalidation error would by default be passed on to the client as a SOAP fault. I am observing that the exceptions show up in the app server logs, but that the client does not get any response (except for the header).
I tried both without a custom error handler, and with my own handler, throwing an exception from handleError(). Both gave the same result: no output sent to the client.
I must be missing something here, any help is appreciated.
Cheers, Luc.
The header is:
HTTP/1.1 200 OK
Date: Wed, 03 Sep 2008 10:03:33 GMT
Content-Length: 0
Content-Type: text/xml;charset=UTF-8
X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5
Server: Apache-Coyote/1.1
In the logs it says:
12:03:33,416 INFO [SOAPBodyElementDoc] Validating: XML_VALID
12:03:33,447 ERROR [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'Service'. One of '{Schema}' is expected.
12:03:33,462 ERROR [RequestHandlerImpl] Error processing web service request
org.jboss.ws.WSException: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'Service'. One of '{Schema}' is expected.
at org.jboss.ws.WSException.rethrow(WSException.java:68)
at org.jboss.ws.core.soap.SOAPBodyElementDoc.validatePayload(SOAPBodyElementDoc.java:130)
at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:90)
at org.jboss.ws.core.soap.SOAPContentElement.writeElement(SOAPContentElement.java:547)
at org.jboss.ws.core.soap.SOAPElementImpl.writeElementContent(SOAPElementImpl.java:840)
at org.jboss.ws.core.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:825)
at org.jboss.ws.core.soap.SOAPElementImpl.writeElementContent(SOAPElementImpl.java:840)
at org.jboss.ws.core.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:825)
at org.jboss.ws.core.soap.SOAPElementWriter.writeElementInternal(SOAPElementWriter.java:149)
at org.jboss.ws.core.soap.SOAPElementWriter.writeElement(SOAPElementWriter.java:130)
at org.jboss.ws.core.soap.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:326)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.sendResponse(RequestHandlerImpl.java:392)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:321)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173905#4173905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173905
17 years, 7 months
[JBoss Messaging] - JBM server shutdown curiously when jboss cluster is running.
by funnyone
We have three nodes in our jboss cluster. We deployed our JBM server on one of three nodes. But in recent days we found our JBM server shutdown curiously when the jboss cluster is running. And all topic was closed.
We checked the server.log in the /server/default/log and found the following information:
2008-09-03 11:29:42,628 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/DLQ] stopped
| 2008-09-03 11:29:42,630 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/ExpiryQueue] stopped
| 2008-09-03 11:29:42,631 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/testTopic] stopped
| 2008-09-03 11:29:42,633 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/securedTopic] stopped
| 2008-09-03 11:29:42,634 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/testDurableTopic] stopped
| 2008-09-03 11:29:42,635 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/testQueue] stopped
| 2008-09-03 11:29:42,636 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/A] stopped
| 2008-09-03 11:29:42,637 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/B] stopped
| 2008-09-03 11:29:42,638 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/C] stopped
| 2008-09-03 11:29:42,640 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/D] stopped
| 2008-09-03 11:29:42,641 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/ex] stopped
| 2008-09-03 11:29:42,642 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/PrivateDLQ] stopped
| 2008-09-03 11:29:42,644 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/PrivateExpiryQueue] stopped
| 2008-09-03 11:29:42,645 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/QueueWithOwnDLQAndExpiryQueue] stopped
| 2008-09-03 11:29:42,646 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/TopicWithOwnDLQAndExpiryQueue] stopped
| 2008-09-03 11:29:42,648 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/QueueWithOwnRedeliveryDelay] stopped
| 2008-09-03 11:29:42,649 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/TopicWithOwnRedeliveryDelay] stopped
| 2008-09-03 11:29:42,650 INFO [DRM Async Publisher#0] destination.QueueService (
| QueueService.java:189) - Queue[/queue/testDistributedQueue] stopped
| 2008-09-03 11:29:42,651 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/testDistributedTopic] stopped
| 2008-09-03 11:29:42,653 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/cmtopic] stopped
| 2008-09-03 11:29:42,709 ERROR [WorkerThread#110[192.166.32.132:3212]] socket.ServerThread
| ( ServerThread.java:377) - Worker thread initialization failure
| java.io.EOFException
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:529)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| 2008-09-03 11:29:42,754 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/cmomttopic] stopped
| 2008-09-03 11:29:42,756 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/Fm4NeaTopic] stopped
| 2008-09-03 11:29:42,758 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/FmTopic] stopped
| 2008-09-03 11:29:42,760 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/FmOmtTopic] stopped
| 2008-09-03 11:29:42,864 INFO [JMS SessionPool Worker-2] server.AbstractCommonMDB (
| AbstractCommonMDB.java:48) - [RouterMDB]receive msg id:50 sequenceId=79742
| 2008-09-03 11:29:42,866 INFO [JMS SessionPool Worker-2] server.AbstractCommonMDB (
| AbstractCommonMDB.java:48) - [RouterMDB]receive msg id:50 sequenceId=79743
| 2008-09-03 11:29:49,837 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/FmNbiTopic] stopped
| 2008-09-03 11:29:49,840 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/LMTopic] stopped
| 2008-09-03 11:29:49,842 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/LMOmtTopic] stopped
| 2008-09-03 11:29:49,844 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/sectopic] stopped
| 2008-09-03 11:29:49,846 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/RouteTopic] stopped
| 2008-09-03 11:29:49,847 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/smtopic] stopped
| 2008-09-03 11:29:49,849 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/topotopic] stopped
| 2008-09-03 11:29:49,850 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/Fm2TopoTopic] stopped
| 2008-09-03 11:29:49,853 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/PmTopic] stopped
| 2008-09-03 11:29:49,854 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/Pm4NeaTopic] stopped
| 2008-09-03 11:29:49,855 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/Pm4ServerTopic] stopped
| 2008-09-03 11:29:49,856 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/TDMTopic] stopped
| 2008-09-03 11:29:49,860 INFO [DRM Async Publisher#0] destination.TopicService (
| TopicService.java:179) - Topic[/topic/TDMOmtTopic] stopped
| 2008-09-03 11:29:49,867 ERROR [WorkerThread#29[192.166.32.8:59979]] remoting.ServerInvoker
| ( ServerInvoker.java:1820) - Error executing server oneway invocation request:
| InvocationRequest[12e727b, JMS, org.jboss.jms.wireformat.SessionSendRequest@5deceb]
| org.jboss.jms.exception.MessagingShutdownException: Cannot handle invocation since messaging server
| is not active (it is either starting up or shutting down)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:
| 133)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
| at org.jboss.remoting.ServerInvoker$1.run(ServerInvoker.java:1815)
| at org.jboss.jms.server.remoting.DirectThreadPool.run(DirectThreadPool.java:63)
| at org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:1826)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:758)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| 2008-09-03 11:29:49,872 ERROR [WorkerThread#29[192.166.32.8:59979]] remoting.ServerInvoker
| ( ServerInvoker.java:1820) - Error executing server oneway invocation request:
| InvocationRequest[6d7710, JMS, org.jboss.jms.wireformat.SessionSendRequest@a3d239]
| org.jboss.jms.exception.MessagingShutdownException: Cannot handle invocation since messaging server
| is not active (it is either starting up or shutting down)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:
| 133)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
| at org.jboss.remoting.ServerInvoker$1.run(ServerInvoker.java:1815)
| at org.jboss.jms.server.remoting.DirectThreadPool.run(DirectThreadPool.java:63)
| at org.jboss.remoting.ServerInvoker.handleOnewayInvocation(ServerInvoker.java:1826)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:758)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:572)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
it was already confirmed that nobody executed shutdown() or stop() operation using jboss web-console. It's just like JBM server shutdown itself, and we don't know what is the cause.
any help will be greatly appreciated here.
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173902#4173902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173902
17 years, 7 months