March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4093) Intermittent failure in AsyncMethodTestCase - @Ignore("EJBCLIENT-28")

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4093: --------------------------------- Summary: Intermittent failure in AsyncMethodTestCase - @Ignore("EJBCLIENT-28") Key: AS7-4093 URL: https://issues.jboss.org/browse/AS7-4093 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Ondrej Zizka Assignee: Ondřej Chaloupka I've tried this after EJBCLIENT-28 was resolved, and see this interm.: {code} java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at org.jboss.as.test.integration.ejb.async.AsyncMethodTestCase.testAsyncDescriptor(AsyncMethodTestCase.java:248) {code} Ondro can you please check? -- 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

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-4092) Remote EJB UserTransaction fails if no EJB invocations occur between begin() and commit/rollback

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4092: ----------------------------------- Summary: Remote EJB UserTransaction fails if no EJB invocations occur between begin() and commit/rollback Key: AS7-4092 URL: https://issues.jboss.org/browse/AS7-4092 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.1.Final -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-4002) Some of subsytem configurations statically refer to localhost

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-4002: ---------------------------------- Summary: Some of subsytem configurations statically refer to localhost Key: AS7-4002 URL: https://issues.jboss.org/browse/AS7-4002 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Reporter: Ivo Studensky Assignee: Kabir Khan Fix For: 7.1.1.Final Some of subsystem configurations in build/src/main/resources/configuration/examples/subsystems directory include URLs hardcoded to localhost. These should be replaced by ${jboss.bind.address:127.0.0.1} or something like that. Otherwise it will cause failures on a IP different to 127.0.0.1 or in IPv6 environment. Affected conf files: subsystems/xts.xml subsystems/jaxr.xml This issue is related to AS7-3806 which is the reason why I am assigning it to Kabir. I've prepared the pull request for this. -- 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

14 years, 1 month

2
9
0 / 0

[JBoss JIRA] (AS7-3905) Allow security domain configurations to reference a deployment login module

by Jason Greene (JIRA)

Jason Greene created AS7-3905: --------------------------------- Summary: Allow security domain configurations to reference a deployment login module Key: AS7-3905 URL: https://issues.jboss.org/browse/AS7-3905 Project: Application Server 7 Issue Type: Feature Request Reporter: Jason Greene Fix For: 7.1.1.Final A few customers and users needs the ability to deploy login modules. While in the future we may want to create more infrastructure around this. A simple short term solution would be to extend our module="" notion to accept deploy modules, and then have picketbox use the ServiceModuleLoader. -- 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

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] (AS7-2536) CLI Configurability

by Vimal Kansal (Created) (JIRA)

CLI Configurability ------------------- Key: AS7-2536 URL: https://issues.jboss.org/browse/AS7-2536 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Vimal Kansal Assignee: Alexey Loubyansky +1 on the CLI config may ping you later in the week as we are getting close to adding both SSL and Kerberos to Remoting so both may need some static config to configure. Regards, Darran Lofthouse. On 11/07/2011 01:32 PM, Alexey Loubyansky wrote: > > No, it's not and deserves a jira. > > > > There should be a CLI config somewhere. > > Besides the history file location and name, there should be the length > > of the history which is 500 by default. > > (Related to history 'history --clear' clears only the in-memory one but > > doesn't touch the file, probably it should, to be consistent.) > > > > There are other things to store. Not sure yet whether they deserve a > > separate file. E.g. rollout plans. > > > > Alexey > > > > On 11/07/2011 06:19 AM, Vimal Kansal wrote: >> >> Hi, >> >> >> >> By default .jboss-cli-history file is created in home folder. I was >> >> wondering if this is configurable? >> >> >> >> Thx >> >> >> >> Vimal -- 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

14 years, 1 month

4
3
0 / 0

[JBoss JIRA] (AS7-333) Context is lost if a service fails to start for a 'random' reason

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-333?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved AS7-333. ----------------------------- Fix Version/s: (was: 7.2.0.Alpha1) Resolution: Won't Fix Unlikely to be fixed in the AS7 timeframe. > Context is lost if a service fails to start for a 'random' reason > ----------------------------------------------------------------- > > Key: AS7-333 > URL: https://issues.jboss.org/browse/AS7-333 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Carlo de Wolf > Assignee: David Lloyd > Priority: Minor > > The error message only contains "Failed to start service" it would be nice if the optional causing message is also appended. > {noformat} > 13:58:53,058 INFO [org.jboss.as.server] (MSC service thread 1-9) Service status report > Services which failed to start: > service jboss.deployment.unit."welcome.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."welcome.war": Failed to start service > {noformat} > https://github.com/jbossas/jboss-msc/blob/1.0.0.Beta8/src/main/java/org/j... -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1455) Log shows a parser error, but not the cause

by Heiko Rupp (JIRA)

Log shows a parser error, but not the cause ------------------------------------------- Key: AS7-1455 URL: https://issues.jboss.org/browse/AS7-1455 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry I see this from time to time: 13:20:50,933 ERROR [org.jboss.as.domain.http.api] (HttpManagementService-threads - 219) Unexpected error executing model request: java.io.IOException: Parser error at org.jboss.dmr.ModelNode.fromJSONStream(ModelNode.java:1221) at org.jboss.as.domain.http.server.DomainApiHandler.convertPostRequest(DomainApiHandler.java:323) at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:187) at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:123) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:85) at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:606) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:578) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] at org.jboss.threads.JBossThread.run(JBossThread.java:122) but can't fix what we send, as the error message does not tell -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] (AS7-3577) Blocked Thread when Remote Client Terminates

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3577: ------------------------------------- Summary: Blocked Thread when Remote Client Terminates Key: AS7-3577 URL: https://issues.jboss.org/browse/AS7-3577 Project: Application Server 7 Issue Type: Bug Components: Remoting Reporter: Darran Lofthouse Assignee: David Lloyd Priority: Critical Fix For: 7.1.0.Final If a remote client is killed which was connected to AS7 using a SSL connection the thread handling the close gets stuck as: - "Remoting "localhost:MANAGEMENT" read-1" prio=10 tid=0x00007ff3f8170800 nid=0x7b2e runnable [0x00007ff3d70ee000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.FileDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198) at sun.nio.ch.IOUtil.read(IOUtil.java:171) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243) - locked <0x00000000e12542e8> (a java.lang.Object) at org.xnio.nio.AbstractNioStreamChannel.read(AbstractNioStreamChannel.java:249) at org.xnio.ssl.JsseConnectedSslStreamChannel.handleUnwrapResult(JsseConnectedSslStreamChannel.java:522) - locked <0x00000000e08a3e38> (a org.xnio.ByteBufferSlicePool$PooledByteBuffer) at org.xnio.ssl.JsseConnectedSslStreamChannel.handleHandshake(JsseConnectedSslStreamChannel.java:396) - locked <0x00000000e08a3e38> (a org.xnio.ByteBufferSlicePool$PooledByteBuffer) at org.xnio.ssl.JsseConnectedSslStreamChannel.doFlush(JsseConnectedSslStreamChannel.java:634) at org.xnio.ssl.JsseConnectedSslStreamChannel.flushAction(JsseConnectedSslStreamChannel.java:609) - locked <0x00000000e08a3ea0> (a org.xnio.ByteBufferSlicePool$PooledByteBuffer) at org.xnio.channels.TranslatingSuspendableChannel.flush(TranslatingSuspendableChannel.java:604) at org.xnio.channels.FramedMessageChannel.doFlush(FramedMessageChannel.java:299) at org.xnio.channels.FramedMessageChannel.closeAction(FramedMessageChannel.java:307) - locked <0x00000000e08a40b0> (a org.xnio.Buffers$4) at org.xnio.channels.TranslatingSuspendableChannel.close(TranslatingSuspendableChannel.java:811) at org.xnio.IoUtils.safeClose(IoUtils.java:137) at org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:101) at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.shutdownWrites(RemoteConnection.java:242) - locked <0x00000000e1254070> (a org.jboss.remoting3.remote.RemoteConnection) at org.jboss.remoting3.remote.RemoteConnection.shutdownWrites(RemoteConnection.java:118) at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:128) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:75) at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:42) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.nio.NioHandle.run(NioHandle.java:90) at org.xnio.nio.WorkerThread.run(WorkerThread.java:184) After this new clients can not connect and the server can not be shut down. -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] (AS7-3955) jboss-deployment-structure.xml top level exclusion does not work

by Markus Lindblom (JIRA)

Markus Lindblom created AS7-3955: ------------------------------------ Summary: jboss-deployment-structure.xml top level exclusion does not work Key: AS7-3955 URL: https://issues.jboss.org/browse/AS7-3955 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.0.Final Environment: Windows, RedHat Linux Reporter: Markus Lindblom Assignee: David Lloyd When I try to exclude for example Log4J in the deployment structure I have to exclude it from every subdeployment in the deployment structure file, the top level exclusion should exclude it from the entire EAR and all of its subdeployments. -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-4076) Upgrade Google Guava to 11.0.2

by Julio Pires (JIRA)

Julio Pires created AS7-4076: -------------------------------- Summary: Upgrade Google Guava to 11.0.2 Key: AS7-4076 URL: https://issues.jboss.org/browse/AS7-4076 Project: Application Server 7 Issue Type: Library Upgrade Reporter: Julio Pires JBoss contains the version 10.0.1. This version (11.0.2) contains bugs fixed and improvements. -- 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

14 years, 1 month

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012