May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-569) support driver as part of datasources_1.0.xsd

by Stefano Maestri (JIRA)

support driver as part of datasources_1.0.xsd --------------------------------------------- Key: JBJCA-569 URL: https://issues.jboss.org/browse/JBJCA-569 Project: IronJacamar Issue Type: Task Components: Common Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.CR1 support this driver into IJ too. See related issues for more details in AS7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-573) use classloaderplugin also in XAManagedConnectionFactory

by Stefano Maestri (JIRA)

use classloaderplugin also in XAManagedConnectionFactory -------------------------------------------------------- Key: JBJCA-573 URL: https://issues.jboss.org/browse/JBJCA-573 Project: IronJacamar Issue Type: Bug Components: JDBC Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Commented: (AS7-867) Dependency issue on OSGi bundle in AS7

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/AS7-867?page=com.atlassian.jira.plugin.sy... ] Gary Brown commented on AS7-867: -------------------------------- Has this test been pushed to AS7 master, as could not find it: https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src... So is the problem the fact that I have added ".jar" to my dependency? i.e. Dependencies: deployment.TestBundle .jar I tried removing the .jar and it still complains: 10:03:31,164 INFO [org.jboss.as.server] (MSC service thread 1-3) Service status report New missing/unsatisfied dependencies: service module.spec.service."deployment.TestBundle".main (missing) 10:03:31,177 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment WS-Dependencies.war in 10ms 10:03:31,178 INFO [org.jboss.as.server] (MSC service thread 1-4) Service status report Newly corrected services: service module.spec.service."deployment.TestBundle".main (no longer required) Do I need to wait for CR1 before this will work? If so, any idea when it will be released? Thanks in advance. > Dependency issue on OSGi bundle in AS7 > -------------------------------------- > > Key: AS7-867 > URL: https://issues.jboss.org/browse/AS7-867 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Environment: jbossas7-beta3 > Reporter: Gary Brown > Assignee: Thomas Diesler > Attachments: TestBundle.jar, WS-Dependencies.war > > > When I deploy the attached "TestBundle.jar" OSGi bundle (with activation set to eager in standalone.xml, to force it to activate), > <subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager"> > I get: > 10:57:14,168 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "TestBundle.jar" > 10:57:14,273 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Installing deployment: [TestBundle:1.0.0.201105171313,location=TestBundle.jar] > 10:57:14,277 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: TestBundle:1.0.0.201105171313 > 10:57:14,282 INFO [stdout] (MSC service thread 1-3) Hello World!! > 10:57:14,282 INFO [stdout] (MSC service thread 1-3) CREATED TEST SERVICE > 10:57:14,294 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-3) Bundle started: TestBundle:1.0.0.201105171313 > which is expected - i.e. the "Hello World!!" message is generated from the activator's start method, so indicates that the bundle has activated. > However if I deploy a war that has a dependency on this module (WS-Dependencies.war), I get: > 10:58:59,335 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "WS-Dependencies.war" > 10:58:59,399 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report > New missing/unsatisfied dependencies: > service module.spec.service."deployment.TestBundle.jar".main (missing) > 10:58:59,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment WS-Dependencies.war in 14ms > 10:58:59,417 INFO [org.jboss.as.server] (MSC service thread 1-1) Service status report > Newly corrected services: > service module.spec.service."deployment.TestBundle.jar".main (no longer required) > But if I do this same process with a TestBundle.jar that has no OSGi metadata (so just a plain jar), when I deploy the war I get: > 11:08:19,704 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "TestBundle.jar" > 11:08:34,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "WS-Dependencies.war" > 11:08:34,849 WARN [org.jboss.wsf.stack.cxf.deployment.aspect.DescriptorDeploymentAspect] (MSC service thread 1-1) Spring not available, skipping check for user provided jbossws-cxf.xml / cxf.xml configuration files. > 11:08:34,855 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-1) Add Service > id=HelloPortType > address=http://localhost:8080/WS-Dependencies/HelloPortType > implementor=test.HelloPortTypeImpl > invoker=org.jboss.wsf.stack.cxf.InvokerJSE > serviceName={http://test/}HelloPortType > portName={http://test/}HelloPortTypeImplPort > wsdlLocation=null > mtomEnabled=false > 11:08:34,856 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (MSC service thread 1-1) register: jboss.ws:context=WS-Dependencies,endpoint=HelloPortType > 11:08:35,831 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://test/}HelloPortType from class test.HelloPortType > 11:08:36,215 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/WS-Dependencies/HelloPortType > 11:08:36,300 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-1) WSDL published to: file:/home/gbrown/NotBackedUp/testing/riftsaw/as7/jboss-7.0.0.Beta3/standalone/data/wsdl/WS-Dependencies.war/HelloPortType.wsdl > 11:08:37,149 INFO [org.jboss.web] (MSC service thread 1-3) registering web context: /WS-Dependencies > First line shows the plain jar being deployed. > This seems to indicate that the OSGi bundle is not in a fully activated state from the jboss modules perspective? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-570) create a driver repository service

by Stefano Maestri (JIRA)

create a driver repository service ---------------------------------- Key: JBJCA-570 URL: https://issues.jboss.org/browse/JBJCA-570 Project: IronJacamar Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.CR1 We need a driver repository service to get the list of deployed jdbc driver during Datrasource adding from UI -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (AS7-711) Make a version attribute (optional) for driver tag instead the current parsed notation

by Stefano Maestri (JIRA)

Make a version attribute (optional) for driver tag instead the current parsed notation -------------------------------------------------------------------------------------- Key: AS7-711 URL: https://issues.jboss.org/browse/AS7-711 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.CR1 <dmlloyd> <driver class="org.foo.Bar" version="1.1"/> where version is *optional* unless there are more than one version of the same driver deployed <maeste> hbraun: it's there if you have more than one version of th driver deployed <dmlloyd> and we need a smarter way to detect Driver, DataSource and XADataSource classes in deployments too <maeste> dmlloyd: oki it makes sense, but it's just another way to express it as an attribute instead of part of the name. We are not removing it, just writing it more elegant :) <dmlloyd> and making it optional <dmlloyd> might even do majorVersion=xs:int, minorVersion=xs:int if you want to be thorough <maeste> dmlloyd: yup, make it optional is possible also on current notation. Making it optional is the real work anyway <dmlloyd> then you can make minor optional even if major is present <maeste> dmlloyd: oki <hbraun> maeste: another valuable modification would be a default value if there is only one driver <maeste> hbraun: yup, it's what we are doing making it optional <hbraun> maeste: great <maeste> hbraun: oh you mean the whole driver tag? <hbraun> maeste: i think that will simpify things a lot <bstansberry> maxandersen: ok good <hbraun> maeste: no <maeste> hbraun: just version right? <hbraun> maeste: i was speking of the version attribute <hbraun> maeste: exactly <maeste> hbraun: oki so we agree -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (AS7-800) Index out of bounds when creating datasource

by Heiko Braun (JIRA)

Index out of bounds when creating datasource -------------------------------------------- Key: AS7-800 URL: https://issues.jboss.org/browse/AS7-800 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Priority: Blocker [INFO] { [INFO] "operation" => "add", [INFO] "address" => [ [INFO] ("profile" => "default"), [INFO] ("subsystem" => "datasources"), [INFO] ("data-source" => "anotherH2") [INFO] ], [INFO] "name" => "anotherH2", [INFO] "jndi-name" => "ah2", [INFO] "enabled" => true, [INFO] "driver-name" => "h2", [INFO] "driver-class-name" => "org.h2.Driver", [INFO] "driver-major-version" => 1, [INFO] "driver-minor-version" => 2, [INFO] "pool-name" => "anotherH2_Pool", [INFO] "connection-url" => "no", [INFO] "user-name" => "asd", [INFO] "password" => "" [INFO] } [ERROR] 2011-05-17 14:19:11,569 [ERROR] On Tue May 17 14:19:11 CEST 2011, MessageCenter received Failed to create datasource [ERROR] 2011-05-17 14:19:11,579 [ERROR] Message{conciseMessage='Failed to create datasource', detailedMessage='{ [ERROR] "outcome" => "failed", [ERROR] "result" => {"server-groups" => {"main-server-group" => { [ERROR] "server-two" => { [ERROR] "host" => "local", [ERROR] "response" => { [ERROR] "outcome" => "failed", [ERROR] "failure-description" => "java.lang.StringIndexOutOfBoundsException: String index out of range: -3" [ERROR] } [ERROR] }, [ERROR] "server-one" => { [ERROR] "host" => "local", [ERROR] "response" => { [ERROR] "outcome" => "failed", [ERROR] "failure-description" => "java.lang.StringIndexOutOfBoundsException: String index out of range: -3" [ERROR] } [ERROR] } [ERROR] }}}, [ERROR] "failure-description" => "Operation was not applied successfully to any servers" [ERROR] }', fired=Tue May 17 14:19:11 CEST 2011, severity=Error, options=[]} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (AS7-720) Removing and re-adding datasource with same name throws Exception (domain)

by Heiko Braun (JIRA)

Removing and re-adding datasource with same name throws Exception (domain) -------------------------------------------------------------------------- Key: AS7-720 URL: https://issues.jboss.org/browse/AS7-720 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (AS7-802) JDCB driver :read-resource-description is not updated

by Heiko Braun (JIRA)

JDCB driver :read-resource-description is not updated ----------------------------------------------------- Key: AS7-802 URL: https://issues.jboss.org/browse/AS7-802 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 I.e. it doesn't contain "driver-xa-datasource-class-name" which is part of the resource representation: [domain@localhost:9999 /] /host=local/server=server-one/subsystem=datasources/jdbc-driver=h2:read-resource { "outcome" => "success", "result" => { "driver-name" => "h2", "driver-module-name" => "com.h2database.h2", "driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource" }, "compensating-operation" => undefined } [domain@localhost:9999 /] /host=local/server=server-one/subsystem=datasources/jdbc-driver=h2:read-resource-description { "outcome" => "success", "result" => { "description" => "A service that makes a JDBC driver available for use in the runtime", "head-comment-allowed" => true, "tail-comment-allowed" => true, "attributes" => { "driver-name" => { "description" => "The symbolic name of this driver used to reference it in the register", "type" => STRING, "required" => true, "access-type" => "read-only", "storage" => "configuration" }, "deployment-name" => { "description" => "The name of the deployment unit from which the driver was loaded, if it was loaded from a deployment", "type" => STRING, "access-type" => "read-only", "storage" => "configuration" }, "driver-module-name" => { "description" => "The name of the module from which the driver was loaded, if it was loaded from the module path", "type" => STRING, "access-type" => "read-only", "storage" => "configuration" }, "module-slot" => { "description" => "The slot of the module from which the driver was loaded, if it was loaded from the module path", "type" => STRING, "access-type" => "read-only", "storage" => "configuration" }, "driver-class-name" => { "description" => "The fully qualified class name of the driver's implementation of java.sql.Driver", "type" => STRING, "access-type" => "read-only", "storage" => "configuration" }, "driver-major-version" => { "description" => "The driver's major version number", "type" => INT, "access-type" => "read-only", "storage" => "configuration" }, "driver-minor-version" => { "description" => "The driver's minor version number", "type" => INT, "access-type" => "read-only", "storage" => "configuration" }, "jdbc-compliant" => { "description" => "Whether or not the driver is JDBC compliant", "type" => BOOLEAN, "access-type" => "read-only", "storage" => "configuration" } } }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (AS7-803) Subsystem "datasource": xa datasource created but not persisted

by Heiko Braun (JIRA)

Subsystem "datasource": xa datasource created but not persisted --------------------------------------------------------------- Key: AS7-803 URL: https://issues.jboss.org/browse/AS7-803 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Priority: Blocker I can create a xa datasource that will show up in-memory, but it's not written to xml: {noformat} [domain@localhost:9999 /] /profile=default/subsystem=datasources/xa-data-source=myXA:read-resource { "outcome" => "success", "result" => { "xa-data-source-properties" => {"URL" => "jdbc:h2:mem:test"}, "jndi-name" => "myXA", "driver-name" => "h2", "pool-name" => "myXA_Pool", "enabled" => true, "user-name" => "sa", "password" => "sa", "use-fast-fail" => undefined, "background-validation" => undefined, "max-pool-size" => undefined, "idle-timeout-minutes" => undefined, "blocking-timeout-wait-millis" => undefined, "background-validation-minutes" => undefined, "pool-use-strict-min" => undefined, "min-pool-size" => undefined, "pool-prefill" => undefined }, "compensating-operation" => undefined } {noformat} {noformat} <subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> <datasource jndi-name="java:/H2DS" pool-name="H2DS" enabled="true" use-java-context="true"> <connection-url> jdbc:h2:mem:test;DB_CLOSE_DELAY=-1 </connection-url> <driver> h2 </driver> <pool> <prefill> false </prefill> <use-strict-min> false </use-strict-min> </pool> <security> <user-name> sa </user-name> <password> sa </password> </security> <validation> <validate-on-match> false </validate-on-match> <background-validation> false </background-validation> <useFastFail> false </useFastFail> </validation> <statement/> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class> org.h2.jdbcx.JdbcDataSource </xa-datasource-class> </driver> </drivers> </datasources> </subsystem> : {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2249) Update on MDB selector without having to redeploy the whole application.

by Tom Ross (JIRA)

Update on MDB selector without having to redeploy the whole application. ------------------------------------------------------------------------ Key: EJBTHREE-2249 URL: https://issues.jboss.org/browse/EJBTHREE-2249 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: EJB 3.1 Environment: JBoss EAP 5.x Reporter: Tom Ross There is a requirement to allow an update on MDB selector to be performed without having to redeploy the application. At the moment the only way to change a MDB selector si to update it's deployment descriptor which will force the redeployment of the whole application. This is not a very practical solution particularly if more than one application is involved. It would have been much more convenient if the MDB container would allow to change the MDB selector without a need to redeploy the application. In this case the end user is prepared to accept any consequences in performance that amy be caused by disconnecting and reconnecting MDB session. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
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 2011