February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2408) Virtual Machine status does not work in domain with remote hosts

by Kevin Barfield (Created) (JIRA)

Virtual Machine status does not work in domain with remote hosts ---------------------------------------------------------------- Key: AS7-2408 URL: https://issues.jboss.org/browse/AS7-2408 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Kevin Barfield Assignee: Heiko Braun There is a domain with a remote host controller (separate physical server/laptop). Try to go to Virtual Machine Status when looking at the remote host in the web console - error messages show in the UI. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8966) Seam 2 Reexplode causes full undeploy + deploy on AS6

by Cody Lerum (JIRA)

Seam 2 Reexplode causes full undeploy + deploy on AS6 ----------------------------------------------------- Key: JBAS-8966 URL: https://issues.jboss.org/browse/JBAS-8966 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: JBoss AS 6 Final, Seam 2.2.1 Reporter: Cody Lerum After upgrading an existing seam 2 project which runs on AS 4.2.3 to run on AS 6 I'm seeing an issue where if I run an reexplode from the seam-gen ant build the application server does a full undeploy and then deploy of the app. This kills any development as I should be able to edit an jsf xhtml page and have that reflected immediately without having to redeploy. Appears the redeploy scanner is too aggressive or seam-gen is copying over something that worked for reexplode in AS4 but not in AS6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3309) unify configuration path element usage in the web subsystem

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-3309: ---------------------------------------- Summary: unify configuration path element usage in the web subsystem Key: AS7-3309 URL: https://issues.jboss.org/browse/AS7-3309 Project: Application Server 7 Issue Type: Task Components: Web Affects Versions: 7.1.0.CR1, 7.0.0.Final Reporter: Emanuel Muckenhuber Assignee: Jean-Frederic Clere Fix For: 7.1.0.Final There are some inconsistent usages of the configuration=jsp vs. ssl=configuration elements in the web subsystem. Those (and most likely further) usages need to get identified and aligned to use configuration=* -- 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, 2 months

5
7
0 / 0

[JBoss JIRA] (JBAS-9454) Can not retrive timer from timerHandle stored in application db

by Sarang Anajwala (Created) (JIRA)

Can not retrive timer from timerHandle stored in application db --------------------------------------------------------------- Key: JBAS-9454 URL: https://issues.jboss.org/browse/JBAS-9454 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.1.0 Environment: default datastore mysql Reporter: Sarang Anajwala We are persisting timerHandle object obtained while creating timers, in our application db so that we can use this handle later on to retrieve timer object and cancel the timer. However, when I try to retrieve the timer from this timerHandle object (after retrieving it from our application db), I am getting following error. (pool-11-thread-10) Unknown Exception: : javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1215) [:3.6.6.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1148) [:3.6.6.Final] at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:255) [:3.6.6.Final] at org.jboss.ejb3.timerservice.mk2.TimerServiceImpl.getPersistedTimer(TimerServiceImpl.java:951) [:1.0.0-alpha-13] at org.jboss.ejb3.timerservice.mk2.TimerServiceImpl.getTimer(TimerServiceImpl.java:530) [:1.0.0-alpha-13] at org.jboss.ejb3.timerservice.mk2.TimerHandleImpl.getTimer(TimerHandleImpl.java:107) [:1.0.0-alpha-13] -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2385) A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution

by Geoffrey De Smet (JIRA)

A BestSolutionChangedEvent should be fired when a StartingSolutionInitializer generates a new best solution ----------------------------------------------------------------------------------------------------------- Key: JBRULES-2385 URL: https://jira.jboss.org/jira/browse/JBRULES-2385 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet try examination example with exam set 2: after initialization the score in the dialog is stale -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-541) Thread pools in transport protocols not using daemon threads

by Paul Ferraro (JIRA)

Thread pools in transport protocols not using daemon threads ------------------------------------------------------------ Key: JGRP-541 URL: http://jira.jboss.com/jira/browse/JGRP-541 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Reporter: Paul Ferraro Assigned To: Bela Ban Priority: Minor The ThreadFactory used by the ThreadPoolExecutors (for both regular and OOB messages) in org.jgroups.protocols.TP does not create daemon threads. During runtime the JVM will resist exiting unless the channel is explicitly shutdown. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] (AS7-3020) Define and use different JDBC driver versions as modules

by Michael Voegele (Created) (JIRA)

Define and use different JDBC driver versions as modules -------------------------------------------------------- Key: AS7-3020 URL: https://issues.jboss.org/browse/AS7-3020 Project: Application Server 7 Issue Type: Bug Components: Documentation, Server Affects Versions: 7.1.0.Beta1b Reporter: Michael Voegele Assignee: Jason Greene When defining a JDBC driver as module and providing two versions as follows: JBOSS_HOME/modules/com/microsoft/sqlserver/main/ JBOSS_HOME/modules/com/microsoft/sqlserver/2.0/ with according jar and module.xml and defining the driver as follows in standalone.xml: <driver name="mssql" module="com.microsoft.sqlserver" major-version="2" minor-version="0"> <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class> </driver> the following error is thrown: 15:53:32,805 ERROR [org.jboss.as.controller] (ServerService Thread Pool -- 25) -> JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("jdbc-driver" => "mssql") ]): java.lang.IllegalStateException: JBAS010435: Specified driver version doesn't match with actual driver version When debugging class JdbcDriverAdd, the slot main is always used. I also tried to configure the driver as: <driver name="mssql" module="com.microsoft.sqlserver" slot="2.0"> or <driver name="mssql" module="com.microsoft.sqlserver:2.0"> but this does not work and is also not foreseen as from the scheme. Also, there is no documentation of how to use major- and minor-version, only the following can be seen in the xsd: Specifies the major/minor version of this driver. If the major and minor version is omitted the fist available Driver in module will be used. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (AS7-901) Figure out why the JPDA remote debugger crashes in domain mode

by Heiko Braun (JIRA)

Figure out why the JPDA remote debugger crashes in domain mode -------------------------------------------------------------- Key: AS7-901 URL: https://issues.jboss.org/browse/AS7-901 Project: Application Server 7 Issue Type: Task Reporter: Heiko Braun -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] (AS7-3511) logmodule on command line causes error in tools

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created AS7-3511: ---------------------------------------- Summary: logmodule on command line causes error in tools Key: AS7-3511 URL: https://issues.jboss.org/browse/AS7-3511 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Final Reporter: Max Rydahl Andersen Assignee: Jason Greene Priority: Critical jboss modules fails to start if you pass the previously required -logmodule option. Invalid option '-logmodule' this will break any tools that works with AS7.0-7.1CR1 by launching via jboss modules instead of the startup script. Please consider ignoring this option (possibly print out a warning) instead of failing hard. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-3701) Deadlock in ServerImpl - inconsistent state

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3701: --------------------------------- Summary: Deadlock in ServerImpl - inconsistent state Key: AS7-3701 URL: https://issues.jboss.org/browse/AS7-3701 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Environment: Sun JDK 1.6.26 Linux 32-bit Reporter: Ondrej Zizka Assignee: Jason Greene Server gets stuck when ServerImpl gets somehow into an inconsistent state, and fails assertion in ServerImpl#responseCompleted(). See the attached files for details. Reproducible in org.jboss.as.test.smoke.surefire.servermodule.HttpDeploymentUploadUnitTestCase using commit https://github.com/OndraZizka/jboss-as/commit/115acf6c7c78cc8971c81861974... {code} 18:16:53,776 INFO [org.jboss.as.repository] (management-handler-threads - 3) JBAS014900: Content added at location /home/ondra/work/AS7/ozizka-as7/testsuite/integration/smoke/target/jbossas/standalone/data/content/38/755f0faae6d5ee656ccc5b64c6492c95143256/content 18:16:53,778 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "please-the-arquillian-gods.jar" 18:16:53,788 INFO [org.jboss.as.server] (management-handler-threads - 3) JBAS018559: Deployed "please-the-arquillian-gods.jar" No resources for servermodule/test-http-deployment.sar 18:16:53,813 ERROR [stderr] (Thread-75) Exception in thread "Thread-75" java.lang.AssertionError 18:16:53,813 ERROR [stderr] (Thread-75) at org.jboss.sun.net.httpserver.ServerImpl.responseCompleted(ServerImpl.java:830) 18:16:53,814 ERROR [stderr] (Thread-75) at org.jboss.sun.net.httpserver.ServerImpl$Dispatcher.handleEvent(ServerImpl.java:325) 18:16:53,814 ERROR [stderr] (Thread-75) at org.jboss.sun.net.httpserver.ServerImpl$Dispatcher.run(ServerImpl.java:392) 18:16:53,814 ERROR [stderr] (Thread-75) at java.lang.Thread.run(Thread.java:662) {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, 2 months

3
9
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 February 2012