January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2800) JMX via JNDI not working

by Savas Ali Tokmen (Created) (JIRA)

JMX via JNDI not working ------------------------ Key: AS7-2800 URL: https://issues.jboss.org/browse/AS7-2800 Project: Application Server 7 Issue Type: Bug Components: JMX Affects Versions: 7.1.0.Beta1 Reporter: Savas Ali Tokmen Assignee: John Bailey Fix For: 7.1.0.CR1, 7.1.0.Final The documentation on https://docs.jboss.org/author/display/AS7/JMX+subsystem+configuration as well as the testcase jmx/src/test/java/org/jboss/as/jmx/JMXSubsystemTestCase.java seems to indicate that the JMX URL service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi should be accessible via a JMX console (for example, the jconsole). When I open: {noformat} jconsole service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi {noformat} I get an error message saying: "the connection to service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi did not succeed". -- 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

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1722) dropped message WARNING on node leaving a group

by Radoslav Husar (JIRA)

dropped message WARNING on node leaving a group ----------------------------------------------- Key: AS7-1722 URL: https://issues.jboss.org/browse/AS7-1722 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro On node leaving the group there is a warning {code} 17:57:31,340 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.lifecycle.web] (Incoming-13,web,rhusar-7808) New cluster view for partition web (id: 4, delta: -1, merge: false) : [rhusar-7808] 17:57:31,340 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-13,web,rhusar-7808) ISPN000094: Received new cluster view: [rhusar-7808|4] [rhusar-7808] 17:57:31,345 WARNING [org.jgroups.protocols.pbcast.NAKACK] (Incoming-15,web,rhusar-7808) rhusar-7808: dropped message from rhusar-41106 (not in table [rhusar-7808]), view=[rhusar-7808|4] [rhusar-7808] {code} because it removes the member before receiving the last message {code} 17:57:31,286 INFO [org.jboss.as.clustering.infinispan.subsystem] Stopped repl cache from web container 17:57:31,290 INFO [jacorb.orb] prepare ORB for shutdown... 17:57:31,290 INFO [jacorb.orb] ORB going down... 17:57:31,305 INFO [jacorb.orb.iiop] Listener exited 17:57:31,310 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000080: Disconnecting and closing JGroups Channel 17:57:31,312 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [8ee2c584-d740-11e0-ad66-0022fabb0b50] stopped 17:57:31,310 INFO [jacorb.orb] ORB shutdown complete 17:57:31,313 INFO [jacorb.orb] ORB run, exit 17:57:31,349 INFO [org.jboss.as.server.deployment] Stopped deployment SessionTest-2.0-SNAPSHOT.war in 197ms 17:57:31,636 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher 17:57:31,637 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService 17:57:31,638 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
3
0 / 0

[JBoss JIRA] (AS7-2407) Cannot connect to domain controller - more detail needed

by Kevin Barfield (Created) (JIRA)

Cannot connect to domain controller - more detail needed -------------------------------------------------------- Key: AS7-2407 URL: https://issues.jboss.org/browse/AS7-2407 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Kevin Barfield Assignee: Brian Stansberry There needs to be more detail when a host controller can't connect to a domain controller. Several times we saw the "cannot connect to the domain controller" message when we knew the two servers could see each other. The host tried 5-6 times to connect then shut down. There were no other messages on the host or domain controller with more detail (even at DEBUG logging level). We could stop the domain controller while the host was trying to connect and we would see an immediate error message on the host. -- 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
4
0 / 0

[JBoss JIRA] (AS7-2432) CLI does not allow a new security-realm to be defined within the management section of a host

by Rich Raposa (Created) (JIRA)

CLI does not allow a new security-realm to be defined within the management section of a host --------------------------------------------------------------------------------------------- Key: AS7-2432 URL: https://issues.jboss.org/browse/AS7-2432 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Rich Raposa Assignee: Alexey Loubyansky The CLI does not allow for attributes to be defined when adding a new security realm at the host=master/core-service=management level. To replicate, enter the following command in the CLI: /host=master/core-service=management/security-realm=MyDomainRealm:add() Within the add() operation I need to define an <authentication> section, but the CLI will not allow it. The message is: Operation 'add' does not expect any property. -- 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

7
15
0 / 0

[JBoss JIRA] Created: (JASSIST-44) Maven profiles for tools.jar should take account of Mac OS

by Martin Burger (JIRA)

Maven profiles for tools.jar should take account of Mac OS ---------------------------------------------------------- Key: JASSIST-44 URL: http://jira.jboss.com/jira/browse/JASSIST-44 Project: Javassist Issue Type: Bug Environment: Maven version: 2.0.8 Java version: 1.5.0_13 OS name: "mac os x" version: "10.4.11" arch: "i386" Family: "unix" Reporter: Martin Burger Assigned To: Shigeru Chiba The pom.xml uses different profiles to add the tools.jar to the dependencies. However, it is already included in the runtime for Mac OS X and some free JDKs and does not exist as a separate file 'tools.jar'. See: http://maven.apache.org/general.html#tools-jar-dependency As soon as http://jira.codehaus.org/browse/MNG-3106 gets fixed, activation should look like the following example: <activation> <jdk>1.6</jdk> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> In the meantime <profiles> <profile> <id>tools.jar</id> <activation> <property> <name>java.vendor</name> <value>Sun Microsystems Inc.</value> </property> </activation> <dependencies> <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6</version> <scope>system</scope> <optional>true</optional> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> </dependencies> </profile> </profiles> should do the job. It could be a permanent solution because the different profiles differ only in the version element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JASSIST-106) Maven build doesn't work on Mac OS X

by Pete Muir (JIRA)

Maven build doesn't work on Mac OS X ------------------------------------ Key: JASSIST-106 URL: https://jira.jboss.org/jira/browse/JASSIST-106 Project: Javassist Issue Type: Task Affects Versions: 3.11.0.GA Reporter: Pete Muir Assignee: Shigeru Chiba It references tools.jar which doesn't exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2844) Encoding problem with Flow definition files which contain german characters

by Alex Alvarez (JIRA)

Encoding problem with Flow definition files which contain german characters --------------------------------------------------------------------------- Key: JBRULES-2844 URL: https://issues.jboss.org/browse/JBRULES-2844 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow), drools-eclipse (flow) Affects Versions: 5.1.0.FINAL Reporter: Alex Alvarez Assignee: Mark Proctor The eclipse workflow plugin generates xml files with invalid encoding when german characters are used. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1545) AS build with --debug fails on OOM

by Radoslav Husar (JIRA)

AS build with --debug fails on OOM ---------------------------------- Key: AS7-1545 URL: https://issues.jboss.org/browse/AS7-1545 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor Currently build uses only 0.5G but --debug option seems to need more, works fine with 1G. I can submit a fix shortly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

7
10
0 / 0

[JBoss JIRA] (AS7-2541) TS: Clutering tests - figure out how they will be run.

by Ondrej Zizka (Created) (JIRA)

TS: Clutering tests - figure out how they will be run. ------------------------------------------------------ Key: AS7-2541 URL: https://issues.jboss.org/browse/AS7-2541 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Andrew Rubinger Fix For: 7.0.0.CR1 The current single test is not multinode - when set up as multinode, it fails. So it runs as single node, even though being in package .cluster. -- 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

11
12
0 / 0

[JBoss JIRA] (AS7-3238) Convert CMP subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert CMP subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ------------------------------------------------------------------------------ Key: AS7-3238 URL: https://issues.jboss.org/browse/AS7-3238 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: Brian Stansberry Assignee: John Bailey Fix For: 7.1.0.Final The CmpLogger and CmpMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- 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

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012