December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6169) CLI does not work on windows

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6169: -------------------------------- Summary: CLI does not work on windows Key: AS7-6169 URL: https://issues.jboss.org/browse/AS7-6169 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.2.0.Alpha1 Environment: Windows 7, Windows 8, Windows Server 2008r2 Reporter: Tomaz Cerar Assignee: Alexey Loubyansky Priority: Critical Typing in CLI crashes with error below after any character is entered {noformat} [standalone@localhost:9999 /] ajava.lang.ArithmeticException: / by zero at org.jboss.aesh.console.Console.writeChar(Console.java:752) at org.jboss.aesh.console.Console.writeChars(Console.java:735) at org.jboss.aesh.console.Console.parseOperation(Console.java:432) at org.jboss.aesh.console.Console.read(Console.java:377) at org.jboss.aesh.console.Console.read(Console.java:331) at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171) at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1167) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259) 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:270) at org.jboss.modules.Main.main(Main.java:294) {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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-1833: --------------------------------------- I changed the schedule on this, although at this point it's not certain to make 7.2. > CLI usability: operations that shutdown the server-side management interface result in "Communication error" > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-1833 > URL: https://issues.jboss.org/browse/AS7-1833 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Affects Versions: 7.0.0.Final, 7.0.1.Final > Reporter: Radoslav Husar > Assignee: Alexey Loubyansky > Priority: Critical > Labels: eap6-ux > Fix For: 7.2.0.CR1 > > > If you shutdown the server, you get an error: > {code} > [standalone@localhost:9999 /] :shutdown > Communication error: Channel closed > Closed connection to localhost:9999 > {code} > Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH. > The same basic issue exists for the :reload operation. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-713) When you configure timeout on PicketBox the application will raise IllegalStateException

by Bruno Oliveira (JIRA)

[ https://issues.jboss.org/browse/SECURITY-713?page=com.atlassian.jira.plug... ] Bruno Oliveira updated SECURITY-713: ------------------------------------ Description: When timeout is configured on PicketBox, an java.lang.IllegalStateException will be raised. Details in this URL: https://gist.github.com/d61102567f79d76c0ba4 Current timed release: 5.0.0-2012Nov26 was: When timeout is configured on PicketBox, an java.lang.IllegalStateException will be raised. Details in this URL: https://gist.github.com/d61102567f79d76c0ba4 > When you configure timeout on PicketBox the application will raise IllegalStateException > ---------------------------------------------------------------------------------------- > > Key: SECURITY-713 > URL: https://issues.jboss.org/browse/SECURITY-713 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Picketbox5 > Affects Versions: Picketbox_v5.0.0.Alpha > Reporter: Bruno Oliveira > Assignee: Anil Saldhana > Fix For: Picketbox_v5.0.0.Alpha > > > When timeout is configured on PicketBox, an java.lang.IllegalStateException will be raised. > Details in this URL: https://gist.github.com/d61102567f79d76c0ba4 > Current timed release: 5.0.0-2012Nov26 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-713) When you configure timeout on PicketBox the application will raise IllegalStateException

by Bruno Oliveira (JIRA)

Bruno Oliveira created SECURITY-713: --------------------------------------- Summary: When you configure timeout on PicketBox the application will raise IllegalStateException Key: SECURITY-713 URL: https://issues.jboss.org/browse/SECURITY-713 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: Picketbox5 Affects Versions: Picketbox_v5.0.0.Alpha Reporter: Bruno Oliveira Assignee: Anil Saldhana Fix For: Picketbox_v5.0.0.Alpha When timeout is configured on PicketBox, an java.lang.IllegalStateException will be raised. Details in this URL: https://gist.github.com/d61102567f79d76c0ba4 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4283) File cache store location used by ROOT.war overlaps with location for other contexts

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-4283?page=com.atlassian.jira.plugin.s... ] Dennis Reed updated AS7-4283: ----------------------------- Workaround Description: One of the following: - Name the war ROOT.war - Set the context root to "ROOT" instead of "" or "/" - Add a new cache configuration for use by the root context that uses a unique file-store path was:Requires adding a new cache configuration for use by the root context that uses a unique file-store path. > File cache store location used by ROOT.war overlaps with location for other contexts > ------------------------------------------------------------------------------------ > > Key: AS7-4283 > URL: https://issues.jboss.org/browse/AS7-4283 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 7.1.2.Final (EAP) > > > The simplest fix is to use "ROOT" as the context path when constructing the cache name. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4283) File cache store location used by ROOT.war overlaps with location for other contexts

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/AS7-4283?page=com.atlassian.jira.plugin.s... ] Dennis Reed reopened AS7-4283: ------------------------------ Reopening since fix did not make it into 7.1.2 (it appears to have been overwritten by a later commit for AS7-4612). > File cache store location used by ROOT.war overlaps with location for other contexts > ------------------------------------------------------------------------------------ > > Key: AS7-4283 > URL: https://issues.jboss.org/browse/AS7-4283 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 7.1.2.Final (EAP) > > > The simplest fix is to use "ROOT" as the context path when constructing the cache name. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate 4.1.9.Final

by Scott Marlow (JIRA)

Scott Marlow created AS7-6168: --------------------------------- Summary: component upgrade to Hibernate 4.1.9.Final Key: AS7-6168 URL: https://issues.jboss.org/browse/AS7-6168 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6092) Allow the CLI to deploy maven projects

by Nicholas DiPiazza (JIRA)

[ https://issues.jboss.org/browse/AS7-6092?page=com.atlassian.jira.plugin.s... ] Nicholas DiPiazza updated AS7-6092: ----------------------------------- Summary: Allow the CLI to deploy maven projects (was: Allow deployment of exploded or unexploded maven projects directly.) Git Pull Request: https://github.com/jbossas/jboss-as/pull/3655 Affects Version/s: 7.1.2.Final (EAP) (was: 7.1.1.Final) Description: Allow users to deploy Maven projects directly from the CLI. Create a new command "mavendeploy" This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler. First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact). Examples: [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install" was: Allow users to deploy Maven projects directly. In order to use this, must create Maven Settings configuration menu in jboss as7 console / properties files. Property settable from CLI. Deployments allowed of type: mavendeploy-mvn.xml <mavendeploy> |--- <pomLocation> |--- <scm> -- @scmhost, @port, @username, @password |--- <dir> -- @pomXmlFilePath |--- <target> -- @artifactId |--- <mavenOps> -- list of ops When jboss sees this it automatially: 0) if scm, checkout to {configuration}/data/mvn/scmco/ 1) mvn install project using opts specified {configuration}/data/mvn/{project}/target 2) deploy resource that maven just installed to target. 2) > Allow the CLI to deploy maven projects > -------------------------------------- > > Key: AS7-6092 > URL: https://issues.jboss.org/browse/AS7-6092 > Project: Application Server 7 > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.2.Final (EAP) > Reporter: Nicholas DiPiazza > Assignee: Jason Greene > > Allow users to deploy Maven projects directly from the CLI. > Create a new command "mavendeploy" > This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler. > First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact). > Examples: > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6092) Allow the CLI to deploy maven projects

by Nicholas DiPiazza (JIRA)

[ https://issues.jboss.org/browse/AS7-6092?page=com.atlassian.jira.plugin.s... ] Nicholas DiPiazza commented on AS7-6092: ---------------------------------------- Created a Pull request https://github.com/jbossas/jboss-as/pull/3655 on 12:21pm CST, Dec 13, 2012. > Allow the CLI to deploy maven projects > -------------------------------------- > > Key: AS7-6092 > URL: https://issues.jboss.org/browse/AS7-6092 > Project: Application Server 7 > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.2.Final (EAP) > Reporter: Nicholas DiPiazza > Assignee: Jason Greene > > Allow users to deploy Maven projects directly from the CLI. > Create a new command "mavendeploy" > This will take a pom.xml for a war, ear or ejb project and will maven build, then deploy to the server using the DeployHandler. > First iteration of this would take same parameters as "deploy" except for one, --goals that specifies what goals to build the project with before deploying. (this makes it so you can clean before install, or just install, or call whatever goal that is needed to build the artifact). > Examples: > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml > [standalone@localhost:9999 /] mavendeploy C:\workspace\test-webapp\pom.xml --goals="clean install" -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6161) Internet Explorer support verification

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6161?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6161: ---------------------------------- Looking at the market share of IE7 (2-4%), we'll support it on a best effort basis, but nothing more. > Internet Explorer support verification > -------------------------------------- > > Key: AS7-6161 > URL: https://issues.jboss.org/browse/AS7-6161 > Project: Application Server 7 > Issue Type: Task > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > With the upcoming 1.5.0 release we need to review the IE support. This is an umbrella issue for collecting issues that have been discovered -- 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

11 years, 9 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 December 2012