[JBoss JIRA] (AS7-5537) Reopened - Remote store config errors in AS7
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5537:
-------------------------------------
Summary: Reopened - Remote store config errors in AS7
Key: AS7-5537
URL: https://issues.jboss.org/browse/AS7-5537
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.1.Final
Environment: Windows
Reporter: rang s
Assignee: Radoslav Husar
Priority: Critical
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
When remote-store is configured in domain.xml, on server startup following errors :-
[Server:server-one] 17:00:00,889 ERROR [org.jboss.msc.service.fail] (pool-13-thread-1) MSC00001: Failed to start service jboss.infinispan.web.repl: org.jboss.msc.servic
e.StartException in service jboss.infinispan.web.repl: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl.
start() on object
[Server:server-one] at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:62) [jboss-as-clustering-common-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] Caused by: org.infinispan.CacheConfigurationException: Unable to instantiate class org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFacto
ry
[Server:server-one] Caused by: java.lang.ClassNotFoundException: org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory
Looks like some issue in locating the jar which contains this class file. I could resolve this issue by :-
Adding the following :-
<module name="org.infinispan.client.hotrod"/>
in %JBOSS_HOME%/modules/org/infinispan/main/module.xml
This seems to be a bug as it should work out of the box.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5360) CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5360?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-5360:
---------------------------------------
The fix for this seems pretty simple (detect the <any-ipv6-address> + -Djava.net.preferIPv4Stack=true combination and fail fast.)
> CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5360
> URL: https://issues.jboss.org/browse/AS7-5360
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Pavel Janousek
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
> {code}
> <server xmlns="urn:jboss:domain:1.3">
> {code}
> The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
> The very common Linux system has implemented and enabled dualstack in these days. If we instruct EAP instance to bind to +any+ IPv6 address via {code}<interface name="public">
> <any-ipv6-address />
> </interface>{code}
> The real result is mess messages to output log:{code}
> 08:17:55,779 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Error initializing endpoint: java.net.SocketException: Protocol family unavailable
> at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_30]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_30]
> at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_30]
> at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:56) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:978) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> 08:17:55,828 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: LifecycleException: Protocol handler initialization failed: java.net.SocketException: Protocol family unavailable
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> 08:17:55,999 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
> 08:17:56,294 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.3.GA-redhat-1
> 08:17:56,294 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 08:17:56,904 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/users-tmp/pjanouse/jboss-eap-6.0/standalone/deployments
> 08:17:56,918 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
> 08:17:56,953 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:111)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: java.net.SocketException: Protocol family unavailable
> at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_30]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_30]
> at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
> at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
> at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
> ... 5 more
> 08:17:57,611 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
> service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> {code}
> The valid result message could be only - there isn't available any IPv6 address when IPv6 is disabled. Or there isn't a such IP address.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5359) CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5359?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-5359:
---------------------------------------
AFAICT in the absence of -Djava.net.preferIPv4Stack=true there is no way to tell the VM to bind a socket to all IPv4 addresses, but only to IPv4 addresses.
So, all we can is check when we see this <any-ipv4-address/> and fail if we don't see -Djava.net.preferIPv4Stack=true.
But, testing on Windows shows that this problem doesn't exist there, which makes my proposed fix problematic; i.e. rejecting <any-ipv4-address/> without a corresponding -Djava.net.preferIPv4Stack=true would break things on Windows.
The <any-ipv4-address/> and <any-ipv6-address/> config elements basically don't have any value, since in the end the behavior we'll support will be what <any-address/> plus the -Djava.net.preferIPv4Stack specifies. So those elements will likely be removed in AS 8.
> CLONE - Config XML with <interface ...><any-ipv4-address /></interface> + -Djava.net.preferIPv4Stack=false produces binding to ANY address (error)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5359
> URL: https://issues.jboss.org/browse/AS7-5359
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Pavel Janousek
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:
> {code}
> <server xmlns="urn:jboss:domain:1.3">
> {code}
> The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.
> The very common Linux system has implemented and enabled dualstack in these days. If we instruct AS instance to bind to +any+ IPv4 address via {code}<interface name="public">
> <any-ipv4-address />
> </interface>{code}
> The real result is to bind running AS instance to +any+ IP address, not only in IPv4 address space but in IPv6 too!
> With default setting (= -Djava.net.preferIPv4Stack=true), result is correct - it is bound to ANY IPv4 addresses only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5535) Cannot register a host with a - in the name with the domain controller.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5535?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-5535:
----------------------------------
Summary: Cannot register a host with a - in the name with the domain controller. (was: CLONE - Register a host with a - in the name with the domain controller.)
Description: If hosts are configured with "-" in their name they cannot join the domain. (was: This is a request from the Cloud Forms team. As they are spinning up new machine, they can produce names with this character.)
Priority: Critical (was: Minor)
Assignee: Emanuel Muckenhuber
Component/s: Domain Management
> Cannot register a host with a - in the name with the domain controller.
> -----------------------------------------------------------------------
>
> Key: AS7-5535
> URL: https://issues.jboss.org/browse/AS7-5535
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Environment: Cloud Forms deployment of EAP.
> Reporter: John Doyle
> Assignee: Emanuel Muckenhuber
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> If hosts are configured with "-" in their name they cannot join the domain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5535) CLONE - Register a host with a - in the name with the domain controller.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-5535?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry moved JBPAPP-9888 to AS7-5535:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5535 (was: JBPAPP-9888)
Issue Type: Bug (was: Feature Request)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: EAP 6.0.0)
Security: (was: JBoss Internal)
Fix Version/s: 7.2.0.CR1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - Register a host with a - in the name with the domain controller.
> ------------------------------------------------------------------------
>
> Key: AS7-5535
> URL: https://issues.jboss.org/browse/AS7-5535
> Project: Application Server 7
> Issue Type: Bug
> Environment: Cloud Forms deployment of EAP.
> Reporter: John Doyle
> Priority: Minor
> Fix For: 7.2.0.CR1
>
>
> This is a request from the Cloud Forms team. As they are spinning up new machine, they can produce names with this character.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5528) Naming context read-only during ResourceAdapter#start()
by Philippe Marschall (JIRA)
Philippe Marschall created AS7-5528:
---------------------------------------
Summary: Naming context read-only during ResourceAdapter#start()
Key: AS7-5528
URL: https://issues.jboss.org/browse/AS7-5528
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.1.Final
Reporter: Philippe Marschall
Assignee: Jesper Pedersen
When the {{ResourceAdapter#start(BoostrapContext)}} method is invoked on an annotation based 1.6 JCR resource adapter the naming context is read only. Binding values results in the following exception:
{code}
20:56:07,321 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.ra.deployer."sample-rar-1.0.0-SNAPSHOT": org.jboss.msc.service.StartException in service jboss.ra.deployer."sample-rar-1.0.0-SNAPSHOT": JBAS010446: Failed to start RA deployment [sample-rar-1.0.0-SNAPSHOT]
at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:105)
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_07]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start com.github.marschall.kotlin.rar.implementation.SampleAdapter
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:354)
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2187)
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1046)
at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService$AS7RaDeployer.doDeploy(ResourceAdapterDeploymentService.java:186)
at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:102)
... 5 more
Caused by: java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:98)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:85)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:244)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:195)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:252)
{code}
The problem seems to be while {{org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(StartContext)}} does {{WritableServiceBasedNamingStore.pushOwner()}} to make the naming context writable {{org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(StartContext)}} does not do it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (JGRP-1455) Message lost in NAKACK due to digest error
by David Hotham (JIRA)
David Hotham created JGRP-1455:
----------------------------------
Summary: Message lost in NAKACK due to digest error
Key: JGRP-1455
URL: https://issues.jboss.org/browse/JGRP-1455
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.9
Reporter: David Hotham
Assignee: Bela Ban
Hello,
In this issue an application-level message broadcast to the cluster is being discarded by NAKACK2, on a new joiner.
I think I understand roughly what's going on - skip to the end for a suggested fix!
I'll keep all my trace so that I can investigate further details if needed.
So, let's start with trace from the new joiner (CFS-B-chucklebrothers), showing that:
- it sets a digest claiming that the sequence numbers for CFS-A-tinkywinky are 26 (26)
- CFS-A-tinkywinky then sends messages with sequence numbers 26 and 27
- Only message 27 is passed upwards
{noformat}
2012-04-18 19:26:49.133 [ForkJoinPool-1-worker-3] DEBUG org.jgroups.protocols.pbcast.NAKACK2 -
[CFS-B-chucklebrothers setDigest()]
existing digest: []
new digest: CFS-A-tinkywinky: [26 (26)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)]
resulting digest: CFS-A-tinkywinky: [26 (26)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)]
2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.TCP - received [dst: <null>, src: CFS-A-tinkywinky (3 headers), size=39 bytes], headers are SEQUENCER: WRAPPED_BCAST (tag=[CFS-B-chucklebrothers|0]), NAKACK2: [MSG, seqno=26], TCP: [channel_name=Clumpy Test Cluster]
2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.TCP - received [dst: <null>, src: CFS-A-tinkywinky (3 headers), size=51 bytes], headers are SEQUENCER: BCAST (tag=[CFS-A-tinkywinky|11]), NAKACK2: [MSG, seqno=27], TCP: [channel_name=Clumpy Test Cluster]
2012-04-18 19:26:49.200 [Incoming-2,Clumpy Test Cluster,CFS-B-chucklebrothers] TRACE org.jgroups.protocols.pbcast.NAKACK2 - CFS-B-chucklebrothers: received CFS-A-tinkywinky#27
{noformat}
And here's the trace from CFS-A-tinkywinky showing that:
- the digest that it sent only claimed sequence numbers 25 (25)
{noformat}
2012-04-18 19:26:49.132 [OOB-1,Clumpy Test Cluster,CFS-A-tinkywinky] TRACE org.jgroups.protocols.TCP - sending msg to CFS-B-chucklebrothers, src=CFS-A-tinkywinky, headers are GMS: GmsHeader[JOIN_RSP]: join_rsp=view: [CFS-A-tinkywinky|3] [CFS-A-tinkywinky, CFS-A-chucklebrothers, CFS-B-tinkywinky, CFS-B-chucklebrothers], digest: CFS-A-tinkywinky: [25 (25)], CFS-A-chucklebrothers: [0 (0)], CFS-B-tinkywinky: [0 (0)], CFS-B-chucklebrothers: [0 (0)], UNICAST2: DATA, seqno=2, conn_id=3, TCP: [channel_name=Clumpy Test Cluster]
{noformat}
By looking at trace from the other members receiving message 26, I can see that this is an application level message.
I think that the incrementing of the received sequence number is deliberate, per ClientGmsImpl ("see doc/design/varia2.txt for details"). If I understand correctly, it's intended to compensate for the fact that the the digest doesn't include the broadcast VIEW message.
However, CFS-A-tinkywinky shows this:
{noformat}
2012-04-18 19:26:49.125 [ViewHandler,Clumpy Test Cluster,CFS-A-tinkywinky] WARN org.jgroups.protocols.pbcast.GMS - CFS-B-chucklebrothers already present; returning existing view [CFS-A-tinkywinky|3] [CFS-A-tinkywinky, CFS-A-chucklebrothers, CFS-B-tinkywinky, CFS-B-chucklebrothers]
2012-04-18 19:26:49.126 [ViewHandler,Clumpy Test Cluster,CFS-A-tinkywinky] TRACE org.jgroups.protocols.pbcast.GMS - found no members to add or remove, will not create new view
{noformat}
My thinking is that since the coordinator does not broadcast a VIEW message, it's a mistake for CFS-B-chucklebrothers to have fixed up the digest.
Possibly the fix is simply to remove the block of code in CoordGmsImpl.handleMembershipChange() for "found no members to add or remove", and send out a view anyway?
Thanks!
David
--
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, 8 months
[JBoss JIRA] (AS7-2322) Stack trace improvements, summarize the things that broke to make them not so intimidating
by Jim Tyrrell (Created) (JIRA)
Stack trace improvements, summarize the things that broke to make them not so intimidating
------------------------------------------------------------------------------------------
Key: AS7-2322
URL: https://issues.jboss.org/browse/AS7-2322
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jim Tyrrell
See the typical attached stack dump:
It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump:
11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}}
11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report
Services which failed to start:
service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context
11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms
11:51:45,417 Error Summary of Exceptions in deployment:
- [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
- [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
- [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
- ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
- [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
- [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
ERROR Scroll up to see more info...
Or
11:51:45,417 Error Summary of Exceptions in deployment:
[1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
[2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
[3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
[4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
[5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
[6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
ERROR Scroll up to see more info...
--
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, 8 months
[JBoss JIRA] (JGRP-1510) SimpleChat runing in two linux machine not commnicating
by Balamurali L (JIRA)
Balamurali L created JGRP-1510:
----------------------------------
Summary: SimpleChat runing in two linux machine not commnicating
Key: JGRP-1510
URL: https://issues.jboss.org/browse/JGRP-1510
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.14
Environment: Between linux machines
Reporter: Balamurali L
Assignee: Bela Ban
Priority: Blocker
SimpleChat running in two linux machines , but not communication (Joining).Warning sender not in table (localhost-41559) in console.I disabled Firewall.What configuration need to do ? Shall i do any configuration in linux side ? Pls help .Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months