May 2012 - jboss-jira - Jboss List Archives

[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

1
1
0 / 0

[JBoss JIRA] (AS7-4712) Add support of mapping between webapps and connectors

by Marcel Å ebek (JIRA)

Marcel Å ebek created AS7-4712: ---------------------------------- Summary: Add support of mapping between webapps and connectors Key: AS7-4712 URL: https://issues.jboss.org/browse/AS7-4712 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.1.Final Reporter: Marcel Å ebek Assignee: Remy Maucherat It would be nice to be able to define in web app (jboss-web.xml) which connectors may be used for accessing the application. That would allow to run several applications on several ports. Now it is just possible to do this per IP (using virtual hosts) and even that is not perfect (one may fake virtual host name in GET request and access application that he should not be able to access). -- 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

1
0
0 / 0

[JBoss JIRA] (JBJCA-815) Add WorkManager identifiers

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-815: ------------------------------------- Summary: Add WorkManager identifiers Key: JBJCA-815 URL: https://issues.jboss.org/browse/JBJCA-815 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.11.Final, 1.1.0.Alpha8 Add a name property to the WorkManager in order to get it an user visible name. Also add an id property which is unique. -- 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

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

4
7
0 / 0

[JBoss JIRA] (JBAS-9491) JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every asynchronous call

by Chris Rankin (JIRA)

Chris Rankin created JBAS-9491: ---------------------------------- Summary: JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every asynchronous call Key: JBAS-9491 URL: https://issues.jboss.org/browse/JBAS-9491 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Environment: CentOS, Windows7 Reporter: Chris Rankin Assignee: Carlo de Wolf The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as: {code:Java} @Override public boolean equals(final Object obj) { return uuid.equals(obj); } {code} This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId, Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the {{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the {{AsynchronousServerInterceptor.invoke()}} method is accumulating {{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes. -- 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
15
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

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

5
8
0 / 0

[JBoss JIRA] (AS7-4698) CLI requires wrong ssl password attribute for management security-realm server-identity=ssl add command.

by R Stokoe (JIRA)

R Stokoe created AS7-4698: ----------------------------- Summary: CLI requires wrong ssl password attribute for management security-realm server-identity=ssl add command. Key: AS7-4698 URL: https://issues.jboss.org/browse/AS7-4698 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.1.Final Reporter: R Stokoe Assignee: Alexey Loubyansky CLI requires ssl password attribute to be "keystore-password", runtime requires "password". [standalone@localhost:10299 /] /core-service=management/security-realm=ManagementRealmHttps/server-identity=ssl:add(keystore-path="security/https.keystore",password=="whatever") 'password' is not found among the supported properties: [keystore-password, protocol, keystore-path, keystore-relative-to] -- 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
11
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
1
0 / 0

[JBoss JIRA] (AS7-4222) Difference in deployment of datasource and its dependent drive in standalone mode (file-scanner and CLI/console deployment)

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-4222: ------------------------------------- Summary: Difference in deployment of datasource and its dependent drive in standalone mode (file-scanner and CLI/console deployment) Key: AS7-4222 URL: https://issues.jboss.org/browse/AS7-4222 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.1.Final Environment: New created server GIT commit d83dee45ca662fbe12b71f477884188887ce0b6a (current upstream) Reporter: Wolf-Dieter Fink Assignee: Stefano Maestri It is a difference whether the necesarry driver of a datasource is deployed from CLI/console or from the filesystem via scanner. If the driver is copied to standalone/deployments the starup failed (drive.jar.deployed state file is available). If the driver is deployed via console/CLI the startup is correct (see log excerpt) Tested with postgresql. == datasource (no other changes to standalone.xml)==== <datasource jta="false" jndi-name="java:jboss/JBTravelDatasource" pool-name="JBTravel" enabled="true" use-ccm="false"> <connection-url>jdbc:postgresql://localhost:5432/postgres</connection-url> <driver-class>org.postgresql.Driver</driver-class> <driver>postgresql-9.0-801.jar</driver> <pool> <min-pool-size>10</min-pool-size> <max-pool-size>50</max-pool-size> <prefill>true</prefill> </pool> <security> <user-name>postgres</user-name> <password>postgres</password> </security> <validation> <background-validation>false</background-validation> </validation> <statement> <share-prepared-statements>false</share-prepared-statements> </statement> </datasource> ============== log with added driver from console ======== 17:47:14,548 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /srv/eap/6.0.Beta1/standalone/deployments 17:47:14,575 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 17:47:14,733 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0) 17:47:14,755 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/JBTravelDatasource] 17:47:14,793 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "postgresql-9.0-801.jar" 17:47:14,801 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started in 2473ms - Started 157 of 231 services (72 services are passive or on-demand) ========== deployed as file to sa/deployments ==== 17:44:11,718 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 17:44:11,926 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.jdbc-driver.postgresql-9_0-801_jar (missing) dependents: [service jboss.data-source.java:jboss/JBTravelDatasource] 17:44:11,935 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.0.Beta1 (AS 7.1.0.Final-redhat-1) started (with errors) in 2418ms - Started 135 of 209 services (2 services failed or missing dependencies, 70 services are passive or on-demand) 17:44:11,946 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "postgresql-9.0-801.jar" 17:44:12,086 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0) 17:44:12,107 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/JBTravelDatasource] 17:44:12,199 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "postgresql-9.0-801.jar" 17:44:12,201 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014776: Newly corrected services: service jboss.jdbc-driver.postgresql-9_0-801_jar (no longer required) -- 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
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 May 2012