April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final

by Rituraj Sinha (JIRA)

[ https://issues.jboss.org/browse/WFLY-3274?page=com.atlassian.jira.plugin.... ] Rituraj Sinha commented on WFLY-3274: ------------------------------------- can anyone please guide us on how to proceed here ..this is the last thing in our migration from jboss 7 to wildfly 8...everything else is working as expected ... > connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3274 > URL: https://issues.jboss.org/browse/WFLY-3274 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Tomaz Cerar > > while using jboss 7.2.0 we were able to fetch above values from the cli command as > {noformat} > [domain@test.com:9999 subsystem=web] ls > configuration valve default-virtual-server=default-host native=false > connector virtual-server instance-id=${jboss.node.name} > [domain@test.com:9999 connector] ls > ajp http > [domain@test.com:9999 connector] cd http > [domain@test.com:9999 connector] pwd > /profile=ha/subsystem=web/connector=http > [domain@test.com:9999 connector=http] ls > configuration max-connections=undefined proxy-port=undefined > ssl max-post-size=2097152 redirect-port=443 > bytesReceived= max-save-post-size=4096 requestCount= > bytesSent= maxTime= scheme=http > enable-lookups=false name=http secure=false > enabled=true processingTime= socket-binding=http > errorCount= protocol=HTTP/1.1 virtual-server=undefined > executor=undefined proxy-name=undefined > {noformat} > > Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8) > as below > {noformat} > [domain@test2.com:9990 subsystem=undertow] ls > buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 ) > configuration servlet-container default-virtual-host=default-host > error-page default-server=default-server instance-id=${jboss.node.name} > {noformat} > > but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as > {noformat} > [domain@test2.com:9990 server=default-server] ls > ajp-listener host http-listener https-listener default-host=default-host servlet-container=default > {noformat} > after getting into http-listener we get the below > {noformat} > [domain@test2.com:9990 http-listener=default] ls > allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http > always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8 > buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default > buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https > {noformat} > > Can someone please look into it ..? -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3149) Windows service on 64 bit systems cannot be stopped

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated WFLY-3149: --------------------------------------- Forum Reference: https://community.jboss.org/message/862793#862793 > Windows service on 64 bit systems cannot be stopped > --------------------------------------------------- > > Key: WFLY-3149 > URL: https://issues.jboss.org/browse/WFLY-3149 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.0.0.Final > Environment: Windows 2008 Server, Windows 7 professional - both 64 bit systems using JDK 1.7.0_09 > Reporter: Mohan Potturi > Assignee: Mladen Turk > > The Windows service cannot be stopped. It says 'stopping' in the windows service user interface window. The only way to stop it is ti actually kill the java process. It works flawlessly on 32 bit systems though. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3282) Remote EJB invocations needs corrected ports and protocol

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3282?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3282: -------------------------------------- Note that Wildfly does still support the 'remote' protocol, it just needs to have the connector explicitly configured, as it is no longer configured by default in order to reduce the port count. > Remote EJB invocations needs corrected ports and protocol > --------------------------------------------------------- > > Key: WFLY-3282 > URL: https://issues.jboss.org/browse/WFLY-3282 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.1.0.CR1 > Reporter: Paul Benedict > Assignee: Darran Lofthouse > Priority: Minor > Labels: jndi, remoting > > This page needs updating. > 1) It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade. > 2) All links to other pages point to AS71 not WFLY8. > https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JN... -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3284) Update add-user to support non-interactive mode without a console without being silent

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3284?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3284: ----------------------------------- Summary: Update add-user to support non-interactive mode without a console without being silent (was: Update add-user to automatically drop into silent mode if already non interactive and no console.) > Update add-user to support non-interactive mode without a console without being silent > -------------------------------------------------------------------------------------- > > Key: WFLY-3284 > URL: https://issues.jboss.org/browse/WFLY-3284 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management, Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > If we have enough information for add-user to run non-interactively and the console is not available we should drop into silent mode instead of reporting an error. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3284) Update add-user to automatically drop into silent mode if already non interactive and no console.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3284: -------------------------------------- Summary: Update add-user to automatically drop into silent mode if already non interactive and no console. Key: WFLY-3284 URL: https://issues.jboss.org/browse/WFLY-3284 Project: WildFly Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse If we have enough information for add-user to run non-interactively and the console is not available we should drop into silent mode instead of reporting an error. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3284) Update add-user to automatically drop into silent mode if already non interactive and no console.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3284?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3284: ----------------------------------- Fix Version/s: 9.0.0.CR1 > Update add-user to automatically drop into silent mode if already non interactive and no console. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3284 > URL: https://issues.jboss.org/browse/WFLY-3284 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > If we have enough information for add-user to run non-interactively and the console is not available we should drop into silent mode instead of reporting an error. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3284) Update add-user to automatically drop into silent mode if already non interactive and no console.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3284?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3284: ----------------------------------- Component/s: Domain Management Scripts > Update add-user to automatically drop into silent mode if already non interactive and no console. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3284 > URL: https://issues.jboss.org/browse/WFLY-3284 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management, Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > If we have enough information for add-user to run non-interactively and the console is not available we should drop into silent mode instead of reporting an error. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3282) Remote EJB invocations needs corrected ports and protocol

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3282?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-3282: -------------------------------------- Assignee: Darran Lofthouse (was: Tom Wells) > Remote EJB invocations needs corrected ports and protocol > --------------------------------------------------------- > > Key: WFLY-3282 > URL: https://issues.jboss.org/browse/WFLY-3282 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.1.0.CR1 > Reporter: Paul Benedict > Assignee: Darran Lofthouse > Priority: Minor > Labels: jndi, remoting > > This page needs updating. > 1) It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade. > 2) All links to other pages point to AS71 not WFLY8. > https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JN... -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3282) Remote EJB invocations needs corrected ports and protocol

by Paul Benedict (JIRA)

[ https://issues.jboss.org/browse/WFLY-3282?page=com.atlassian.jira.plugin.... ] Paul Benedict commented on WFLY-3282: ------------------------------------- My apologies. I did not realize your documentation is editable by end users. You can either close this as invalid or I can resolve it when finished editing -- your choice, please. > Remote EJB invocations needs corrected ports and protocol > --------------------------------------------------------- > > Key: WFLY-3282 > URL: https://issues.jboss.org/browse/WFLY-3282 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.1.0.CR1 > Reporter: Paul Benedict > Assignee: Tom Wells > Priority: Minor > Labels: jndi, remoting > > This page needs updating. > 1) It refers to old "remote" protocol but WildFly only supports "http-remoting" through HTTP Upgrade. > 2) All links to other pages point to AS71 not WFLY8. > https://docs.jboss.org/author/display/WFLY8/Remote+EJB+invocations+via+JN... -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3283) Upgrade Generic JMS RA to 1.0.5.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3283: ----------------------------------------------- Jeff Mesnil <jmesnil(a)redhat.com> changed the Status of [bug 1090961|https://bugzilla.redhat.com/show_bug.cgi?id=1090961] from NEW to POST > Upgrade Generic JMS RA to 1.0.5.Final > ------------------------------------- > > Key: WFLY-3283 > URL: https://issues.jboss.org/browse/WFLY-3283 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.1.0.CR1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- 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

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2014