March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4000) CLONE - bin/standalone.sh --help says '----server-config=<config> ...'

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-4000: -------------------------------------- Summary: CLONE - bin/standalone.sh --help says '----server-config=<config> ...' Key: AS7-4000 URL: https://issues.jboss.org/browse/AS7-4000 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Reporter: Rostislav Svoboda Assignee: Paul Gier Fix For: 7.1.1.Final This typo is present in upstream too, it should contain dash only twice not four times. {code} ----server-config=<config> Name of the server configuration file to use (default is "standalone.xml") {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3994) CLONE - Can't connect CLI to server on IPv6 address

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3994?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-3994: ------------------------------------- Assignee: Brian Stansberry (was: Alexey Loubyansky) > CLONE - Can't connect CLI to server on IPv6 address > --------------------------------------------------- > > Key: AS7-3994 > URL: https://issues.jboss.org/browse/AS7-3994 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.0.Final > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Critical > Labels: eap6_LA > Fix For: 7.1.1.Final > > > Server started with: > {code} > bin/standalone.sh -b=::1 -bmanagement=::1 -Djava.net.preferIPv4Stack=false > {code} > CLI execution attempts: > {code} > $ bin/jboss-cli.sh --connect command=:shutdown > The controller is not available at localhost:9999 > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > $ bin/jboss-cli.sh --connect controller=::1 command=:shutdown > The port must be a valid non-negative integer: 'controller=::1' > $ bin/jboss-cli.sh --connect controller=[::1] command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]' > $ netstat -natup | grep java > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp 0 0 ::1:9990 :::* LISTEN 21912/java > tcp 0 0 ::1:9999 :::* LISTEN 21912/java > tcp 0 0 ::1:8080 :::* LISTEN 21912/java > tcp 0 0 ::1:4447 :::* LISTEN 21912/java > $ bin/jboss-cli.sh --connect controller=[::1]:9999 command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]:9999' > $ bin/jboss-cli.sh --connect controller=[::1]#9999 command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]#9999' > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3997) Jacorb subsystem uses magic socket binding names

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3997: ------------------------------------- Summary: Jacorb subsystem uses magic socket binding names Key: AS7-3997 URL: https://issues.jboss.org/browse/AS7-3997 Project: Application Server 7 Issue Type: Bug Components: IIOP Affects Versions: 7.1.0.Final Reporter: Brian Stansberry Assignee: Stefan Guilhen In JacORBSubsystemAdd: CorbaORBService orbService = new CorbaORBService(props); final ServiceBuilder<ORB> builder = context.getServiceTarget().addService( CorbaORBService.SERVICE_NAME, orbService); // inject the socket bindings that specify the JacORB IIOP and IIOP/SSL ports. builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SOCKET_BINDING), SocketBinding.class, orbService.getJacORBSocketBindingInjector()); builder.addDependency(SocketBinding.JBOSS_BINDING_NAME.append(JACORB_SSL_SOCKET_BINDING), SocketBinding.class, orbService.getJacORBSSLSocketBindingInjector()); The JACORB_SOCKET_BINDING and JACORB_SSL_SOCKET_BINDING values should be coming from some configuration attributes, which perhaps have those constants as their default values. Users can name socket-binding configs whatever they want; the names we provide in our standard configs are just obvious defaults. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-152) instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null

by Yanic Inghelbrecht (JIRA)

Yanic Inghelbrecht created JASSIST-152: ------------------------------------------ Summary: instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null Key: JASSIST-152 URL: https://issues.jboss.org/browse/JASSIST-152 Project: Javassist Issue Type: Bug Affects Versions: 3.15.0-GA Environment: Any Reporter: Yanic Inghelbrecht Assignee: Shigeru Chiba When trying to instrument the attached org.hibernate.cfg.AbstractPropertyHolder (copied from the hibernate 4.0.1 final distribution), instrumentation fails with the following exception : java.lang.RuntimeException: fatal error: at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:177) at javassist.bytecode.stackmap.MapMaker.fillStackMap(MapMaker.java:410) at javassist.bytecode.stackmap.MapMaker.toStackMapBody(MapMaker.java:393) at javassist.bytecode.stackmap.MapMaker.toStackMap(MapMaker.java:323) at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:98) at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:417) at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:399) at javassist.expr.ExprEditor.doit(ExprEditor.java:113) at javassist.CtBehavior.instrument(CtBehavior.java:672) at test_abstractpropertyholder.SimpleTranslator.modify(SimpleTranslator.java:25) at test_abstractpropertyholder.SimpleTranslator.onLoad(SimpleTranslator.java:19) at test_abstractpropertyholder.JavassistInstrumenter.getInstrumentedClass(JavassistInstrumenter.java:21) at test_abstractpropertyholder.Main.main(Main.java:32)transforming org.hibernate.cfg.AbstractPropertyHolder Caused by: javassist.bytecode.BadBytecode: bad array type for AALOAD: null at javassist.bytecode.stackmap.TypeData$ArrayElement.getName(TypeData.java:422) at javassist.bytecode.stackmap.TypeData$TypeName.getExpected(TypeData.java:292) at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:175) ... 12 more -- 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

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (AS7-3994) CLONE - Can't connect CLI to server on IPv6 address

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3994?page=com.atlassian.jira.plugin.s... ] Brian Stansberry moved JBPAPP-8324 to AS7-3994: ----------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3994 (was: JBPAPP-8324) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.Final (was: EAP 6.0.0 ER 2) Component/s: CLI (was: Scripts and Commands) Security: (was: Public) Fix Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 3) Docs QE Status: (was: NEW) > CLONE - Can't connect CLI to server on IPv6 address > --------------------------------------------------- > > Key: AS7-3994 > URL: https://issues.jboss.org/browse/AS7-3994 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.0.Final > Reporter: Rostislav Svoboda > Assignee: Alexey Loubyansky > Priority: Blocker > Labels: eap6_LA > Fix For: 7.1.1.Final > > > Server started with: > {code} > bin/standalone.sh -b=::1 -bmanagement=::1 -Djava.net.preferIPv4Stack=false > {code} > CLI execution attempts: > {code} > $ bin/jboss-cli.sh --connect command=:shutdown > The controller is not available at localhost:9999 > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > $ bin/jboss-cli.sh --connect controller=::1 command=:shutdown > The port must be a valid non-negative integer: 'controller=::1' > $ bin/jboss-cli.sh --connect controller=[::1] command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]' > $ netstat -natup | grep java > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp 0 0 ::1:9990 :::* LISTEN 21912/java > tcp 0 0 ::1:9999 :::* LISTEN 21912/java > tcp 0 0 ::1:8080 :::* LISTEN 21912/java > tcp 0 0 ::1:4447 :::* LISTEN 21912/java > $ bin/jboss-cli.sh --connect controller=[::1]:9999 command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]:9999' > $ bin/jboss-cli.sh --connect controller=[::1]#9999 command=:shutdown > The port must be a valid non-negative integer: 'controller=[::1]#9999' > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3910) How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS

by Mustafa Khambatta (JIRA)

Mustafa Khambatta created AS7-3910: -------------------------------------- Summary: How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS Key: AS7-3910 URL: https://issues.jboss.org/browse/AS7-3910 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: 7.1.0.Final Environment: Windows 2003 EE OS 32bit 4GB RAM Reporter: Mustafa Khambatta Assignee: Paul Ferraro Fix For: No Release I am unable to find any information on creating server instances on windows OS for JBoss AS7.1.0. I have tried the other ways mentioned but nothing. The admin console doesnot have any function of creating a server instance and I cant find any instruction for doing it through command prompt. Also after creating the server instances how to you create the cluster and what are the steps for it. Then after that, what is the steps for creating a High Availability clustering Thankyou in advance Appreciate your help -- 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

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-3988) ClassNotFoundException org.slf4j thrown from module org.jboss.logging

by Tanya Ruttenberg (JIRA)

Tanya Ruttenberg created AS7-3988: ------------------------------------- Summary: ClassNotFoundException org.slf4j thrown from module org.jboss.logging Key: AS7-3988 URL: https://issues.jboss.org/browse/AS7-3988 Project: Application Server 7 Issue Type: Bug Components: Class Loading, Logging Affects Versions: 7.1.0.Final Environment: Windows Vista Reporter: Tanya Ruttenberg Assignee: David Lloyd I created the kitchensink quickstart from jboss tools. When I deployed it I got a raft of ClassNotFound errors refering to classes in org.slf4j. I tried to fix it by adding this module to maven, to jboss-deployment-structure.xml, the WEB-INF/lib, Manifest.MF classpath, everything I could think of. The only thing that fixed this very annoying error was to add org.slf4j to the org.jboss.logging module.xml as a dependent. -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-3980) Default subsystem not loaded

by Heiko Braun (JIRA)

Heiko Braun created AS7-3980: -------------------------------- Summary: Default subsystem not loaded Key: AS7-3980 URL: https://issues.jboss.org/browse/AS7-3980 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.1.Final on safari 4.0.5: http://localhost:9990/console/App.html#profiles -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-3991) bin/standalone.sh --help says '----server-config=<config> ...'

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-3991?page=com.atlassian.jira.plugin.s... ] Paul Gier moved JBPAPP-8261 to AS7-3991: ---------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3991 (was: JBPAPP-8261) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.Final (was: EAP 6.0.0 ER 1) Security: (was: Public) Fix Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 3) Docs QE Status: (was: NEW) > bin/standalone.sh --help says '----server-config=<config> ...' > --------------------------------------------------------------- > > Key: AS7-3991 > URL: https://issues.jboss.org/browse/AS7-3991 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.Final > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Fix For: 7.1.1.Final > > > This typo is present in upstream too, it should contain dash only twice not four times. > {code} > ----server-config=<config> Name of the server configuration file > to use (default is "standalone.xml") > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3991) bin/standalone.sh --help says '----server-config=<config> ...'

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-3991?page=com.atlassian.jira.plugin.s... ] Paul Gier reassigned AS7-3991: ------------------------------ Assignee: Paul Gier (was: Brian Stansberry) > bin/standalone.sh --help says '----server-config=<config> ...' > --------------------------------------------------------------- > > Key: AS7-3991 > URL: https://issues.jboss.org/browse/AS7-3991 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.0.Final > Reporter: Rostislav Svoboda > Assignee: Paul Gier > Fix For: 7.1.1.Final > > > This typo is present in upstream too, it should contain dash only twice not four times. > {code} > ----server-config=<config> Name of the server configuration file > to use (default is "standalone.xml") > {code} -- 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

12 years, 1 month

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 March 2012