[JBoss JIRA] (WFCORE-58) Setting some locales causes missing buttons on console and throws errors.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-58?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-58:
-----------------------------------------------
Jay SenSharma <jsenshar(a)redhat.com> changed the Status of [bug 1141668|https://bugzilla.redhat.com/show_bug.cgi?id=1141668] from NEW to POST
> Setting some locales causes missing buttons on console and throws errors.
> -------------------------------------------------------------------------
>
> Key: WFCORE-58
> URL: https://issues.jboss.org/browse/WFCORE-58
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha4
> Reporter: Jay Kumar SenSharma
> Assignee: Tomaz Cerar
> Fix For: 1.0.0.Alpha5
>
> Attachments: mssing_add_remove_disable_Buttons.png
>
>
> - When WildFly 9 Alpha1 is started with the following system properties in the "standalone.conf" then the admin console behaves abnormally and shows some missing buttons in the console. See attached screenshot "mssing_add_remove_disable_Buttons.png".
> {code}
> JAVA_OPTS="$JAVA_OPTS -Duser.country=TR -Duser.language=tr"
> {code}
> - Also it throws following Error while accessing the console URL like [1]
> [1] http://localhost:9990/console/App.html#datasources
> {code}
> 10:39:39,223 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-8) WFLYCTL0013: Operation ("check-resource-access") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "*"),
> ("connection-properties" => "*")
> ]): java.lang.IllegalArgumentException: No enum constant org.jboss.as.controller.registry.AttributeAccess.Storage.CONFİGURATİON
> at java.lang.Enum.valueOf(Enum.java:236) [rt.jar:1.7.0_51]
> at org.jboss.as.controller.registry.AttributeAccess$Storage.valueOf(AttributeAccess.java:91) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$CheckResourceAccessHandler.execute(ReadResourceDescriptionHandler.java:431) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:603) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:481) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1060) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:296) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:165) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:179) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
> at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_51]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:83) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFCORE-92) cli deploy command with unpaired quotation mark causes StringIndexOutOfBoundsException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-92?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-92:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1139515|https://bugzilla.redhat.com/show_bug.cgi?id=1139515] from POST to MODIFIED
> cli deploy command with unpaired quotation mark causes StringIndexOutOfBoundsException
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-92
> URL: https://issues.jboss.org/browse/WFCORE-92
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 1.0.0.Alpha5, 1.0.0.Alpha6
> Environment: * Windows Operating System is Must *
> Reporter: Jay Kumar SenSharma
> Assignee: Alexey Loubyansky
> Fix For: 1.0.0.Alpha6
>
>
> - CLI "deploy" command with open quote and tab for completion results in a "StringIndexOutOfBoundsException" exception
> - Type 'connect' to connect to the server or 'help' for the list of supported commands.
> {code}
> [disconnected /] connect
> [standalone@localhost:9999 /] deploy "d<Tab>
> [standalone@localhost:9990 /] deploy "djava.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1958)
> at org.jboss.as.cli.handlers.WindowsFilenameTabCompleter.complete(WindowsFilenameTabCompleter.java:54)
> at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:229)
> at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:73)
> at org.jboss.as.cli.CommandCompleter.doComplete(CommandCompleter.java:126)
> at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:63)
> at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:102)
> at org.jboss.aesh.console.Console.complete(Console.java:1155)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:550)
> at org.jboss.aesh.console.Console.read(Console.java:452)
> at org.jboss.aesh.console.Console.read(Console.java:346)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:178)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1283)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:254)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:312)
> at org.jboss.modules.Main.main(Main.java:460)
> Press any key to continue . . .
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFCORE-58) Setting some locales causes missing buttons on console and throws errors.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-58?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFCORE-58:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1130863, https://bugzilla.redhat.com/show_bug.cgi?id=1141668 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1130863)
> Setting some locales causes missing buttons on console and throws errors.
> -------------------------------------------------------------------------
>
> Key: WFCORE-58
> URL: https://issues.jboss.org/browse/WFCORE-58
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha4
> Reporter: Jay Kumar SenSharma
> Assignee: Tomaz Cerar
> Fix For: 1.0.0.Alpha5
>
> Attachments: mssing_add_remove_disable_Buttons.png
>
>
> - When WildFly 9 Alpha1 is started with the following system properties in the "standalone.conf" then the admin console behaves abnormally and shows some missing buttons in the console. See attached screenshot "mssing_add_remove_disable_Buttons.png".
> {code}
> JAVA_OPTS="$JAVA_OPTS -Duser.country=TR -Duser.language=tr"
> {code}
> - Also it throws following Error while accessing the console URL like [1]
> [1] http://localhost:9990/console/App.html#datasources
> {code}
> 10:39:39,223 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-8) WFLYCTL0013: Operation ("check-resource-access") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "*"),
> ("connection-properties" => "*")
> ]): java.lang.IllegalArgumentException: No enum constant org.jboss.as.controller.registry.AttributeAccess.Storage.CONFİGURATİON
> at java.lang.Enum.valueOf(Enum.java:236) [rt.jar:1.7.0_51]
> at org.jboss.as.controller.registry.AttributeAccess$Storage.valueOf(AttributeAccess.java:91) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler$CheckResourceAccessHandler.execute(ReadResourceDescriptionHandler.java:431) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:603) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:481) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1060) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:296) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:165) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:179) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
> at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_51]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [wildfly-controller-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:83) [wildfly-domain-http-interface-1.0.0.Alpha3.jar:1.0.0.Alpha3]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta5.jar:1.1.0.Beta5]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-597) Custom implementations of dynamic salience don't work
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-597?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-597.
--------------------------------
Fix Version/s: 6.2.0.CR1
Resolution: Done
> Custom implementations of dynamic salience don't work
> -----------------------------------------------------
>
> Key: DROOLS-597
> URL: https://issues.jboss.org/browse/DROOLS-597
> Project: Drools
> Issue Type: Bug
> Environment: Eclipse/Windows 7 - 64 bits
> Reporter: Yacine Jaber
> Assignee: Mario Fusco
> Fix For: 6.2.0.CR1
>
> Attachments: SalienceProject.7z, WodSalienceImpl.java
>
>
> I have implemented my own bean (Salience) that manage the dynamic salience for the rules.
> After building the drl file i overlaod the salience of the rules with my dynamic salience WodSalienceImpl(Attached file).
> However, the salience is not respected even if this bean was called (getValue) before the match creation.
> N.B: I used MVELSalience by writing the dynamic salience into the rules(MEVL expression). The result was the same.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-597) Custom implementations of dynamic salience don't work
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-597?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-597:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Custom implementations of dynamic salience don't work
> -----------------------------------------------------
>
> Key: DROOLS-597
> URL: https://issues.jboss.org/browse/DROOLS-597
> Project: Drools
> Issue Type: Bug
> Environment: Eclipse/Windows 7 - 64 bits
> Reporter: Yacine Jaber
> Assignee: Mario Fusco
> Fix For: 6.2.0.CR1
>
> Attachments: SalienceProject.7z, WodSalienceImpl.java
>
>
> I have implemented my own bean (Salience) that manage the dynamic salience for the rules.
> After building the drl file i overlaod the salience of the rules with my dynamic salience WodSalienceImpl(Attached file).
> However, the salience is not respected even if this bean was called (getValue) before the match creation.
> N.B: I used MVELSalience by writing the dynamic salience into the rules(MEVL expression). The result was the same.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-595) Generate a warning when ruleflow and agenda groups are used in the same rule
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-595?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-595:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Generate a warning when ruleflow and agenda groups are used in the same rule
> ----------------------------------------------------------------------------
>
> Key: DROOLS-595
> URL: https://issues.jboss.org/browse/DROOLS-595
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.2.0.Beta1
> Reporter: Davide Sottara
> Assignee: Mario Fusco
> Priority: Minor
> Fix For: 6.2.0.CR1
>
>
> Ruleflow and agenda groups have been unified since 6.x
> Specifying both attributes in a rule will result in one of them being
> overwritten. Specifically, RFGs are implemented using AGs, but
> the RFG name is the one that will be used in case of a conflict.
> A warning should be generated in case of potential conflicts
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-568) Module dependencies missing from brms and bpms layers to support remote runtime engines
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-568?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-568:
------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1124885|https://bugzilla.redhat.com/show_bug.cgi?id=1124885] from MODIFIED to ON_QA
> Module dependencies missing from brms and bpms layers to support remote runtime engines
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-568
> URL: https://issues.jboss.org/browse/DROOLS-568
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.CR2
> Environment: JBoss EAP 6.3
> Reporter: David Ward
> Assignee: Jeremy Lindop
>
> Regarding artifacts:
> org.kie:kie-eap-distributions-brms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-brms:brms-layer:6.0.2-redhat-7
> org.kie:kie-eap-distributions-bpms-layer::6.1.0.CR2
> org.kie:kie-eap-integration-bpms:bpms-layer:6.0.2-redhat-7
> And these modules:
> modules/system/layers/brms/org/kie/main/module.xml
> modules/system/layers/bpms/org/kie/main/module.xml
> There are missing libraries needed to support the remote rest and jms runtime engine factories (and associated builders):
> org.kie.services.client.api.RemoteJmsRuntimeEngineFactory/Builder
> org.kie.services.client.api.RemoteRestRuntimeEngineFactory/Builder
> Including at least these resource-roots:
> org.kie.remote:kie-services-client
> org.kie.remote:kie-services-jaxb
> and this dependency module:
> org.jboss.resteasy:resteasy-jackson-provider
> (Although still validating other possible dependencies.)
> Without having all the necessary libraries included and dependencies linked, using the RemoteRuntimeEngines via kie-services-client is not possible.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1882) Possible NullPointerException in JDBC_PING
by Thomas Santosa (JIRA)
Thomas Santosa created JGRP-1882:
------------------------------------
Summary: Possible NullPointerException in JDBC_PING
Key: JGRP-1882
URL: https://issues.jboss.org/browse/JGRP-1882
Project: JGroups
Issue Type: Bug
Affects Versions: 3.5
Environment: Windows Server 2012
Reporter: Thomas Santosa
Assignee: Bela Ban
JGroups version: 3.5.0 final
{noformat}
Caused by: java.lang.NullPointerException
at org.jgroups.protocols.JDBC_PING.readAll(Katalis.java:225)
at org.jgroups.protocols.JDBC_PING.readAll(Katalis.java:192)
at org.jgroups.protocols.JDBC_PING.findMembers(Katalis.java:128)
at org.jgroups.protocols.Discovery.findMembers(Katalis.java:226)
at org.jgroups.protocols.Discovery.down(Katalis.java:366)
at org.jgroups.protocols.JDBC_PING.down(Katalis.java:124)
at org.jgroups.protocols.MERGE2.down(Katalis.java:222)
at org.jgroups.protocols.FD_SOCK.down(Katalis.java:356)
at org.jgroups.protocols.FD_ALL.down(Katalis.java:233)
at org.jgroups.protocols.VERIFY_SUSPECT.down(Katalis.java:92)
at org.jgroups.protocols.pbcast.NAKACK2.down(Katalis.java:551)
at org.jgroups.protocols.UNICAST2.down(Katalis.java:584)
at org.jgroups.protocols.pbcast.STABLE.down(Katalis.java:347)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(Katalis.java:76)
at org.jgroups.protocols.pbcast.ClientGmsImpl.join(Katalis.java:41)
at org.jgroups.protocols.pbcast.GMS.down(Katalis.java:1084)
at org.jgroups.protocols.FlowControl.down(Katalis.java:349)
at org.jgroups.protocols.FlowControl.down(Katalis.java:349)
at org.jgroups.protocols.FRAG2.down(Katalis.java:136)
at org.jgroups.protocols.RSVP.down(Katalis.java:145)
at org.jgroups.stack.ProtocolStack.down(Katalis.java:1039)
at org.jgroups.JChannel.down(Katalis.java:785)
at org.jgroups.JChannel._connect(Katalis.java:558)
... 40 more
{noformat}
I suspect that data is null. The code in line 225 is
{code}
if(local_addr != null && !local_addr.equals(data.getAddress()))
addDiscoveryResponseToCaches(data.getAddress(), data.getLogicalName(), data.getPhysicalAddr());
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month