[JBoss JIRA] (JBJCA-1138) TransactionSynchronizer leaks memory and causes deadlocks in jacorb
by Andrey Smirnov (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1138?page=com.atlassian.jira.plugin... ]
Andrey Smirnov updated JBJCA-1138:
----------------------------------
Description:
Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
296: Record record = records.get(tx);
But 'records' map uses TransactionKey as key and above line should be written as
296:TransactionKey key = new TransactionKey(tx);
297: Record record = records.get(key);
I've checked 1.0.22 containing applied fix and mem-leaks and deadlocks are all gone
was:
Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
296: Record record = records.get(tx);
But 'records' map uses TransactionKey as key and above line should be written as
296:TransactionKey key = new TransactionKey(tx);
297: Record record = records.get(key);
I've checked fixed 1.0.22 and mem-leaks and deadlocks are all gone
> TransactionSynchronizer leaks memory and causes deadlocks in jacorb
> -------------------------------------------------------------------
>
> Key: JBJCA-1138
> URL: https://issues.jboss.org/browse/JBJCA-1138
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.23.Final
> Reporter: Andrey Smirnov
> Assignee: Jesper Pedersen
> Priority: Blocker
> Fix For: 1.0.24.Final
>
>
> Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
> 296: Record record = records.get(tx);
> But 'records' map uses TransactionKey as key and above line should be written as
> 296:TransactionKey key = new TransactionKey(tx);
> 297: Record record = records.get(key);
> I've checked 1.0.22 containing applied fix and mem-leaks and deadlocks are all gone
--
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, 5 months
[JBoss JIRA] (JBJCA-1138) TransactionSynchronizer leaks memory and causes deadlocks in jacorb
by Andrey Smirnov (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1138?page=com.atlassian.jira.plugin... ]
Andrey Smirnov commented on JBJCA-1138:
---------------------------------------
I think vague term failures means deadlocks in jacorb caused by unreleased lock in TransactionSynchronizer
> TransactionSynchronizer leaks memory and causes deadlocks in jacorb
> -------------------------------------------------------------------
>
> Key: JBJCA-1138
> URL: https://issues.jboss.org/browse/JBJCA-1138
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.23.Final
> Reporter: Andrey Smirnov
> Assignee: Jesper Pedersen
> Priority: Blocker
> Fix For: 1.0.24.Final
>
>
> Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
> 296: Record record = records.get(tx);
> But 'records' map uses TransactionKey as key and above line should be written as
> 296:TransactionKey key = new TransactionKey(tx);
> 297: Record record = records.get(key);
--
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, 5 months
[JBoss JIRA] (JBJCA-1138) TransactionSynchronizer leaks memory and causes deadlocks in jacorb
by Andrey Smirnov (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1138?page=com.atlassian.jira.plugin... ]
Andrey Smirnov edited comment on JBJCA-1138 at 2/10/14 7:31 AM:
----------------------------------------------------------------
Seems like rollback to August is not necessary
was (Author: cheezzario):
I think vague term failures means deadlocks in jacorb caused by unreleased lock in TransactionSynchronizer
> TransactionSynchronizer leaks memory and causes deadlocks in jacorb
> -------------------------------------------------------------------
>
> Key: JBJCA-1138
> URL: https://issues.jboss.org/browse/JBJCA-1138
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.23.Final
> Reporter: Andrey Smirnov
> Assignee: Jesper Pedersen
> Priority: Blocker
> Fix For: 1.0.24.Final
>
>
> Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
> 296: Record record = records.get(tx);
> But 'records' map uses TransactionKey as key and above line should be written as
> 296:TransactionKey key = new TransactionKey(tx);
> 297: Record record = records.get(key);
--
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, 5 months
[JBoss JIRA] (JBJCA-1138) TransactionSynchronizer leaks memory and causes deadlocks in jacorb
by Andrey Smirnov (JIRA)
Andrey Smirnov created JBJCA-1138:
-------------------------------------
Summary: TransactionSynchronizer leaks memory and causes deadlocks in jacorb
Key: JBJCA-1138
URL: https://issues.jboss.org/browse/JBJCA-1138
Project: IronJacamar
Issue Type: Bug
Components: Core
Affects Versions: 1.0.23.Final
Reporter: Andrey Smirnov
Assignee: Jesper Pedersen
Priority: Blocker
Fix For: 1.0.24.Final
Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44
296: Record record = records.get(tx);
But 'records' map uses TransactionKey as key and above line should be written as
296:TransactionKey key = new TransactionKey(tx);
297: Record record = records.get(key);
--
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, 5 months
[JBoss JIRA] (WFLY-130) Cygwin, add-user.sh and error "JBAS015232: No java.io.Console available to interact with user."
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-130?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved WFLY-130.
-----------------------------------
Fix Version/s: 8.0.0.Final
(was: 9.0.0.CR1)
Resolution: Done
The associated pull request was resolved.
If there are additional problems please create new Jira issues - if there are multiple problems it is better to have one Jira per problem so they can be resolved independently.
> Cygwin, add-user.sh and error "JBAS015232: No java.io.Console available to interact with user."
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-130
> URL: https://issues.jboss.org/browse/WFLY-130
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Affects Versions: 8.0.0.CR1
> Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686
> Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode
> JBoss AS 7.1.3.Final
> Reporter: Bernard Giroud
> Assignee: Darran Lofthouse
> Labels: as7, investigation_required, management
> Fix For: 8.0.0.Final
>
>
> First of all, the add-user.sh script has an invalid syntax on line 14 which reads:
> {code}
> cygwin = true;
> {code}
> It should read:
> {code}
> cygwin=true;
> {code}
> without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done.
> Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME.
> Finally, issuance of the following command : bin/add-user.sh u p
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107)
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Issuance of the following command : bin/add-user.sh
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Option --silent doesn't make a difference.
> An obvious workaround exists though: use with a CMD windows
> {noformat}
> bin\add-user.bat u p
> {noformat}
--
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, 5 months
[JBoss JIRA] (WFLY-130) Cygwin, add-user.sh and error "JBAS015232: No java.io.Console available to interact with user."
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-130?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated WFLY-130:
----------------------------------
Labels: as7 investigation_required management (was: as7 management)
> Cygwin, add-user.sh and error "JBAS015232: No java.io.Console available to interact with user."
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-130
> URL: https://issues.jboss.org/browse/WFLY-130
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Affects Versions: 8.0.0.CR1
> Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686
> Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode
> JBoss AS 7.1.3.Final
> Reporter: Bernard Giroud
> Assignee: Darran Lofthouse
> Labels: as7, investigation_required, management
> Fix For: 9.0.0.CR1
>
>
> First of all, the add-user.sh script has an invalid syntax on line 14 which reads:
> {code}
> cygwin = true;
> {code}
> It should read:
> {code}
> cygwin=true;
> {code}
> without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done.
> Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME.
> Finally, issuance of the following command : bin/add-user.sh u p
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107)
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Issuance of the following command : bin/add-user.sh
> Gives:
> {noformat}
> cygpath: can't convert empty path
> Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur.
> at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78)
> at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {noformat}
> Option --silent doesn't make a difference.
> An obvious workaround exists though: use with a CMD windows
> {noformat}
> bin\add-user.bat u p
> {noformat}
--
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, 5 months
[JBoss JIRA] (WFLY-335) Catching custom login module exceptions in remote client
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-335?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated WFLY-335:
----------------------------------
Fix Version/s: (was: 9.0.0.CR1)
> Catching custom login module exceptions in remote client
> --------------------------------------------------------
>
> Key: WFLY-335
> URL: https://issues.jboss.org/browse/WFLY-335
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Remoting, Security, Server
> Environment: Win 7 64 Bit
> 4 GB RAM
> java 1.6
> Reporter: Serkan Yıldırım
> Assignee: Darran Lofthouse
> Labels: exception, login, login-module, remoting
>
> This feature request is related with the discussion:
> https://community.jboss.org/message/732948#732948
> I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client. Darran said that it's not supported in this version. I think it is a necessary feature because a remote user could be informed why login is failed.
--
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, 5 months
[JBoss JIRA] (WFLY-326) Logout a remote client from server and clearing login module cache.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-326?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated WFLY-326:
----------------------------------
Fix Version/s: (was: 9.0.0.CR1)
> Logout a remote client from server and clearing login module cache.
> -------------------------------------------------------------------
>
> Key: WFLY-326
> URL: https://issues.jboss.org/browse/WFLY-326
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Remoting, Security, Server
> Environment: java 1.6
> win 7 64 bit
> 4 gb ram
> Reporter: Serkan Yıldırım
> Assignee: Darran Lofthouse
> Labels: Remoting_Management, jboss-as7, login-module, logout, remoting, security
>
> I have a custom login module. I authenticate and authorize a user (creating roles) by using this custom module. When i close the remote application, i want to logout the user from server so that clear login module cache, i.e deleting principals and roles from the cache. I couldn't find a solution for this problem in forum. If it exists, could you please explain it, 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
12 years, 5 months