[JBoss JIRA] (AS7-4947) write-remote-domain-controller operation fails
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4947:
-------------------------------------
Summary: write-remote-domain-controller operation fails
Key: AS7-4947
URL: https://issues.jboss.org/browse/AS7-4947
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
The operation to update the configuration a HostController uses for connecting to the master fails:
[Host Controller] 20:47:17,985 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) JBAS014612: Operation ("write-remote-domain-controller") failed - address: ([("host" => "besdev")]): java.lang.IllegalStateException: JBAS010949: Configuration persister for domain model is already initialized
[Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.initializeDomainConfigurationPersister(HostControllerConfigurationPersister.java:72) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.host.controller.operations.RemoteDomainControllerAddHandler.initializeDomain(RemoteDomainControllerAddHandler.java:134) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.host.controller.operations.RemoteDomainControllerAddHandler.execute(RemoteDomainControllerAddHandler.java:120) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.execute(DomainFinalResultHandler.java:75) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:225) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:118) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:85) [jboss-as-host-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:286) [jboss-as-protocol-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:491) [jboss-as-protocol-7.1.2.Final.jar:7.1.2.Final]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
[Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
[Host Controller] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
[Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
[Host Controller]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4022) Add support for indexing properties to infinispan subsystem schema
by Paul Ferraro (JIRA)
Paul Ferraro created AS7-4022:
---------------------------------
Summary: Add support for indexing properties to infinispan subsystem schema
Key: AS7-4022
URL: https://issues.jboss.org/browse/AS7-4022
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.1.1.Final
As requested by CapeDwarf team:
e.g.
<distributed-cache name="default" mode="ASYNC" batching="true" indexing="LOCAL" owners="2">
<transaction mode="NON_XA"/>
<eviction strategy="NONE"/>
<indexing>
<property name="hibernate.search.default.directory_provider">infinispan</property>
<property name="hibernate.search.default.worker.backend">jgroupsMaster</property>
</properties>
</indexing>
</distributed-cache>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4946) ManagedDeployableContainer.ConsoleConsumer should not change the console output
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-4946:
-------------------------------------
Summary: ManagedDeployableContainer.ConsoleConsumer should not change the console output
Key: AS7-4946
URL: https://issues.jboss.org/browse/AS7-4946
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.2.Final (EAP)
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 7.1.3.Final (EAP)
Executing the following code in a standalone J2SE app:
{code}val out = new PrintStream(new BufferedOutputStream(new FileOutputStream(FileDescriptor.out), 128), true, "UTF-8")
out.print("hello\rgoodbye"){code}
Will print:
{code}goodbye{code}
However, when running an Arquillian test with AS, if the code within AS writes that, it will print:
{code}hello
goodbye{code}
The culprit is org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.ConsoleConsumer whose consuming the process output and it's using readLine, which is translating \r to \n, when it really shouldn't be any transformation of the output.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (AS7-947) server:reload() exception
by Heiko Braun (JIRA)
server:reload() exception
-------------------------
Key: AS7-947
URL: https://issues.jboss.org/browse/AS7-947
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.CR1
Reloading yields an exception:
/host=local/server=server-one:reload
{noformat}
[Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)'
[Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
{noformat}
A second operation request results in "broken pipe":
{noformat}
[Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4763) Wrong PropertyEditor is used by ThreadGroups other than "ModelController ThreadGroup" in JDK 7
by Carlo de Wolf (JIRA)
Carlo de Wolf created AS7-4763:
----------------------------------
Summary: Wrong PropertyEditor is used by ThreadGroups other than "ModelController ThreadGroup" in JDK 7
Key: AS7-4763
URL: https://issues.jboss.org/browse/AS7-4763
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.2.Final (EAP)
Environment: java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b20)
Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
Reporter: Carlo de Wolf
{noformat}
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
{noformat}
gives:
{noformat}
14:15:37,247 ERROR [stderr] (EJB default - 1) java.lang.ThreadGroup[name=EJB default,maxpri=10]
14:15:37,249 ERROR [stderr] (EJB default - 1) org.jboss.common.beans.property.LongEditor@610a9daf
{noformat}
JDK 7 however gives:
{noformat}
14:13:19,077 ERROR [stderr] (EJB default - 1) java.lang.ThreadGroup[name=EJB default,maxpri=10]
14:13:19,079 ERROR [stderr] (EJB default - 1) sun.beans.editors.LongEditor@2ef2f659
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-3615) CLI: xa-data-source add command does not allow to specify xa-datasource-properties
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3615:
-------------------------------------
Summary: CLI: xa-data-source add command does not allow to specify xa-datasource-properties
Key: AS7-3615
URL: https://issues.jboss.org/browse/AS7-3615
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
It seems that CLI xa-data-source add command does not allow to specify xa-datasource-properties. As having non empty xa-tadasource-properties map is mandatory, enabling such datasource fails:
[standalone@localhost:9999 xa-datasource-properties] xa-data-source add --name=TestXADS --jndi-name=java:jboss/datasources/TestXADS --driver-name=h2
[standalone@localhost:9999 xa-datasource-properties] xa-data-source enable --name=TestXADS
JBAS014750: Operation handler failed to complete
Server exception:
15:54:56,948 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.data-source.java:jboss/datasources/TestXADS: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/TestXADS: JBAS010433: Error during the deployment of TestXADS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:118)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea]
Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.XADataSourceImpl
at org.jboss.jca.common.metadata.ds.XADataSourceImpl.validate(XADataSourceImpl.java:384)
at org.jboss.jca.common.metadata.ds.XADataSourceImpl.<init>(XADataSourceImpl.java:115)
at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:372)
at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:66)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:111)
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-4943) removing security-realm attribute in jboss-ejb-client.xml causes failures
by jkreska (JIRA)
jkreska created AS7-4943:
----------------------------
Summary: removing security-realm attribute in jboss-ejb-client.xml causes failures
Key: AS7-4943
URL: https://issues.jboss.org/browse/AS7-4943
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.2.Final (EAP)
Environment: Linux
Reporter: jkreska
Assignee: jaikiran pai
The following exception occurs when the security-realm attribute is removed
15:14:17,273 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."xxi-framework-test-modul
e-deploy-ejb.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xxi-framework-test-module-deploy-ejb.ear".POST_MODUL
E: JBAS018733: Failed to process phase POST_MODULE of deployment "xxi-framework-test-module-deploy-ejb.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.2.Final.jar:7.1.2.Fin
al]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
Caused by: java.lang.IllegalArgumentException: Name segment is null for security_realm
at org.jboss.msc.service.ServiceName.of(ServiceName.java:82) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.as.ejb3.remote.EJBClientCommonConnectionConfig$CallbackHandlerProvider.<init>(EJBClientCommonConnectionConfig.java:114)
at org.jboss.as.ejb3.remote.EJBClientCommonConnectionConfig.setCallbackHandler(EJBClientCommonConnectionConfig.java:86)
at org.jboss.as.ejb3.remote.EJBClientClusterConfig.<init>(EJBClientClusterConfig.java:72)
at org.jboss.as.ejb3.deployment.processors.EJBClientDescriptorMetaDataProcessor.createClientConfiguration(EJBClientDescriptorMetaDataProcessor.jav
a:158)
at org.jboss.as.ejb3.deployment.processors.EJBClientDescriptorMetaDataProcessor.deploy(EJBClientDescriptorMetaDataProcessor.java:89)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.2.Final.jar:7.1.2.Fin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (JBRULES-3512) Move ProblemIO into core Planner API
by Lukáš Petrovický (JIRA)
Lukáš Petrovický created JBRULES-3512:
-----------------------------------------
Summary: Move ProblemIO into core Planner API
Key: JBRULES-3512
URL: https://issues.jboss.org/browse/JBRULES-3512
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: Lukáš Petrovický
Assignee: Geoffrey De Smet
After the benchmark has been split into its own Maven module, I need to import both -core and -benchmark into my projects when I'm using ProblemIO interface.
Since I'm using it not only inside a benchmark but also for general reading/writing of solutions (in order to be able to share the code between my planner and my benchmarks), I would appreciate if this useful interface could be part of the core API.
(Because one day I would like to distribute my planner app without the unnecessary benchmark dependencies, while still keeping the classes implementing the ProblemIO interface.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months