[JBoss JIRA] (AS7-4468) Cannot remove and re-add socket-binding group
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-4468:
-------------------------------------
Summary: Cannot remove and re-add socket-binding group
Key: AS7-4468
URL: https://issues.jboss.org/browse/AS7-4468
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
Error message when trying to (remove and) add a socket-binding-group in domain mode:
First remove:
{ "operation" => "remove", "address" => [("socket-binding-group" => "standard-sockets")] }
Result:
{
"outcome" : "success",
"result" : null,
"server-groups" : {"server-group-1" : {"server-1" : {
"host" : "master",
"response" : {"outcome" : "success"}
}}}
}
Now add again:
{
"name" : "standard-sockets",
"default-interface" : "public",
"operation" : "add",
"address" : [{ "socket-binding-group" : "standard-sockets" }]
}
Result:
{
"outcome" : "failed",
"result" : null,
"failure-description" : "JBAS010839: Operation failed or was rolled back on all servers.",
"rolled-back" : true,
"server-groups" : {"server-group-1" : {"server-1" : {
"host" : "master",
"response" : { "outcome" : "failed", "failure-description" : "JBAS014749: Operation handler failed: Service jboss.socket-binding-manager is already registered", "rolled-back" : true }
}}}
}
For me, this seems a bit strange. If an error shall be produced, then it should be thrown when removing the socket-binding-group, as there is a server running referencing the socket-binding-group via server-group. But if the socket-binding-group can be removed, it should also be possible to add it again (possibly with new defined socket-bindings in the group, then trigger a restart of the server in order to take the newly configured ports into account).
--
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, 10 months
[JBoss JIRA] (JGRP-1438) GMS shouldn't bundle requests that can't be processed together
by Benoit Leblanc (JIRA)
Benoit Leblanc created JGRP-1438:
------------------------------------
Summary: GMS shouldn't bundle requests that can't be processed together
Key: JGRP-1438
URL: https://issues.jboss.org/browse/JGRP-1438
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0, 3.1
Reporter: Benoit Leblanc
Assignee: Bela Ban
Priority: Minor
GMS's Requests are divided into two categories:
1/ Can Be Processed Together (CBPT): JOIN, LEAVE and SUSPECT
2 Can Not Be Processed Together (CNBPT) : MERGE and JOIN_WITH_STATE_TRANSFER
Bundling concerns only CBPT requests. So when a CNBPT request is received, it should be processed immediately.
Currently, a MERGE request is postponed due to bundling instead of being executed immediately. Two conditions to unblock it:
- Timeout expiration.
- Receiving another message. Note that whatever the following message is, it can't be processed with CBPT message
Expected behavior: Treating immediately CNBPT requests
A simple solution: Bring a light modification to method GMS.ViewHandler.run() at line 1333
-------------
if(wait_time > 0)
becomes :
if(wait_time > 0 && firstRequest.canBeProcessedTogether(firstRequest))
-------------
Note that if a request can't be processed with a request of the same type => it coudn't be processed with any other request type
--
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, 10 months
[JBoss JIRA] (JBRULES-3534) DSL expander causes a StackOverflowError on Solaris
by Mario Fusco (JIRA)
Mario Fusco created JBRULES-3534:
------------------------------------
Summary: DSL expander causes a StackOverflowError on Solaris
Key: JBRULES-3534
URL: https://issues.jboss.org/browse/JBRULES-3534
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
When running Drools unit tests on Solaris with Sun JDK 6, the following test throws a SOE:
org.drools.jsr94.rules.StatefulRuleSessionTest.testContainsObject
java.lang.StackOverflowError
at java.util.regex.Pattern$Loop.match(Pattern.java:4275)
at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)
at java.util.regex.Pattern$BranchConn.match(Pattern.java:4078)
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)
at java.util.regex.Pattern$Branch.match(Pattern.java:4114)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)
at java.util.regex.Pattern$Loop.match(Pattern.java:4295)
...
Turns out this is because of a bug in Sun JDK that will never be fixed:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5050507
--
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, 10 months