November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1801) Unable to create new profiles via the CLI

by Chris Hiner (JIRA)

Unable to create new profiles via the CLI ----------------------------------------- Key: AS7-1801 URL: https://issues.jboss.org/browse/AS7-1801 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Chris Hiner Assignee: Alexey Loubyansky Running/profile=exampleprofile:add() from the CLI gives an error message: "outcome" => "failed", "failure-description" => {"domain-failure-description" => "Failed to persist configuration change: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to marshal configuration"}, "rolled-back" => true [Host Controller] Caused by: java.lang.IllegalArgumentException [Host Controller] at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.dmr.ModelNode.keys(ModelNode.java:1085) [jboss-dmr-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.writeProfile(DomainXml.java:502) [jboss-as-controller-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console

by Andre Dietisheim (Assigned) (JIRA)

[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim reassigned JBASM-38: ------------------------------------- Assignee: Shelly McGowan (was: Rob Stryker) > shutdown the second time throw stack trace to the console > --------------------------------------------------------- > > Key: JBASM-38 > URL: https://issues.jboss.org/browse/JBASM-38 > Project: JBoss AS Server Manager > Issue Type: Enhancement > Environment: JBossAS 6.0.0.Final "Neo", Windows 7 > Reporter: Larry Chan > Assignee: Shelly McGowan > Priority: Minor > > I'm filing for my coworker who doesn't have an account here. > shutdown.bat -o 16.89.22.157 > Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu > b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE > xception: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33 > 8) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto > ry.java:248) > at org.jboss.Shutdown.main(Shutdown.java:235) > Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi. > ConnectException: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :101) > at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j > ava:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect > or.java:1886) > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j > ava:1856) > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25 > 7) > ... 2 more > Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157; > nested exception is: > java.net.ConnectException: Connection refused: connect > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198 > ) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :97) > ... 7 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at java.net.Socket.<init>(Socket.java:375) > at java.net.Socket.<init>(Socket.java:189) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect > SocketFactory.java:22) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster > SocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 12 more > Press any key to continue . . . > EXPECTED BEHAVIOR: > It is better and more standard just output message of "already shutdown". -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBASM-38) shutdown the second time throw stack trace to the console

by Andre Dietisheim (Moved) (JIRA)

[ https://issues.jboss.org/browse/JBASM-38?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim moved JBIDE-10074 to JBASM-38: ----------------------------------------------- Project: JBoss AS Server Manager (was: Tools (JBoss Tools)) Key: JBASM-38 (was: JBIDE-10074) Component/s: (was: JBossAS/Servers) > shutdown the second time throw stack trace to the console > --------------------------------------------------------- > > Key: JBASM-38 > URL: https://issues.jboss.org/browse/JBASM-38 > Project: JBoss AS Server Manager > Issue Type: Enhancement > Environment: JBossAS 6.0.0.Final "Neo", Windows 7 > Reporter: Larry Chan > Assignee: Rob Stryker > Priority: Minor > > I'm filing for my coworker who doesn't have an account here. > shutdown.bat -o 16.89.22.157 > Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu > b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE > xception: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33 > 8) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto > ry.java:248) > at org.jboss.Shutdown.main(Shutdown.java:235) > Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi. > ConnectException: Connection refused to host: 16.89.22.157; nested exception is: > java.net.ConnectException: Connection refused: connect] > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :101) > at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j > ava:185) > at javax.naming.InitialContext.lookup(InitialContext.java:392) > at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect > or.java:1886) > at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j > ava:1856) > at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25 > 7) > ... 2 more > Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157; > nested exception is: > java.net.ConnectException: Connection refused: connect > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198 > ) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) > at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java > :97) > ... 7 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at java.net.Socket.<init>(Socket.java:375) > at java.net.Socket.<init>(Socket.java:189) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect > SocketFactory.java:22) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster > SocketFactory.java:128) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) > ... 12 more > Press any key to continue . . . > EXPECTED BEHAVIOR: > It is better and more standard just output message of "already shutdown". -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2380) Decide how to distribute jars that are intended for client use only

by Thomas Diesler (Created) (JIRA)

Decide how to distribute jars that are intended for client use only ------------------------------------------------------------------- Key: AS7-2380 URL: https://issues.jboss.org/browse/AS7-2380 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.1.0.Beta1 Shelly says: One question I have, though, is the jar, jboss-as-ee-deployment-7.1.0.Alpha2-SNAPSHOT.jar, is not even part of the build. How do we ship a compliant EE implementation with JSR-88 if it is not included? I have to pick this jar up from jboss-as/ee-deployment/target -- 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, 7 months

4
5
0 / 0

[JBoss JIRA] (AS7-2361) It appears there is no external JNDI port like 1099, even though the ports are in the console

by Jim Tyrrell (Created) (JIRA)

It appears there is no external JNDI port like 1099, even though the ports are in the console --------------------------------------------------------------------------------------------- Key: AS7-2361 URL: https://issues.jboss.org/browse/AS7-2361 Project: Application Server 7 Issue Type: Feature Request Components: Naming Reporter: Jim Tyrrell Assignee: John Bailey Many many customers use client lookups of JNDI contexts to get at what used to be called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is this be design? If so, this is going to be a problem for many current customers, as they do this today. -- 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, 7 months

9
15
0 / 0

[JBoss JIRA] (AS7-2473) Need a new version of jboss-deployment-structure's XSD

by David Lloyd (Created) (JIRA)

Need a new version of jboss-deployment-structure's XSD ------------------------------------------------------ Key: AS7-2473 URL: https://issues.jboss.org/browse/AS7-2473 Project: Application Server 7 Issue Type: Task Components: Deployment Reporter: David Lloyd Assignee: Stuart Douglas Priority: Blocker Fix For: 7.1.0.Beta1 We've introduced new elements into jboss-deployment-structure. This means we need a 1.1 schema for the new stuff, while still shipping the 1.0 XSD (and parsing it of course). -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8320) Logging initialization

by Alexey Loubyansky (JIRA)

Logging initialization ---------------------- Key: JBAS-8320 URL: https://jira.jboss.org/browse/JBAS-8320 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Modules Reporter: Alexey Loubyansky Assignee: David Lloyd Fix For: 7.0.0.M1 The following exception is thrown during the start-up on windows (Sun JDK). The system property is in fact set as the error message suggests and I can successfully invoke java.util.logging.Logger logger = java.util.logging.Logger.getLogger("mylogger"); System.out.println(logger.getClass().getName() + " " + logger.getClass().getClassLoader().getClass().getName() + " " + logger.getClass().getClassLoader()); from ManagedProcess just before this.log = Logger.getLogger("org.jboss.process." + processName); (which causes the error) and output will be org.jboss.logmanager.Logger org.jboss.modules.ModuleClassLoader ClassLoader for Module "module:org.jboss.logmanager:jboss-logmanager" Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:55) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:46) at org.jboss.logging.Logger.getLogger(Logger.java:2222) at org.jboss.as.process.ManagedProcess.<init>(ManagedProcess.java:66) at org.jboss.as.process.ProcessManagerMaster.addProcess(ProcessManagerMaster.java:64) at org.jboss.as.process.ProcessManagerMaster.main(ProcessManagerMaster.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:105) at org.jboss.modules.Main.main(Main.java:169) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
13
0 / 0

[JBoss JIRA] (JBRULES-3278) Add support for DRT Files into drools-ant-task

by David Faulkner (Created) (JIRA)

Add support for DRT Files into drools-ant-task ---------------------------------------------- Key: JBRULES-3278 URL: https://issues.jboss.org/browse/JBRULES-3278 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 5.2.0.Final Environment: N/A Reporter: David Faulkner Assignee: Mark Proctor The Drools template (.drt file) functionality is not currently supported by the Ant task. -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (JBRULES-3277) Add support for DRT Files into drools-ant-task

by David Faulkner (Created) (JIRA)

Add support for DRT Files into drools-ant-task ---------------------------------------------- Key: JBRULES-3277 URL: https://issues.jboss.org/browse/JBRULES-3277 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 5.2.0.Final Environment: N/A Reporter: David Faulkner Assignee: Mark Proctor The Drools template (.drt file) functionality is not currently supported by the Ant task. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-655) ResourceAdapter level config properties are not being set

by Weston M. Price (JIRA)

ResourceAdapter level config properties are not being set --------------------------------------------------------- Key: JBJCA-655 URL: https://issues.jboss.org/browse/JBJCA-655 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.0.3.Final Environment: JBoss AS7 7.1.0.Alpha1-SNAPSHOT, built from GitHub master branch Reporter: Weston M. Price Assignee: Stefano Maestri In attempting to deploy a RA in AS7 with ResourceAdapter configuration properties, these properties do not appear to be getting set. Sample: <resource-adapters> <resource-adapter> <archive> qpid-ra-0.10.rar </archive> <config-property name="TransactionManagerLocatorClass"> org.apache.qpid.ra.tm.JBoss7TransactionManagerLocator </config-property> <config-property name="TransactionManagerLocatorMethod"> getTm </config-property> </resource-adapter> </resource-adapters> Running via a debugger never shows the setter methods being invoked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2011