[EJB 3.0] - Unable to deploy a simple MDB with SwiftMQ on JBOSS 5
by omerlin13
Hello,
I was unable to deploy the MDB sample http://www.swiftmq.com/developers/howto_swiftmq_jboss404/ on JBoss 5 CR1
The example work fine on JBoss 4.2.2.
18:09:15,942 WARN [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.In
| terceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
| 18:09:16,535 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/D:/win32app/jboss-5.0.0.CR1/server/default/dep
| loy/simplemdb.ear state=Not Installed mode=Manual requiredState=Parse
| org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/D:/win32app/jboss-5.0.0.CR1/server/default/de
| ploy/simplemdb.ear/simplemdb-ejb.jar
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutp
| ut.java:343)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutp
| ut.java:303)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutp
| ut.java:275)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:
| 236)
| 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:1023)
| 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.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(Executors.java:417)
| at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
| at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: cvc-datatype-valid.1.2.1: 'queue/SimpleMessageEJB' is not
| a valid value for 'NMTOKEN'. @ vfszip:/D:/win32app/jboss-5.0.0.CR1/server/default/deploy/simplemdb.ear/simplemdb-ejb.jar/META-INF/ej
| b-jar.xml[8,50]
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:198)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutp
| ut.java:329)
| ... 27 more
| Caused by: org.xml.sax.SAXException: cvc-datatype-valid.1.2.1: 'queue/SimpleMessageEJB' is not a valid value for 'NMTOKEN'. @ vfszip
| :/D:/win32app/jboss-5.0.0.CR1/server/default/deploy/simplemdb.ear/simplemdb-ejb.jar/META-INF/ejb-jar.xml[8,50]
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
| at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
| ... 34 more
| 18:09:16,707 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
|
| vfszip:/D:/win32app/jboss-5.0.0.CR1/server/default/deploy/simplemdb.ear -> org.xml.sax.SAXException: cvc-datatype-valid.1.2.1: 'queu
| e/SimpleMessageEJB' is not a valid value for 'NMTOKEN'. @ vfszip:/D:/win32app/jboss-5.0.0.CR1/server/default/deploy/simplemdb.ear/si
| mplemdb-ejb.jar/META-INF/ejb-jar.xml[8,50]
|
|
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
| 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(Executors.java:417)
| at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
| at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:595)
|
|
My ejb-jar.xml is :
<?xml version="1.0" encoding="UTF-8"?>
| <!-- Copyright (c) 2003 Sun Microsystems, Inc. All rights reserved. -->
| <ejb-jar version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
| <display-name>SimpleMessageJAR</display-name>
| <enterprise-beans>
| <message-driven>
| <display-name>SimpleMessageEJB</display-name>
| <ejb-name>SimpleMessageEJB</ejb-name>
| <ejb-class>mdb.simple.SimpleMessageBean</ejb-class>
| <messaging-type>javax.jms.MessageListener</messaging-type>
| <transaction-type>Container</transaction-type>
| <activation-config>
| <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>
| sample1-input@router1
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| ConnectionFactoryName
| </activation-config-property-name>
| <activation-config-property-value>
| ConnectionFactory
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| Transacted
| </activation-config-property-name>
| <activation-config-property-value>
| true
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| Xa
| </activation-config-property-name>
| <activation-config-property-value>
| true
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| DeliveryOption
| </activation-config-property-name>
| <activation-config-property-value>
| A
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| MaxPoolSize
| </activation-config-property-name>
| <activation-config-property-value>
| 5
| </activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>
| MaxMessages
| </activation-config-property-name>
| <activation-config-property-value>
| 5
| </activation-config-property-value>
| </activation-config-property>
| </activation-config>
| </message-driven>
| </enterprise-beans>
|
| <assembly-descriptor >
| <container-transaction >
| <method >
| <ejb-name>SimpleMessageEJB</ejb-name>
| <method-name>*</method-name>
| </method>
| <trans-attribute>Required</trans-attribute>
| </container-transaction>
| </assembly-descriptor>
|
| </ejb-jar>
|
|
|
Does someone has achieve to do a simpleMDB on Jboss 5 with Swiftmq ??
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164403#4164403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164403
17 years, 12 months
[JBoss Messaging] - Re: Threads Hanging Indefinitely in ClosedInterceptor
by zackurey
I'm just now circling back on looking into this issue.
We upgraded remoting to SP8 and the client still hangs. It doesn't appear to be ClosedInterceptor where it gets stuck initially, as I had originally thought.
"QuartzScheduler_Worker-18" prio=1 tid=0x1b14c390 nid=0x351d runnable [0x19973000..0x19974020]
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)
- locked <0x3bd216f8> (a java.lang.Object)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:680)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
- locked <0x3bd21700> (a com.sun.net.ssl.internal.ssl.AppInputStream)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
- locked <0x3bd21718> (a java.io.BufferedInputStream)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:988)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:621)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:418)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.remoting.Client.invoke(Client.java:536)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeNext(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:114)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeNext(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeNext(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java)
After waiting for about 10 minutes for this condition to go away I bounced the messaging instance. Then I went to get another thread dump of my client app and this time it was stuck in ClosedInterceptor.
Just to give more info these are large( 1MB ), BytesMessages( can't wait for file messages in JBM 2.0 as we will need those to scale). We are using sslbisocket for the connections. Latency shouldn't be an issue as both JBoss messaging and client application, are living on the same server.
This issue seems to love to pop up on a system I have little control over experimentation with, and again have been unable to reproduce consistently with a test case elsewhere. So apologies for not much more information than the thread dumps, but any ideas would be very welcome at this point.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164402#4164402
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164402
17 years, 12 months
[JBoss jBPM] - Re: jBPM on GlassFish - HTTP status 500
by naruszef
"villatore" wrote : And the solution, wasssss??????? for run jBPM under other Java Aplication Server.
Hm solution - I think that it's not the simpliest way, but it works (almost):
Configure hibernate - easiest one :)
In deploy folder - ant customize.console.for.tomcat
In folder "target" You have to add some libraries - now I don't remember which ones - but I think that, it was libraries similar like in tomcat/websphere.
In file web.xml - change authorization method:
| <login-config>
| <auth-method>FORM</auth-method>
| <realm-name>GlassFishRealmName</realm-name>
| <form-login-config>
| <form-login-page>/ua/login-example.jsf</form-login-page>
| <form-error-page>/ua/login-example.jsf?error=true</form-error-page>
| </form-login-config>
| </login-config>
|
Now You have to configure in GlassFish JDBC Connection, Connection Pools and realms.
Realms - set jdbc realm, use connection pool configured earlier. User table: JPBM_ID_USER, user column: USER_ passwd column: PASSWORD_. For group table You need create new view in Your database : In this view You should have Name with user name, and Group with name of group connected to him. (You should have in this view only secure-roles).
Then set username, password for database.
I think that's all...
/If everything works - You will have problems with jbpm-console forms - I still don't know how to fix it - commenting bad lines is simpliest way to do it...
Regards
Jakub Naruszewicz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164399#4164399
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164399
17 years, 12 months