[JBoss JIRA] (WFLY-5252) Fix MDB20TestCase
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5252?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5252:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Fix MDB20TestCase
> -----------------
>
> Key: WFLY-5252
> URL: https://issues.jboss.org/browse/WFLY-5252
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Beta2
> Reporter: Jeff Mesnil
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> The MDB20TestCase is failing often on our test suite with the error:
> {noformat}
> java.lang.AssertionError: Reply message was null on reply queue: ActiveMQQueue[ejb2x/replyQueueB]
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at org.jboss.as.test.integration.ejb.mdb.ejb2x.MDB20TopicTestCase.testEjb20TopicMDBs(MDB20TopicTestCase.java:118)
> {noformat}
> From the logs, only 1 of the MDB receives the message sent to the topic.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5682) Can't define absolute path for object store location
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5682?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5682:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Can't define absolute path for object store location
> ----------------------------------------------------
>
> Key: WFLY-5682
> URL: https://issues.jboss.org/browse/WFLY-5682
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 10.0.0.CR4
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Fix For: 10.0.0.Final
>
>
> As trying to set absolute path for location of transaction log store I've got to suspicion that's not possible.
> If I try to set `object-store-relative-to` to some absolute path or set `object-store-relative-to` to empty string and then `object-store-path` to some absolute path the server starts with exceptions [1][2].
> [1]
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/home/ochaloup/tmp/'
> at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:87) at org.jboss.as.txn.service.ArjunaObjectStoreEnvironmentService.start(ArjunaObjectStoreEnvironmentService.java:76)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ...
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaObjectStoreEnvironment" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
> Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/home/ochaloup/tmp/'"}}
> INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status reportWFLYCTL0186: Services which failed to start: service jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
> {code}
> [2]
> {code}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:356) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[348,13]
> Message: "WFLYCTL0113: '' is an invalid value for parameter relative-to. Values must have a minimum length of 1 characters"
> at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:161) at org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:186)
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseObjectStoreEnvironmentElementAndEnrichOperation(TransactionSubsystem14Parser.java:205)
> at org.jboss.as.txn.subsystem.TransactionSubsystem30Parser.readElement(TransactionSubsystem30Parser.java:67) at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:111)
> at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:54) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:547)
> at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:244) at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:143)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:69) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:47) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5658) Improve the subsystem test schema test coverage
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5658?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5658:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Improve the subsystem test schema test coverage
> -----------------------------------------------
>
> Key: WFLY-5658
> URL: https://issues.jboss.org/browse/WFLY-5658
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.0.0.CR4
> Reporter: Kabir Khan
> Assignee: Kabir Khan
> Fix For: 10.0.0.Final
>
>
> Currently the way to enable the AbstractSubsystemBaseTest testSchema() and testSchemaOfSubsystemTemplates() tests is to override getSubsystemXsdPath() and getSubsystemTemplatePaths().
> Rather than making it explicit to turn on, it should be explicit to turn off.
> Also the current way of doing this uses Assume.assumeTrue() to check if a test has provided a schema file, which provides a lot of ignored test noise in the test output. If the xsd should not be tested, methods should instead override testSchema() or testSchemaOfSubsystemTemplates() and provide an empty implementation with a comment saying why it is not important.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5613) Fix transaction subsystem resource descriptions
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5613:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Fix transaction subsystem resource descriptions
> -----------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Fix For: 10.0.0.Final
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5858) Testsuite on windows sometimes fails with file locks on standalone-*.xml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5858?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5858:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Testsuite on windows sometimes fails with file locks on standalone-*.xml
> -------------------------------------------------------------------------
>
> Key: WFLY-5858
> URL: https://issues.jboss.org/browse/WFLY-5858
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.0.0.CR3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 10.0.0.Final
>
>
> ModelPersistenceTestCase.testSimpleOperation occasionally fails with the following pattern:
> {code}
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.test.integration.management.api.ModelPersistenceTestCase.testSimpleOperation(ModelPersistenceTestCase.java:119)
> ------- Stdout: -------
> 14:06:18,604 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0081: Failed to back up C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0081: Failed to back up C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone.xml
> at org.jboss.as.controller.persistence.ConfigurationFile.fileWritten(ConfigurationFile.java:552)
> at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:65)
> at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
> at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:780)
> at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:391)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:299)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:519)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.nio.file.FileSystemException: C:\BuildAgent\work\a31d203e70e89f90\testsuite\integration\basic\target\jbossas\standalone\configuration\standalone_xml_history\standalone.last.xml: The process cannot access the file because it is being used by another process.
> at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
> at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
> at sun.nio.fs.WindowsFileCopy.copy(WindowsFileCopy.java:165)
> at sun.nio.fs.WindowsFileSystemProvider.copy(WindowsFileSystemProvider.java:278)
> at java.nio.file.Files.copy(Files.java:1274)
> at org.jboss.as.controller.persistence.FilePersistenceUtils.copyFile(FilePersistenceUtils.java:73)
> at org.jboss.as.controller.persistence.ConfigurationFile.fileWritten(ConfigurationFile.java:550)
> ... 23 more
> {code}
> The test fails because the standalone.last.xml file isn't being updated as expected; the file isn't updated due to the "The process cannot access the file because it is being used by another process" IOException.
> 3 generally possibilities come to mind:
> 1) There's some other process on the CI server that really is using the file. Something like antivirus that touches lots of files briefly. (Not suggesting its actually AV.) It's odd we don't get other failures though; e.g. failures to persist the main config file.
> 2) It's the test driver process that's holding the file, conflicting with the server process. This is certainly possible. I've looked though and the test driver seems to be correct in terms of how it handles the file, reading it to calculate a CRC and then closing the stream used to do that in a finally block. It's also odd that this would only happen on Windows CI. Still, since we know we have 2 processes, test driver and server, both touching a file and we are getting an exception about 2 processes conflicting over that file, something in this area seems most likely.
> 3) There's some flaw in ConfigurationFile itself. But it's odd that a flaw there would produce an exception talking about how the file "is being used by another process".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5759) Local web-app.xsd can't be loaded to validate web.xml
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5759?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5759:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Local web-app.xsd can't be loaded to validate web.xml
> ------------------------------------------------------
>
> Key: WFLY-5759
> URL: https://issues.jboss.org/browse/WFLY-5759
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR4
> Reporter: Jim Ma
> Assignee: Jim Ma
> Fix For: 10.0.0.Final
>
>
> When "org.jboss.metadata.parser.validate" is enabled , WebParsingDeploymentProcessor retrieves web-app.xsd from remote to validate web.xml instead of load it from local.
> {code:java}
> 2015-11-24 04:13:12,404 WARN [org.jboss.metadata.parser.util.XMLResourceResolver] (MSC service thread 1-4) Cannot load publicId from resource: web-app_2_5.xsd
> 2015-11-24 04:13:12,406 WARN [org.jboss.metadata.parser.util.XMLResourceResolver] (MSC service thread 1-3) Cannot load publicId from resource: web-app_2_5.xsd
> 2015-11-24 04:13:13,106 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-3) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd: org.xml.sax.SAXParseException; systemId: http://java.sun.com/xml/ns/javaee/javaee_5.xsd; lineNumber: 83; columnNumber: 38; sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup'.
> at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:132) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4093) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4088) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(XSDHandler.java:3746) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(XSDHandler.java:1315) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:610) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:233) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_60]
> at _redirected.SchemaFactory.newSchema(_SchemaFactory.java:167) [jboss-modules.jar:1.4.4.Final]
> at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117)
> at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85)
> at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:104)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.2.Final.jar:2.0.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> 2015-11-24 04:13:13,115 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-3) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
> 2015-11-24 04:13:13,112 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-4) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd: org.xml.sax.SAXParseException; systemId: http://java.sun.com/xml/ns/javaee/javaee_5.xsd; lineNumber: 83; columnNumber: 38; sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup'.
> at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:132) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:394) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4093) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4088) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(XSDHandler.java:3746) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(XSDHandler.java:1315) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:610) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:233) [xercesImpl-2.11.0.SP4.jar:2.11.0.SP4]
> at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_60]
> at _redirected.SchemaFactory.newSchema(_SchemaFactory.java:167) [jboss-modules.jar:1.4.4.Final]
> at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117)
> at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85)
> at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:104)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.2.Final.jar:2.0.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> 2015-11-24 04:13:13,120 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-4) Cannot get schema for location: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-5716) Wrong handling of request context for remote EJB calls
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5716?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5716:
-------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR5)
> Wrong handling of request context for remote EJB calls
> ------------------------------------------------------
>
> Key: WFLY-5716
> URL: https://issues.jboss.org/browse/WFLY-5716
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, EJB
> Affects Versions: 9.0.0.Final, 10.0.0.CR4
> Reporter: Ste Gr
> Assignee: Martin Kouba
> Fix For: 10.0.0.Final
>
> Attachments: wfly5716.zip
>
>
> Two applications deployed to Wildfly. The first one provides a singleton remote ejb which uses request scoped beans (in this case a RESOURCE_LOCAL entity manager manged by a CDI producer/disposer, but +all+ request scoped beans are affected). The second application uses that EJB to get some data only accessible by the first application.
> A request is made to the second app from a browser. The app will get the remote EJB and invokes two methods on it. The first method produces the entity manager, accesses the database and returns the result. The entity manager will be disposed again. The second method won't produce a new entity manager but tries to re-use the one from the previous invokation. This fails as the entity manager was disposed.
> If the same use-case is made using the first app everythings works as desired. But it doesn't look right (or the request context is joined because it is the same application). It produces the the entity manager on the first invocation and closes it as soon as the whole request made from the browser is completed. Thats why the second invokation has a valid entity manager to work with.
> I don't know the spec but:
> - either the first EJB invokation from second app to first app is not allowed to dispose the request context (all the request scoped beans)
> - or each invokation must get its own request context (entity manager must be produced and disposed again).
> I've made a [stackoverflow thread|http://stackoverflow.com/q/33826720/1741604] which shows some code examples.
> (JBoss AS 7.1.3.Final is also affected but it is not available in 'affected version/s')
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (WFLY-1272) Infinite loop when starting my ear in JBoss 7.2.0 with autodeploy
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-1272?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet closed WFLY-1272.
-----------------------------------
Fix Version/s: 9.0.2.Final
Resolution: Out of Date
The issue was in the ear itself, it's working on WildFly now (at least for the next release) with some rework and configuration cleaning.
> Infinite loop when starting my ear in JBoss 7.2.0 with autodeploy
> -----------------------------------------------------------------
>
> Key: WFLY-1272
> URL: https://issues.jboss.org/browse/WFLY-1272
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
> Fix For: 9.0.2.Final
>
>
> Hi,
> I have a quite complexe application which I'm trying to port form JBoss 6.1.0 to JBoss 7.2.0.
> The ear is exploded as well as the war it contains. I have activated the auto-deploy-exploded on the deployment scanner.
> I have no error messages only warnings but the startup goes into an infinite loop trying to deploy my application again and again.
> If I set the auto-deploy-exploded to false then I can deploy correctly.
> Maybe it is because my application takes some time to launch (having to load a bunch of data into cache on startup).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months