January 2012 - jboss-jira - Jboss List Archives

[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

14 years, 4 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

14 years, 4 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

14 years, 4 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

14 years, 4 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

14 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JASSIST-96) Publish javassist to Maven central

by Pete Muir (JIRA)

Publish javassist to Maven central ---------------------------------- Key: JASSIST-96 URL: https://jira.jboss.org/jira/browse/JASSIST-96 Project: Javassist Issue Type: Task Reporter: Pete Muir It would be nice if Javassist were published to Maven central regularly -- 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

14 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (AS7-1749) CLI usability: disconnect can take up to several seconds

by Radoslav Husar (JIRA)

CLI usability: disconnect can take up to several seconds -------------------------------------------------------- Key: AS7-1749 URL: https://issues.jboss.org/browse/AS7-1749 Project: Application Server 7 Issue Type: Enhancement Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Alexey Loubyansky Priority: Minor CTRL+D / disconnect sometimes takes up to 3-4 seconds to finish; making it seem as the console is stuck. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] (AS7-2342) Multiple Log Directories in one tree

by Jim Tyrrell (Created) (JIRA)

Multiple Log Directories in one tree ------------------------------------ Key: AS7-2342 URL: https://issues.jboss.org/browse/AS7-2342 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell See the attached screen shot, does it make sense to have the log files in each of the server/s directories, along with the log directory in the domain context. When first looking for log files, it was odd to cd to domain, and then cd to log and not see my server directories. For a long time JBoss user what we are doing does not probably hurt that much, but for a new user, having multiple log directories is a little odd. Does it make sense to have just one log directory. In this case: domain/log/server-one domain/log/server-two ... instead of domina/log domain/servers/server-one/log domain/servers/server-two/log ... -- 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

14 years, 4 months

6
6
0 / 0

[JBoss JIRA] Created: (JBAS-4526) JBossMQ UIL2 Read/Write Tasks should not be doing initialization

by Adrian Brock (JIRA)

JBossMQ UIL2 Read/Write Tasks should not be doing initialization ---------------------------------------------------------------- Key: JBAS-4526 URL: http://jira.jboss.com/jira/browse/JBAS-4526 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 Read/Write tasks both do their stream initialization when each thread starts. This code needs changing such that the streams are allocated before started the threads. Only if all resources can be succesfully allocated should we start the threads. -- 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

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] (AS7-3408) Classloading issue with HornetQLoggerFactory - possilbe problem with failback

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3408: ----------------------------------- Summary: Classloading issue with HornetQLoggerFactory - possilbe problem with failback Key: AS7-3408 URL: https://issues.jboss.org/browse/AS7-3408 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Andy Taylor Priority: Critical Fix For: 7.1.0.Final Attachments: console-log-backup-server.txt, console-log-live-server.txt, reproducer.zip Test scenario: 1. Start two servers AS7/EAP6 servers - live and its backup in dedicated topology - each on different machine 2. Kill live server using "kill -9 ..." 3. Start live server again In step 3. there are unexpected messages in console log of live and backup server. >From backup server: {code} 12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [17700d86-45b2-11e1-a575-d48564b8e1e7] stopped 12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) unable to restart server, please kill and restart manually: java.lang.IllegalArgumentException: Could not find class org.jboss.as.messaging.HornetQLoggerFactory at org.hornetq.utils.ClassloadingUtil$1.run(ClassloadingUtil.java:42) [hornetq-core-2.2.7.Final.jar:] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_22] at org.hornetq.utils.ClassloadingUtil.safeInitNewInstance(ClassloadingUtil.java:16) [hornetq-core-2.2.7.Final.jar:] at org.hornetq.core.server.impl.HornetQServerImpl.instantiateInstance(HornetQServerImpl.java:1868) [hornetq-core-2.2.7.Final.jar:] at org.hornetq.core.server.impl.HornetQServerImpl.initialiseLogging(HornetQServerImpl.java:1301) [hornetq-core-2.2.7.Final.jar:] at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:541) [hornetq-core-2.2.7.Final.jar:] at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation$1FailbackChecker$1.run(HornetQServerImpl.java:430) [hornetq-core-2.2.7.Final.jar:] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] {code} >From live server: {code} 12:07:51,993 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test 12:07:52,007 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 31092ms - Started 155 of 263 services (103 services are passive or on-demand) 12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 1 12:07:53,292 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber} 12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4 12:07:53,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup configured now! 12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 2 12:07:55,293 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber} 12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4 12:07:55,294 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup {code} I'm not fully sure but it looks like that backup server did not manage to get to "waiting for live to fail" state and live server is not able to detect it. There is set "DEBUG" level logging for "org.hornetq" in attached logs. I've attached reproducer.zip - steps to use: 1. Download and unzip "reproducer.zip" 2. Prepare live and backup server - "sh prepare.sh" 3. Start live - "sh start-server1.sh server1_hostname" 4. Start backup - "sh start-server2.sh server2_hostname" 5. Kill live server using "kill -9 server1_process_id" 6. Start live server again - "sh start-server1.sh server1_hostname" Note: In reproducer.zip are configuration files standalone-ha-A.xml, standalone-ha-B.xml (A for live, B for backup). -- 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

14 years, 4 months

2
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012