[JBoss JIRA] (WFLY-3845) Share the same jsessionid in different context root
by Sandeep Samdaria (JIRA)
Sandeep Samdaria created WFLY-3845:
--------------------------------------
Summary: Share the same jsessionid in different context root
Key: WFLY-3845
URL: https://issues.jboss.org/browse/WFLY-3845
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.1.0.Final
Environment: Ubuntu 12.04
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Wildfly 8.1.0.Final
Reporter: Sandeep Samdaria
Assignee: Stuart Douglas
I have two applications which need a Single Sign On. User once logged into an application should not need login again to another application.
To achieve that I was storing the session id in the cookie. The other application used to retrieve the session and verify the user.
Now, the problem that I am facing, after upgrading to wildfly, is that the each application is producing different jsessionid. I have also tried the workaround mentioned in https://issues.jboss.org/browse/WFLY-3617, but in vain.
I have deployed the same wars in jboss-eap-6.2 and that worked for me.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3834) Memory leak in org.xnio.ByteBufferSlicePool
by Sergey Lisovoy (JIRA)
[ https://issues.jboss.org/browse/WFLY-3834?page=com.atlassian.jira.plugin.... ]
Sergey Lisovoy commented on WFLY-3834:
--------------------------------------
Hooray! It works. No more memory leaking!
Thank you, guys!
I push my test project to github: [https://github.com/lis0x90/jboss-remoting-momory-leak-reproduce]
When it patch may be releassed?
> Memory leak in org.xnio.ByteBufferSlicePool
> -------------------------------------------
>
> Key: WFLY-3834
> URL: https://issues.jboss.org/browse/WFLY-3834
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Reporter: Sergey Lisovoy
> Assignee: David Lloyd
> Labels: memory_leak, memoryleak
>
> I have a simple thread that monitor remote wildfly process status. After some time it fail with OutOfMemory exception.
> I wrote simple exsample how to reproduce its error:
> {code:java}
> package ru.kamis.tests.xniomemoryleaks;
> import org.jboss.as.controller.client.ModelControllerClient;
> import org.jboss.as.controller.client.helpers.Operations;
> import org.jboss.dmr.ModelNode;
> public class OutOfMemoryDemo {
> public static void main(String[] args) throws Exception {
>
> for(int i=0; i<1000000; i++) {
> ModelControllerClient client = null;
> client = ModelControllerClient.Factory.create("localhost", 9990);
>
> ModelNode operation = Operations.createReadAttributeOperation(new ModelNode().setEmptyList(), "server-state");
> client.execute(operation);
>
> client.close();
>
> if(i % 1000 == 0) {
> System.out.println("Processed: " + i);
> }
> }
> }
> }
> {code}
> Program produces folowing output:
> {noformat}
> сен 09, 2014 2:33:20 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.2.2.Final
> сен 09, 2014 2:33:20 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.2.2.Final
> сен 09, 2014 2:33:20 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.3.Final
> Processed: 0
> Processed: 1000
> Processed: 2000
> Processed: 3000
> Processed: 4000
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at java.lang.String.toCharArray(String.java:2746)
> at sun.net.www.ParseUtil.encodePath(ParseUtil.java:107)
> at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:757)
> at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:842)
> at sun.misc.URLClassPath.getResource(URLClassPath.java:199)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:358)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:15)
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> сен 09, 2014 2:35:20 PM org.jboss.as.controller.client.impl.RemotingModelControllerClient finalize
> WARN: JBAS010600: Closing leaked controller client
> JBAS010649: Allocation stack trace:
> at java.lang.Thread.getStackTrace(Thread.java:1589)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:76)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:353)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:200)
> at ru.kamis.tests.xniomemoryleaks.OutOfMemoryDemo.main(OutOfMemoryDemo.java:12)
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space
> {noformat}
> Used libraries:
> {code:xml}
> <dependency>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-controller-client</artifactId>
> <version>8.1.0.Final</version>
> </dependency>
> {code}
> The same bug is reproduced on other xnio versions: 3.2.3.Final, 3.3.0.Beta2
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[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:
-----------------------------------------------
Jay SenSharma <jsenshar(a)redhat.com> changed the Status of [bug 1139515|https://bugzilla.redhat.com/show_bug.cgi?id=1139515] from NEW to POST
> 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
>
> - 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
[JBoss JIRA] (WFLY-3844) Authentication cache is not flushed on logout
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-3844:
------------------------------------
Summary: Authentication cache is not flushed on logout
Key: WFLY-3844
URL: https://issues.jboss.org/browse/WFLY-3844
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.1.0.Final
Reporter: Stuart Douglas
Assignee: Stuart Douglas
This means that if a users details are changed even if they log in and out then these details will not be reflected when the user logs in again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (LOGMGR-113) Create a better way to handle a TCP reconnect policy
by James Perkins (JIRA)
James Perkins created LOGMGR-113:
------------------------------------
Summary: Create a better way to handle a TCP reconnect policy
Key: LOGMGR-113
URL: https://issues.jboss.org/browse/LOGMGR-113
Project: JBoss Log Manager
Issue Type: Enhancement
Reporter: James Perkins
Assignee: James Perkins
Fix For: 2.0.0.Beta2
The audit logger in WildFly uses it's own policy to reconnect a TCP connection for the {{SyslogHandler}}. The current {{org.jboss.logmanager.handlers.TcpOutputStream}} handles a reconnection on it's own unless a deprecated constructor is used. A way to set some kind of policy or enable the reconnection to be turned off should be added.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (LOGMGR-57) Log files cleanup for periodic-rotating-file-handler
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-57?page=com.atlassian.jira.plugin.... ]
James Perkins updated LOGMGR-57:
--------------------------------
Fix Version/s: (was: 2.0.0.Beta2)
> Log files cleanup for periodic-rotating-file-handler
> ----------------------------------------------------
>
> Key: LOGMGR-57
> URL: https://issues.jboss.org/browse/LOGMGR-57
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Reporter: Razvan Popa
> Assignee: James Perkins
> Priority: Minor
>
> Hi,
> It would be useful for the periodic-rotating-file-handler to have a "max-backup-index" attribute to allow the removal of older files like in the size-rotating-file-handler.
> It would also be nice to have something like "archive-older-than" and "delete-older-than" to also keep some older files archived for a while.
> Regards,
> Razvan
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (LOGMGR-57) Log files cleanup for periodic-rotating-file-handler
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-57?page=com.atlassian.jira.plugin.... ]
James Perkins updated LOGMGR-57:
--------------------------------
Fix Version/s: 2.0.0.Beta2
(was: 2.0.0.Beta1)
> Log files cleanup for periodic-rotating-file-handler
> ----------------------------------------------------
>
> Key: LOGMGR-57
> URL: https://issues.jboss.org/browse/LOGMGR-57
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Reporter: Razvan Popa
> Assignee: James Perkins
> Priority: Minor
> Fix For: 2.0.0.Beta2
>
>
> Hi,
> It would be useful for the periodic-rotating-file-handler to have a "max-backup-index" attribute to allow the removal of older files like in the size-rotating-file-handler.
> It would also be nice to have something like "archive-older-than" and "delete-older-than" to also keep some older files archived for a while.
> Regards,
> Razvan
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years