February 2012 - jboss-jira - Jboss List Archives

[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, 4 months

4
3
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, 4 months

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, 4 months

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, 4 months

2
2
0 / 0

[JBoss JIRA] (AS7-3891) Need a new version of jboss-remote-naming that builds with jboss-remoting3 3.2.2.GA

by Fernando Nasser (JIRA)

Fernando Nasser created AS7-3891: ------------------------------------ Summary: Need a new version of jboss-remote-naming that builds with jboss-remoting3 3.2.2.GA Key: AS7-3891 URL: https://issues.jboss.org/browse/AS7-3891 Project: Application Server 7 Issue Type: Component Upgrade Components: Remoting Reporter: Fernando Nasser Assignee: David Lloyd Priority: Critical Fix For: 7.1.1.Final AS 7.1.0.Final has remoting 3.2.2.GA and a jboss-remote-naming 1.0.1.Final but the latter does not build with the former. So we need a new version (and tag) for jboss-remote-naming that can be used in the AS and that builds with the jboss-remoting in it (3.2.2.GA currently) References: https://github.com/jbossas/jboss-remote-naming/issues/2 and https://github.com/jbossas/jboss-remote-naming/pull/4 Thanks in advance. -- 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, 4 months

5
6
0 / 0

[JBoss JIRA] (AS7-3871) $JBOSS_CONFIG_DIR not switched to Windows format when running standalone.sh on Cygwin

by Rune Flobakk (JIRA)

Rune Flobakk created AS7-3871: --------------------------------- Summary: $JBOSS_CONFIG_DIR not switched to Windows format when running standalone.sh on Cygwin Key: AS7-3871 URL: https://issues.jboss.org/browse/AS7-3871 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Environment: Windows 7, Cygwin Reporter: Rune Flobakk Assignee: Alexey Loubyansky Paths which are fed to the JVM as parameters are switched to Windows format using cygpath, but $JAVA_CONFIG_DIR seems to have been forgotten. This results in an error during bootup: {quote} Unable to read the logging configuration from 'file:/cygdrive/c/apps/jboss-7.1.0.Final/standalone/configuration/logging.properties' (java.io.FileNotFoundException: \cygdrive\c\apps\jboss-7.1.0.Final\standalone\configuration\logging.properties (The system cannot find the path specified)) {quote} Fix: This line needs to be inserted after line 157 in standalone.sh (inside the {{if $cygwin}} block) {quote} JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"` {quote} The same bug seems to be the case for domain.sh. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1561) <distributable> web applications fail to deploy with the DOMAIN HA configuration

by Riccardo Pasquini (JIRA)

<distributable> web applications fail to deploy with the DOMAIN HA configuration -------------------------------------------------------------------------------- Key: AS7-1561 URL: https://issues.jboss.org/browse/AS7-1561 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Environment: riccardo@7suse:~> uname -a Linux 7suse.localhost 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux riccardo@7suse:~> java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) Reporter: Riccardo Pasquini Assignee: Remy Maucherat Using the console to deploy a web application packaged as WAR and described as <distributable /> fails on enabling in the server group with the following message: Failed to disable Webapp-0.1-SNAPSHOT.war. Unexpected HTTP response: 500 Request { "address" => [ ("server-group" => "dragon-standalone"), ("deployment" => "Webapp-0.1-SNAPSHOT.war") ], "operation" => "deploy" } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => [("dragon-standalone" => {"master" => { "host" => "master", "response" => { "outcome" => "failed", "failure-description" => "Operation handler failed to complete", "rolled-back" => true } }})]}, "failure-description" => "Operation failed or was rolled back on all servers.", "rolled-back" => true } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
6
0 / 0

[JBoss JIRA] (AS7-3727) Arq: Make mgmt address and port available in the @Deployment method.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3727: --------------------------------- Summary: Arq: Make mgmt address and port available in the @Deployment method. Key: AS7-3727 URL: https://issues.jboss.org/browse/AS7-3727 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka 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, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (AS7-1658) Referencing a remote business view within the same server leads to CCE

by Carlo de Wolf (JIRA)

Referencing a remote business view within the same server leads to CCE ---------------------------------------------------------------------- Key: AS7-1658 URL: https://issues.jboss.org/browse/AS7-1658 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.1.Final Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
11
0 / 0

[JBoss JIRA] (AS7-3809) Limit of open file descriptors missing in standalone.sh/domain.sh in AS7

by Luka Furlan (JIRA)

Luka Furlan created AS7-3809: -------------------------------- Summary: Limit of open file descriptors missing in standalone.sh/domain.sh in AS7 Key: AS7-3809 URL: https://issues.jboss.org/browse/AS7-3809 Project: Application Server 7 Issue Type: Feature Request Components: Scripts, Server Affects Versions: 7.1.0.Final Reporter: Luka Furlan Assignee: Brian Stansberry Priority: Minor In AS6 run.sh script included an option to raise the limit of open file descriptors. In AS7, where run.sh was replaced by standalone.sh/domain.sh, MAX_FD variable still exists, but it's not used. If you decide to include this functionality in AS7, it would be great if the flow of the script would be changed, so it doesn't immediately stop when MAX_FD could not be set, but it tries with a lower value. Something like: {noformat} STEP_VALUE=50 i=${MAX_FD} while [ ${i} -gt 0 ]; do if ulimit -n ${i} 2> /dev/null 1>&2; then percent=`expr ${i} \* 100 \/ ${MAX_FD}` echo "Open files limit set to ${i} (${percent}% value of desired ${MAX_FD})." exit 0 else i=`expr ${i} - ${STEP_VALUE}` fi done {noformat} -- 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, 4 months

4
11
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 February 2012