January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3333) Admin console should not require "max threads" value when creating an EJB3 thread pool

by Jan Martiska (JIRA)

Jan Martiska created AS7-3333: --------------------------------- Summary: Admin console should not require "max threads" value when creating an EJB3 thread pool Key: AS7-3333 URL: https://issues.jboss.org/browse/AS7-3333 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Fix For: 7.1.0.Final Attachments: ejb3threadpool.png The help says: "The default value if not configured is the number of processes as returned by Runtime.availableProcessors()", therefore a specific number should not be required from the user. See screenshot. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] (AS7-3410) CLONE - Classloading issue with HornetQLoggerFactory - problem with failback

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3410: ----------------------------------- Summary: CLONE - Classloading issue with HornetQLoggerFactory - problem with failback Key: AS7-3410 URL: https://issues.jboss.org/browse/AS7-3410 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 backup. 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3368) jboss-admin tool doesn't return non zero code when command fails to execute

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3368: -------------------------------------- Summary: jboss-admin tool doesn't return non zero code when command fails to execute Key: AS7-3368 URL: https://issues.jboss.org/browse/AS7-3368 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management, Scripts Affects Versions: 7.1.0.CR1b Reporter: Rostislav Svoboda Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.0.Final Jboss-admin tool doesn't return non zero code when command fails to execute. It's necessary for us to know if command was executed properly or not. Parsing output is unacceptable. {code} [rsvoboda@rosta-ntb ~]$ TESTING/jboss-as7/bin/jboss-admin.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. [rsvoboda@rosta-ntb ~]$ echo $? 0 {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

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3400) Description for replace-deployment shows deploy

by Erhard Siegl (JIRA)

Erhard Siegl created AS7-3400: --------------------------------- Summary: Description for replace-deployment shows deploy Key: AS7-3400 URL: https://issues.jboss.org/browse/AS7-3400 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Affects Versions: 7.1.0.CR1b Reporter: Erhard Siegl Assignee: Thomas Diesler In jboss-admin: [domain@localhost:9999 server-group=other-server-group] :read-operation-description(name="replace-deployment") { "outcome" => "success", "result" => { "operation-name" => "deploy", "description" => "Deploy the specified deployment content into the runtime, optionally replacing existing content.", "reply-properties" => {}, "read-only" => false } } This is the description for the "deploy" operation and not for "replace-deployment". -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3210) Apache Tomcat SingleSignonValve not being invoked

by Luis Barreiro (Created) (JIRA)

Apache Tomcat SingleSignonValve not being invoked ------------------------------------------------- Key: AS7-3210 URL: https://issues.jboss.org/browse/AS7-3210 Project: Application Server 7 Issue Type: Bug Components: Security Reporter: Luis Barreiro Assignee: Anil Saldhana Despite having org.apache.catalina.authenticator.SingleSignOn valve defined in jboss-web.xml and <sso> element present in virtual-host configuration, there is no invocation of the valve, neither a JSESSIONIDSSO cookie is present in responses. The valve is present in the pipeline, but the following line appears in the server log: [org.apache.catalina.authenticator.AuthenticatorBase] (MSC service thread 1-2) No SingleSignOn Valve is present Testcase available at https://github.com/barreiro/jboss-as/tree/JBQA-5281/testsuite/integration... -- 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, 3 months

6
6
0 / 0

[JBoss JIRA] (AS7-3391) org.apache.felix.framework.util.VersionRange in both jbosgi-resolver-felix-1.0.10.jar , org.apache.felix.webconsole-3.1.6.SP1.jar

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3391: --------------------------------- Summary: org.apache.felix.framework.util.VersionRange in both jbosgi-resolver-felix-1.0.10.jar , org.apache.felix.webconsole-3.1.6.SP1.jar Key: AS7-3391 URL: https://issues.jboss.org/browse/AS7-3391 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Thomas Diesler Refer to this TattleTale report: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1956) Add failover support to client-side proxies to clustered session beans.

by Paul Ferraro (JIRA)

Add failover support to client-side proxies to clustered session beans. ----------------------------------------------------------------------- Key: AS7-1956 URL: https://issues.jboss.org/browse/AS7-1956 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: 7.1.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] (AS7-3399) Upgrade jboss-metadata to 7.0.0.Beta33

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3399: --------------------------------- Summary: Upgrade jboss-metadata to 7.0.0.Beta33 Key: AS7-3399 URL: https://issues.jboss.org/browse/AS7-3399 Project: Application Server 7 Issue Type: Component Upgrade Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Priority: Blocker Fix For: 7.1.0.Final -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3373) around-timeout tag in ejb-jar.xml throws RuntimeException "around-timeout element parsing is not yet implemented"

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3373: ------------------------------------- Summary: around-timeout tag in ejb-jar.xml throws RuntimeException "around-timeout element parsing is not yet implemented" Key: AS7-3373 URL: https://issues.jboss.org/browse/AS7-3373 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Ondřej Chaloupka Assignee: Stuart Douglas In case of usage around-timeout element in ejb-jar.xml file the RuntimeException is thrown. Example of way how I wanted to use it could be found on (currently commented): https://github.com/ochaloup/jboss-as/blob/JBQA-5273-test-interceptors/tes... -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3263) Upgrade to resteasy 2.3.1

by Bill Burke (Created) (JIRA)

Upgrade to resteasy 2.3.1 ------------------------- Key: AS7-3263 URL: https://issues.jboss.org/browse/AS7-3263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.1.0.CR1, 7.1.0.Final Reporter: Bill Burke Fix For: 7.1.0.Final There's a couple of blocker bugs for resteasy that need to be in 7.1 2.3.1 Resteasy should be out this week. -- 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, 3 months

3
2
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