[JBoss JIRA] Moved: (AS7-1816) CLONE - DC down, domain.sh with --cached-dc option doesn't start on slave node
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/AS7-1816?page=com.atlassian.jira.plugin.s... ]
Rostislav Svoboda moved JBPAPP-7191 to AS7-1816:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-1816 (was: JBPAPP-7191)
Issue Type: Feature Request (was: Bug)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.0.1.Final
(was: EAP 6.0.0 DR3)
Component/s: Scripts
(was: Scripts and Commands)
Security: (was: Public)
Fix Version/s: 7.1.0.Alpha1
(was: EAP 6.0.0)
Docs QE Status: (was: NEW)
> CLONE - DC down, domain.sh with --cached-dc option doesn't start on slave node
> ------------------------------------------------------------------------------
>
> Key: AS7-1816
> URL: https://issues.jboss.org/browse/AS7-1816
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Scripts
> Affects Versions: 7.0.1.Final
> Reporter: Rostislav Svoboda
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 7.1.0.Alpha1
>
>
> I have local copy of the domain configuration (using -backup), file domain.cached-remote.xml exists.
> Can't start domain.sh (with --cached-dc) when DC is down, script ends with could not connect to remote server error.
> *Details:*
> (Master instance = MI, slave instance = SI, both on the same machine, EAP6 instances copied into different directories)
> MI> just start bin/domain.sh
> SI: remove all domain/configuration/domain* (optional)
> SI: change name attribute of host element in domain/configuration/host.xml
> SI: change interfaces definition to public IP address in domain/configuration/host.xml
> SI: change domain-controller definition to use remote domain controller (127.0.0.1 in my case) in domain/configuration/host.xml
> SI: run bin/domain.sh --backup
> MI> shutdown EAP6 instance
> SI: shutdown EAP6 instance
> SI: make sure file domain/configuration/domain.cached-remote.xml
> SI: run bin/domain.sh --cached-dc
> SI: there is error, DC couldn't be contacted
> log:
> {code}
> [Host Controller] 09:01:06,861 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
> [Host Controller] 09:01:11,980 WARN [org.jboss.as.domain.controller] (Controller Boot Thread) Could not connect to remote domain controller 127.0.0.1:9999
> [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) Exception in thread "Controller Boot Thread" java.lang.IllegalStateException: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms
> [Host Controller] 09:01:12,083 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:238)
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.register(RemoteDomainConnectionService.java:159)
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:291)
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83)
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:662)
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) Caused by: java.net.ConnectException: Could not connect to remote server at 5000 within 5000ms
> [Host Controller] 09:01:12,084 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:144)
> [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.host.controller.RemoteDomainConnectionService.connect(RemoteDomainConnectionService.java:221)
> [Host Controller] 09:01:12,085 ERROR [stderr] (Controller Boot Thread) ... 4 more
> {code}
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1810) CLONE - ClassNotFoundException: org.jgroups.util.UUID when sessions are quickly created
by Radoslav Husar (JIRA)
CLONE - ClassNotFoundException: org.jgroups.util.UUID when sessions are quickly created
---------------------------------------------------------------------------------------
Key: AS7-1810
URL: https://issues.jboss.org/browse/AS7-1810
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.0.1.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.0.2.Final, 7.1.0.Alpha1
Just randomly thrown out when creating about 30 sessions very quickly one after another.
{code}
14:43:48,602 INFO [org.jboss.test.cluster.servlet.SessionTestServlet] (http-rhusar-10.34.3.13-8080-1) Setting up new session - x-+65n79GohuOuJAUsqtFdsE.5395c435-05f4-38a6-832f-3999740381a2.5395c435-05f4-38a6-832f-3999740381a2
14:43:48,621 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-13,web,rhusar-26008) Problems unmarshalling remote command from byte buffer: java.lang.ClassNotFoundException: org.jgroups.util.UUID from [Module "org.jboss.as.clustering.web.infinispan:main" from local module loader @42a9c09e (roots: /home/rhusar/Download/jboss-eap-6.0.0.Alpha1-rhusar/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
at java.lang.Class.forName0(Native Method) [:1.6.0_26]
at java.lang.Class.forName(Class.java:247) [:1.6.0_26]
at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:135) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:116) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:930)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1200)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.infinispan.remoting.transport.jgroups.JGroupsAddress$Externalizer.readObject(JGroupsAddress.java:90) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.remoting.transport.jgroups.JGroupsAddress$Externalizer.readObject(JGroupsAddress.java:81) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:356) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:244) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.infinispan.transaction.xa.GlobalTransaction$AbstractGlobalTxExternalizer.readObject(GlobalTransaction.java:150) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.transaction.xa.GlobalTransaction$Externalizer.readObject(GlobalTransaction.java:155) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.transaction.xa.GlobalTransaction$AbstractGlobalTxExternalizer.readObject(GlobalTransaction.java:133) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:356) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:244) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:116) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:71) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:356) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:244) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:116) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.exts.ReplicableCommandExternalizer.readObject(ReplicableCommandExternalizer.java:71) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:356) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:244) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.0.GA.jar:1.3.0.GA]
at org.infinispan.marshall.jboss.GenericJBossMarshaller.objectFromObjectStream(GenericJBossMarshaller.java:194) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.marshall.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:122) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromByteBuffer(MarshallerAdapter.java:48) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:142) [infinispan-core-5.0.0.FINAL.jar:5.0.0.FINAL]
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:577)
at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:488)
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:364)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:770)
at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:135)
at org.jgroups.JChannel.up(JChannel.java:1484)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1074)
at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:477)
at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:263)
at org.jgroups.protocols.FRAG2.unfragment(FRAG2.java:310)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:170)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:400)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:908)
at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:170)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:246)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:309)
at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:838)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:667)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:123)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:133)
at org.jgroups.protocols.FD.up(FD.java:275)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:275)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
at org.jgroups.protocols.Discovery.up(Discovery.java:293)
at org.jgroups.protocols.PING.up(PING.java:69)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1109)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1665)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1647)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (AS7-1685) Management layer doesn't reflect true handler attributes
by Stan Silvert (JIRA)
Management layer doesn't reflect true handler attributes
--------------------------------------------------------
Key: AS7-1685
URL: https://issues.jboss.org/browse/AS7-1685
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.0.1.Final
Reporter: Stan Silvert
Assignee: James Perkins
In the logging subsystem, the management operations are defined in LoggingSubsystemProviders.java.
The attributes defined for each handler type don't always reflect the real attributes that are available.
For example, if I go into the CLI and ask to read the resource description for an async handler, I get:
[standalone@localhost:9999 async-handler=ASYNC] :read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Defines a handler which writes to the sub-handlers in an asynchronous thread. Used for handlers which introduce a substantial amount of lag.",
"attributes" => {
"name" => {
"type" => STRING,
"description" => "The handler's name.",
"access-type" => "read-only",
"storage" => "configuration"
},
"level" => {
"type" => STRING,
"description" => "The log level specifying which message levels will be logged by this. Message levels lower than this value will be discarded.",
"access-type" => "read-only",
"storage" => "configuration"
},
"encoding" => {
"type" => STRING,
"description" => "The character encoding used by this Handler.",
"access-type" => "read-only",
"storage" => "configuration"
},
"filter" => {
"type" => STRING,
"description" => "Defines a simple filter type.",
"access-type" => "read-only",
"storage" => "configuration"
},
"formatter" => {
"type" => STRING,
"description" => "Defines a formatter.",
"access-type" => "read-only",
"storage" => "configuration"
},
"autoflush" => {
"type" => BOOLEAN,
"description" => "Automatically flush after each write.",
"access-type" => "read-only",
"storage" => "configuration"
},
"handler" => {
"type" => LIST,
"value-type" => STRING,
"description" => "The Handlers associated with this Logger.",
"access-type" => "read-only",
"storage" => "configuration"
},
"queue-length" => {
"type" => STRING,
"description" => "The queue length to use before flushing writing",
"access-type" => "read-only",
"storage" => "configuration"
},
"overflow-action" => {
"type" => STRING,
"description" => "Specify what action to take when the overflowing. The valid options are 'block' and 'discard'",
"access-type" => "read-only",
"storage" => "configuration"
}
}
}
}
Clearly, an async handler doesn't accept all of those attributes. If I add the autoflush attribute to my standalone.xml then I will get an error on startup.
<async-handler name="ASYNC" autoflush="true">
<level name="INFO"/>
<queue-length value="512"/>
<overflow-action value="BLOCK"/>
</async-handler>
Furthermore, there is a discrepancy in which attributes are required. Looking at autoflush again, LoggingSubsystemProviders.java says that this attribute is not required. But if I try to create a console handler without this attribute I will get an exception.
[standalone@localhost:9999 console-handler=MYCONSOLE] :add(name=MYCONSOLE,level=INFO)
{
"outcome" => "failed",
"failure-description" => "Operation handler failed: java.lang.IllegalArgumentException",
"rolled-back" => true
}
[standalone@localhost:9999 console-handler=MYCONSOLE] :add(name=MYCONSOLE,level=INFO,autoflush=true)
{"outcome" => "success"}
So each attribute needs to be checked to see if it is really required or not. Once this is fixed in LoggingSubsystemProviders.java I can go in and fix this in the console.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months