[JBoss JIRA] (AS7-5634) add-user scripts not checking password strength for management users
by Cheng Fang (JIRA)
Cheng Fang created AS7-5634:
-------------------------------
Summary: add-user scripts not checking password strength for management users
Key: AS7-5634
URL: https://issues.jboss.org/browse/AS7-5634
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.2.0.CR1
Reporter: Cheng Fang
Assignee: Darran Lofthouse
So there is passwd check for app users, like at least x characters long, with mixed letters, numbers, etc.
Is the same strength check applied to management user? I would assume management user passwords have more stringent requirement, at least should be the same as app user. But I can create a management user using password that consists of all letters (more than 8 letters).
--
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
12 years, 2 months
[JBoss JIRA] (JBRULES-3678) Drools 5.4 evaluates wrong on repeated execution
by Thomas Kruse (JIRA)
Thomas Kruse created JBRULES-3678:
-------------------------------------
Summary: Drools 5.4 evaluates wrong on repeated execution
Key: JBRULES-3678
URL: https://issues.jboss.org/browse/JBRULES-3678
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.4.0.Final
Reporter: Thomas Kruse
Assignee: Mark Proctor
Priority: Critical
Regression in Drools 5.4: On repeated evaluation Drools starts to (not) fire rules.
It seems like a knowledge session is getting corrupted over time. Perhaps related to the JIT?
Disabling JIT in mvel did not mitigate the problem, change to Drools 5.3.0 does.
I will add a test project.
--
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
12 years, 2 months
[JBoss JIRA] (AS7-5609) RaRemove does not handle rollback
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5609:
-------------------------------------
Summary: RaRemove does not handle rollback
Key: AS7-5609
URL: https://issues.jboss.org/browse/AS7-5609
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, JCA
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Stefano Maestri
A rollback handling callback needs to be added to the Stage.RUNTIME context.completeStep() call.
--
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
12 years, 2 months
[JBoss JIRA] (JGRP-1529) RELAY2: Intra-site view not being accepted upon inter-site installation failure
by Radim Vansa (JIRA)
Radim Vansa created JGRP-1529:
---------------------------------
Summary: RELAY2: Intra-site view not being accepted upon inter-site installation failure
Key: JGRP-1529
URL: https://issues.jboss.org/browse/JGRP-1529
Project: JGroups
Issue Type: Bug
Reporter: Radim Vansa
Assignee: Bela Ban
When a node becomes coordinator, it sends the VIEW_CHANGE event up the stack. This should result in Receiver.viewAccepted(...) method call. However, when RELAY2 is in stack and the coordinator cannot be reached, it blocks the thread (sending discovery pings) and, therefore, the viewAccepted event is postponed.
In my opinion the inter-site stack should be created and handled in different thread.
Context:
In my case, the coordinator for both local cluster and the global (inter-site) cluster was killed. The FD_SOCK on inter-site stack somehow failed to notice that the coordinator has crashed (more investigation required) and the nodes in global cluster still reported the crashed node as the global coordinator.
Therefore, the new coordinator of local cluster failed to join the global cluster (obviously got no response from the dead global coordinator).
The restarted node joined the local cluster and then tried to join the local Infinispan cache with a new local view ID. However, the coordinator failed to notice (in Infinispan viewAccepted handler which was not called) that he had already installed a new JGroups view and it did not respond to the cache join request because it was waiting until it got the new JGroups view (again, which was installed in JGroups but the viewAccepted did not notified Infinispan about that).
--
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
12 years, 2 months
[JBoss JIRA] (JGRP-1528) RELAY2: batch messages forwarded to remote sites
by Bela Ban (JIRA)
Bela Ban created JGRP-1528:
------------------------------
Summary: RELAY2: batch messages forwarded to remote sites
Key: JGRP-1528
URL: https://issues.jboss.org/browse/JGRP-1528
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.3
If a site is down, then forwarding a message to it will block the thread (actually: wait) for max_forward_attempts * forward_sleep milliseconds.
If we have many incoming messages (from the local site) to be forwarded to the remote site, then having every thread sleep for (say) 10 seconds will increase the thread pool.
We should therefore add *batching* to RELAY2; messages to be forwarded are queued until a certain time has elapsed or the accumulated total size of all queued messages exceeds a certain threshold.
Incoming messages to be forwarded would be added to the queue (allowing the sending thread to be returned to the thread pool). A separate thread (or task) would monitor the queue and do the forwarding, and it would also notice that a site is down and send unreachable messages back to the original senders.
--
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
12 years, 2 months
[JBoss JIRA] (AS7-5870) Services should only be created when the resource adapter is activated
by Jesper Pedersen (JIRA)
Jesper Pedersen created AS7-5870:
------------------------------------
Summary: Services should only be created when the resource adapter is activated
Key: AS7-5870
URL: https://issues.jboss.org/browse/AS7-5870
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.3.Final (EAP)
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Priority: Critical
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
The ResourceAdapterDeploymentService class creates services for the resource adapter deployment even though the resource adapter isn't activated
--
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
12 years, 2 months
[JBoss JIRA] (AS7-5863) simplified dmr format parser doesn't support '\' linebreaks
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created AS7-5863:
--------------------------------------
Summary: simplified dmr format parser doesn't support '\' linebreaks
Key: AS7-5863
URL: https://issues.jboss.org/browse/AS7-5863
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.3.Final (EAP)
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
The following fails because the simplified format parser doesn't know how to handle '\' linebreaks.
/subsystem=security/security-domain=DemoAuthRealm/authentication=classic:add( \
login-modules=[ \
{ \
code=Database, \
flag=required, \
module-options=[ \
unauthenticatedIdentity=guest, \
dsJndiName=java:jboss/jdbc/ApplicationDS, \
principalsQuery=select password from users where username=?, \
rolesQuery = "select name, 'Roles' FROM user_roless ur, roles r, user u WHERE u.username=? and u.id = ur.user_id and ur.role_id = r.id", \
hashAlgorithm = MD5, \
hashEncoding = hex) \
] \
} \
] \
)
--
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
12 years, 2 months