September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-675) Feedback with invalid configuration

by Jesper Pedersen (JIRA)

Feedback with invalid configuration ----------------------------------- Key: JBJCA-675 URL: https://issues.jboss.org/browse/JBJCA-675 Project: IronJacamar Issue Type: Task Components: Deployer Affects Versions: 1.1.0.Alpha1, 1.0.4.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0.5.Final, 1.1.0.Alpha2 Provide feedback when a <connection-definition> or <admin-object> is configured incorrectly regarding class-name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1842) Console usability: missing favicon icon

by Radoslav Husar (JIRA)

Console usability: missing favicon icon --------------------------------------- Key: AS7-1842 URL: https://issues.jboss.org/browse/AS7-1842 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Trivial This is useful for admins to bookmark it and recognize it easily, here is the icon: http://design.jboss.org/jbossAS/logo/final/favicon.ico and to head <link rel="shortcut icon" href="/console/favicon.ico" /> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1452) Resource Adapter config-property value passed incorrectly

by Brian Wallis (JIRA)

Resource Adapter config-property value passed incorrectly --------------------------------------------------------- Key: AS7-1452 URL: https://issues.jboss.org/browse/AS7-1452 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Environment: MacOSX, JDK 1.6.0_26 Reporter: Brian Wallis Assignee: Jesper Pedersen Possibly related to AS-1304 See the forum (link below) for details on how to reproduce. In the resource-adapter connection definition when you specify properties for the adapter like so: <connection-definition class-name="org.apache.jackrabbit.jca.JCAManagedConnectionFactory" jndi-name="java:/jca/DocumentStore" enabled="true" use-java-context="true" pool-name="jackrabbit-jca-2_2_7_rar-Pool" use-ccm="true"> <config-property name="HomeDir"> /Users/bwallis/InfoMedix/JBoss/jboss-as-7.1.0.Alpha1-SNAPSHOT/repository </config-property> <config-property name="ConfigFile"> /Users/bwallis/InfoMedix/JBoss/jboss-as-7.1.0.Alpha1-SNAPSHOT/repository/repository.xml </config-property> ... The values passed through to the resource adapter seems to come through as the strings ("HomeDir" => "/Users/bwallis/InfoMedix/JBoss/jboss-as-7.1.0.Alpha1-SNAPSHOT/repository") ("ConfigFile" => "/Users/bwallis/InfoMedix/JBoss/jboss-as-7.1.0.Alpha1-SNAPSHOT/repository/repository.xml") ie: not just the path as required. Result in the jackrabbit adapter case is that a directory called '("HomeDir" => "' is created. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
15
0 / 0

[JBoss JIRA] Created: (AS7-1745) update IJ to 1.0.4

by Stefano Maestri (JIRA)

update IJ to 1.0.4 ------------------ Key: AS7-1745 URL: https://issues.jboss.org/browse/AS7-1745 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Priority: Critical -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBMETA-335) Implement message-driven parsing

by Carlo de Wolf (JIRA)

Implement message-driven parsing -------------------------------- Key: JBMETA-335 URL: https://issues.jboss.org/browse/JBMETA-335 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Affects Versions: 7.0.0.Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1517) make sure flush connection operations work for non-java context bound ds

by Alexey Loubyansky (JIRA)

make sure flush connection operations work for non-java context bound ds ------------------------------------------------------------------------ Key: AS7-1517 URL: https://issues.jboss.org/browse/AS7-1517 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Alexey Loubyansky Assignee: Jesper Pedersen Fix For: 7.0.1.Final Working on the CLI I found flush connection operations don't work for datasources not bound in the java: context. Although, it's not the latest JCA code in my branch and needs checking against the latest one. This doesn't work: [standalone@localhost:9999 /] data-source add --jndi-name=myds --driver-name=h2 --pool-name=myds --connection-url=curl [standalone@localhost:9999 /] data-source flush-idle-connection-in-pool --jndi-name=myds failed to invoke operation: failed to match pool. Check JndiName: myds [standalone@localhost:9999 /] data-source remove --jndi-name=myds This does: [standalone@localhost:9999 /] data-source add --jndi-name=myds --driver-name=h2 --pool-name=myds --connection-url=curl --use-java-context=true [standalone@localhost:9999 /] flush-idle-connection-in-pool --jndi-name=myds [standalone@localhost:9999 /] remove --jndi-name=myds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1736) JCA seems to be installing services with no prefix

by Stefano Maestri (JIRA)

JCA seems to be installing services with no prefix -------------------------------------------------- Key: AS7-1736 URL: https://issues.jboss.org/browse/AS7-1736 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.1.Final Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 I just noticed that JCA seems to be installing services with no prefix (e.g. hortnetq-ra). I was just wondering if there any particular reason for this, rather than installing it under a resource adaptor specific namespace (e.g. jboss.jca.resourceadators.hornetq-ra) ? Stuart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1686) RARs with uppercase characters in the filename and connections defined in standalone.xml fails to deploy

by Leo Osborne (JIRA)

RARs with uppercase characters in the filename and connections defined in standalone.xml fails to deploy -------------------------------------------------------------------------------------------------------- Key: AS7-1686 URL: https://issues.jboss.org/browse/AS7-1686 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.1.Final Reporter: Leo Osborne Assignee: Jesper Pedersen a resource adapter with uppercase case characters in the filename fails to deploy when it has connections defined in standalone.xml. Stack trace: {quote} 17:30:12,426 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.raxml.uppercaseadapter_1: org.jboss.msc.service.StartException in service jboss.raxml.uppercaseadapter_1: org.jboss.jca.core.spi.mdr.NotFoundException: IJ000855: UpperCaseAdapter isn't registered at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:115) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: org.jboss.jca.core.spi.mdr.NotFoundException: IJ000855: UpperCaseAdapter isn't registered at org.jboss.jca.core.mdr.SimpleMetadataRepository.getResourceAdapter(SimpleMetadataRepository.java:150) at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:81) ... 5 more {quote} If there is a resource adapter with the same lowercase name, the stack trace is: {quote} 17:29:03,376 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."Adapter.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Adapter.rar".INSTALL: Failed to process phase INSTALL of deployment "Adapter.rar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.adapter is already registered at org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:137) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] ... 5 more Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.adapter is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:124) ... 6 more {quote} Tried on 7.0.1.Final and 7.1.0.Alpha1-SNAPSHOT commit 6c1afc2632aef6759f80139e5c74e7f594f50be3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1691) ConnectorServices.getResourceAdapteServiceName(raName) doesn't return ServiceName for hornetq-ra

by jaikiran pai (JIRA)

ConnectorServices.getResourceAdapteServiceName(raName) doesn't return ServiceName for hornetq-ra ------------------------------------------------------------------------------------------------ Key: AS7-1691 URL: https://issues.jboss.org/browse/AS7-1691 Project: Application Server 7 Issue Type: Bug Components: JCA Environment: AS7 upstream Reporter: jaikiran pai Assignee: Jesper Pedersen {code} ConnectorServices.getResourceAdapteServiceName(this.resourceAdapterName) {code} is expected to return the ServiceName(s) for the passed RA name. However, in the current AS7 upstream it fails to return any ServiceName for "hornetq-ra". Looks like the ResourceAdapterDeploymentService which processes the hornetq-ra never generates/registers the ServiceName via ConnectorServices. Furthermore, from a API client point of view (for example EJB3), this API may not always function correctly. For example, if the EJB3 integration code ends up calling this API to get the ServiceName to depend on, this API might return no value if the corresponding RA hasn't yet been processed. This makes it impossible for the EJB3 code to know on which ServiceName to depend on for a given RA. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1543) Failures in XADatasourceAdd leaves services still registered

by Stuart Douglas (JIRA)

Failures in XADatasourceAdd leaves services still registered ------------------------------------------------------------ Key: AS7-1543 URL: https://issues.jboss.org/browse/AS7-1543 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.Final Reporter: Stuart Douglas Assignee: Jesper Pedersen When attempting to register a xa datasource via the management api I ommited driver-name and the operation failed. After adding the required attribute and re-sending I now get: failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.xa-data-source-config.java:jboss/datasources/myDS is already registered", [ERROR] "rolled-back" => true -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 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 September 2011