[JBoss JIRA] (AS7-4950) CLONE - NotSerializableException: org.infinispan.loaders.bucket.Bucket on undeploying application
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-4950?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar moved JBPAPP-9248 to AS7-4950:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4950 (was: JBPAPP-9248)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0 ER 5)
(was: EAP 6.0.0 CR1)
Release Notes Docs Status: (was: Not Yet Documented)
Component/s: Clustering
(was: Clustering)
Security: (was: Public)
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - NotSerializableException: org.infinispan.loaders.bucket.Bucket on undeploying application
> -------------------------------------------------------------------------------------------------
>
> Key: AS7-4950
> URL: https://issues.jboss.org/browse/AS7-4950
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Labels: eap6_clustering, eap6_need_triage
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Just undeploying application from one node in the cluster. Application is still being accessed by remote ejb clients.
> {noformat}
> [JBossINF] 18:01:15,248 INFO [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011943: Unregister module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-ejb.jar:main" from Service Module Loader
> [JBossINF] 18:01:15,249 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011943: Unregister module: Module "deployment.clusterbench-ee6.ear:main" from Service Module Loader
> [JBossINF] 18:01:15,253 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-15) ISPN000029: Passivating all entries to disk
> [JBossINF] 18:01:15,249 INFO [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011943: Unregister module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-web.war:main" from Service Module Loader
> [JBossINF] 18:01:15,255 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-15) ISPN000030: Passivated 0 entries in 2 milliseconds
> [JBossINF] 18:01:15,269 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-9) ISPN000029: Passivating all entries to disk
> [JBossINF] 18:01:15,273 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-8) ISPN000029: Passivating all entries to disk
> [JBossINF] 18:01:15,270 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-15) JBAS010282: Stopped org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from ejb container
> [JBossINF] 18:01:15,275 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-8) ISPN000030: Passivated 0 entries in 1 milliseconds
> [JBossINF] 18:01:15,296 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-8) JBAS010282: Stopped //default-host//clusterbench cache from web container
> [JBossINF] 18:01:15,303 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016009: Stopping weld service for deployment clusterbench-ee6.ear
> [JBossINF] 18:01:15,311 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-2) ISPN000029: Passivating all entries to disk
> [JBossINF] 18:01:15,313 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-20-thread-2) ISPN000030: Passivated 0 entries in 1 milliseconds
> [JBossINF] 18:01:15,314 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-15-thread-2) ISPN000029: Passivating all entries to disk
> [JBossINF] 18:01:15,317 INFO [org.jboss.as.clustering.infinispan] (pool-20-thread-2) JBAS010282: Stopped repl cache from ejb container
> [JBossINF] 18:01:15,326 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015877: Stopped deployment clusterbench-ee6-ejb.jar in 82ms
> [JBossINF] 18:01:15,328 INFO [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015877: Stopped deployment clusterbench-ee6-web.war in 84ms
> [JBossINF] 18:01:15,328 INFO [org.jboss.as.clustering.infinispan] (pool-21-thread-2) JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
> [JBossINF] 18:01:15,330 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015877: Stopped deployment clusterbench-ee6.ear in 88ms
> [JBossINF] 18:01:15,352 INFO [org.infinispan.eviction.PassivationManagerImpl] (pool-15-thread-2) ISPN000030: Passivated 3 entries in 37 milliseconds
> [JBossINF] 18:01:15,354 INFO [org.jboss.as.clustering.infinispan] (pool-15-thread-2) JBAS010282: Stopped repl cache from web container
> [JBossINF] 18:01:15,476 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-14-thread-2) ISPN000082: Stopping the RpcDispatcher
> [JBossINF] 18:01:15,498 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-19-thread-2) ISPN000082: Stopping the RpcDispatcher
> [JBossINF] 18:01:15,523 WARN [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC000004: Failure during stop of service jboss.deployment.subunit."clusterbench-ee6.ear"."clusterbench-ee6-ejb.jar".component.RemoteStatefulSBImpl.START: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.eviction.PassivationManagerImpl.passivateAll() throws org.infinispan.loaders.CacheLoaderException on object of type PassivationManagerImpl
> [JBossINF] at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:238)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:882)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:672)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:551)
> [JBossINF] at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:198)
> [JBossINF] at org.infinispan.CacheImpl.stop(CacheImpl.java:516)
> [JBossINF] at org.infinispan.CacheImpl.stop(CacheImpl.java:508)
> [JBossINF] at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:291)
> [JBossINF] at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.stop(InfinispanBackingCacheEntryStore.java:107)
> [JBossINF] at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.stop(SerializationGroupMemberContainer.java:308)
> [JBossINF] at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.stop(PassivatingBackingCacheImpl.java:315)
> [JBossINF] at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.stop(AbstractCache.java:102)
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.stop(StatefulSessionComponent.java:306)
> [JBossINF] at org.jboss.as.ee.component.ComponentStartService.stop(ComponentStartService.java:49)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> [JBossINF] Caused by: org.infinispan.marshall.NotSerializableException: org.infinispan.loaders.bucket.Bucket
> [JBossINF] Caused by: an exception which occurred:
> [JBossINF] in object org.infinispan.loaders.bucket.Bucket@40a995c5
> [JBossINF]
> [JBossINF] 18:01:15,916 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "clusterbench-ee6.ear"
> {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
11 years, 10 months
[JBoss JIRA] (AS7-4949) NPE on :read-attribute in messaging subsystem
by Heiko Rupp (JIRA)
Heiko Rupp created AS7-4949:
-------------------------------
Summary: NPE on :read-attribute in messaging subsystem
Key: AS7-4949
URL: https://issues.jboss.org/browse/AS7-4949
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Heiko Rupp
Assignee: Andy Taylor
Not sure what the exact input from RHQ was, but the console showed this: -- and NPEs are always bad
[Server:server-two] 09:08:35,445 ERROR [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 4) JBAS014612: Operation ("read-attribute") fehlgeschlagen - Adresse: ([
[Server:server-two] ("subsystem" => "messaging"),
[Server:server-two] ("hornetq-server" => "default"),
[Server:server-two] ("core-address" => "jms.queue.testQueue")
[Server:server-two] ]): java.lang.NullPointerException
[Server:server-two] at org.jboss.as.messaging.AddressControlHandler.handleReadAttribute(AddressControlHandler.java:110)
[Server:server-two] at org.jboss.as.messaging.AddressControlHandler.executeRuntimeStep(AddressControlHandler.java:74)
[Server:server-two] at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
[Server:server-two] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
[Server:server-two] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
[Server:server-two] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
--
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
11 years, 10 months
[JBoss JIRA] (LOGTOOL-50) logging generation processing breaks Eclipse when a Logger uses JBoss Modules
by Fred Bricon (JIRA)
Fred Bricon created LOGTOOL-50:
----------------------------------
Summary: logging generation processing breaks Eclipse when a Logger uses JBoss Modules
Key: LOGTOOL-50
URL: https://issues.jboss.org/browse/LOGTOOL-50
Project: Log Tool
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.3.Final
Environment: JBDS 5.5.0.CR1
Reporter: Fred Bricon
Assignee: David Lloyd
Priority: Blocker
JBDS 5.5.0.CR1 embeds [m2e-apt|https://github.com/jbosstools/m2e-apt], which automatically enables Eclipse JDT Annotation Processor Toolkit.
When importing the [server|https://github.com/jbossas/jboss-as/tree/master/server] module from http://github.com/jbossas/jboss-as.git (also happens for other modules), Eclipse starts crashing with errors like :
{noformat}
javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:127)
at org.eclipse.jdt.apt.core.internal.util.FactoryPathUtil.decodeFactoryPath(FactoryPathUtil.java:222)
at org.eclipse.jdt.apt.core.internal.util.FactoryPathUtil.readFactoryPathFile(FactoryPathUtil.java:115)
at org.eclipse.jdt.apt.core.internal.util.FactoryPathUtil.calculatePath(FactoryPathUtil.java:342)
at org.eclipse.jdt.apt.core.internal.util.FactoryPathUtil.getFactoryPath(FactoryPathUtil.java:429)
at org.eclipse.jdt.apt.core.internal.AnnotationProcessorFactoryLoader.getJava6FactoriesAndAttributesForProject(AnnotationProcessorFactoryLoader.java:420)
at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:130)
at org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:813)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:432)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:364)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:178)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:301)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: __redirected/__DocumentBuilderFactory
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at javax.xml.parsers.FactoryFinder.getProviderClass(FactoryFinder.java:119)
at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:144)
at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185)
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:121)
{noformat}
It turns out the Eclipse System Properties have been changed to use javax.xml.parsers.SAXParserFactory=__redirected/__DocumentBuilderFactory
I tracked the code responsible with messing with the properties :
{noformat}
Thread [Worker-24] (Suspended (breakpoint at line 779 in System))
System.setProperty(String, String) line: 779
__SAXParserFactory.<clinit>() line: 68
__JAXPRedirected.initAll() line: 80
Module$1.run() line: 126
Module$1.run() line: 113
AccessController.doPrivileged(PrivilegedAction<T>) line: not available [native method]
Module.<clinit>() line: 113
Class<T>.forName0(String, boolean, ClassLoader) line: not available [native method]
Class<T>.forName(String) line: 186 <====== org.jboss.modules.Module
JCodeModel.ref(String) line: 363
MessageBundleImplementor(ImplementationClassModel).createBundleMethod(MessageMethod, JMethod, JMethod, JVar) line: 150
MessageBundleImplementor.generateModel() line: 86
MessageBundleImplementor(ClassModel).create(JavaFileObject) line: 104
ImplementationClassGenerator.processTypeElement(TypeElement, TypeElement, MessageInterface) line: 63
LoggingToolsProcessor.process(Set<TypeElement>, RoundEnvironment) line: 155
RoundDispatcher.handleProcessor(ProcessorInfo) line: 139
RoundDispatcher.round() line: 121
IdeAnnotationProcessorManager(BaseAnnotationProcessorManager).processAnnotations(CompilationUnitDeclaration[], ReferenceBinding[], boolean) line: 159
IdeAnnotationProcessorManager.processAnnotations(CompilationUnitDeclaration[], ReferenceBinding[], boolean) line: 134
Compiler.processAnnotations() line: 813
Compiler.compile(ICompilationUnit[]) line: 432
BatchImageBuilder(AbstractImageBuilder).compile(SourceFile[], SourceFile[], boolean) line: 364
BatchImageBuilder.compile(SourceFile[], SourceFile[], boolean) line: 178
BatchImageBuilder(AbstractImageBuilder).compile(SourceFile[]) line: 301
BatchImageBuilder.build() line: 60
JavaBuilder.buildAll() line: 254
JavaBuilder.build(int, Map, IProgressMonitor) line: 173
BuildManager$2.run() line: 728
SafeRunner.run(ISafeRunnable) line: 42
BuildManager.basicBuild(int, IncrementalProjectBuilder, Map<String,String>, MultiStatus, IProgressMonitor) line: 199
BuildManager.basicBuild(IBuildConfiguration, int, IBuildContext, ICommand[], MultiStatus, IProgressMonitor) line: 239
BuildManager$1.run() line: 292
SafeRunner.run(ISafeRunnable) line: 42
BuildManager.basicBuild(IBuildConfiguration, int, IBuildContext, MultiStatus, IProgressMonitor) line: 295
BuildManager.basicBuildLoop(IBuildConfiguration[], IBuildConfiguration[], int, MultiStatus, IProgressMonitor) line: 351
BuildManager.build(IBuildConfiguration[], IBuildConfiguration[], int, IProgressMonitor) line: 374
AutoBuildJob.doBuild(IProgressMonitor) line: 143
AutoBuildJob.run(IProgressMonitor) line: 241
Worker.run() line: 54
{noformat}
That stacktrace represents the processing of https://github.com/jbossas/jboss-as/blob/master/server/src/main/java/org/...
So basically, whenever a Logger has a dependency to the [org.jboss.modules.Module|https://github.com/jbossas/jboss-modules/blob/ma...] class, stuff starts hitting the fan.
Ideally we should process the classes in an isolated way, so that doesn't break IDE embdeding.
Currently, JBoss AS source code can only be used in JBDS if m2e-apt is disabled (Preferences > Maven > Annotation Processing).
--
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
11 years, 10 months
[JBoss JIRA] (AS7-4948) Error: Missing configuration value for: jboss.home.dir when starting standalone server using module path in windows
by Peter Cadman (JIRA)
Peter Cadman created AS7-4948:
---------------------------------
Summary: Error: Missing configuration value for: jboss.home.dir when starting standalone server using module path in windows
Key: AS7-4948
URL: https://issues.jboss.org/browse/AS7-4948
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.1.Final
Environment: Windows 7
jdk1.6.0_30
Reporter: Peter Cadman
Assignee: Alexey Loubyansky
When running
java -jar jboss-modules.jar -mp "%JBOSS_HOME%\modules" org.jboss.as.standalone
The exception
java.lang.IllegalStateException: JBAS015816: Missing configuration value for: jboss.home.dir
at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:325)
at org.jboss.as.server.Main.determineEnvironment(Main.java:242)
at org.jboss.as.server.Main.main(Main.java:83)
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:597)
at org.jboss.modules.Module.run(Module.java:260)
at org.jboss.modules.Main.main(Main.java:291
--
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
11 years, 10 months
[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
11 years, 10 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
11 years, 10 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
11 years, 10 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
11 years, 10 months