[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear
by Tom Eicher (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Tom Eicher commented on AS7-6565:
---------------------------------
Having the ear name as _part_ of the service name is reasonable, but not _only_ the ear name.
i.e. {{myapp_ear_postgresql_9_1_901_jdbc4_jar as expected}} would make sense, but not {{myapp_ear}}.
Igmagine, you had 2 JDBC drivers (one postgres, one Oracle) in the ear...
> jdbc driver deployed inside ear takes name of ear
> -------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Tom Eicher
> Assignee: Jesper Pedersen
>
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear
by Tom Eicher (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Tom Eicher edited comment on AS7-6565 at 2/20/13 3:18 AM:
----------------------------------------------------------
Having the ear name as _part_ of the service name is reasonable, but not _only_ the ear name.
i.e. {{myapp_ear_postgresql_9_1_901_jdbc4_jar}} would make sense, but not {{myapp_ear}}.
Imagine, you had 2 JDBC drivers (one postgres, one Oracle) in the ear...
was (Author: tomeicher):
Having the ear name as _part_ of the service name is reasonable, but not _only_ the ear name.
i.e. {{myapp_ear_postgresql_9_1_901_jdbc4_jar as expected}} would make sense, but not {{myapp_ear}}.
Igmagine, you had 2 JDBC drivers (one postgres, one Oracle) in the ear...
> jdbc driver deployed inside ear takes name of ear
> -------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Tom Eicher
> Assignee: Jesper Pedersen
>
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
jaikiran pai updated AS7-6565:
------------------------------
Assignee: Jesper Pedersen
Component/s: JCA
> jdbc driver deployed inside ear takes name of ear
> -------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Tom Eicher
> Assignee: Jesper Pedersen
>
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on AS7-6565:
-----------------------------------
I don't think this is a bug. In fact, I think it's good to have the .ear name as part of the driver name. I even think there was a proper feature request for this. Consider a case where you deployed 2 different versions but with the same name, foo-driver.jar JDBC jar as part of 2 different EAR files. You want them to be unique and uniquely identifiable. So if I was packaging the driver jar as part of the EAR, I would find it right that the ear name is being used to identify the driver.
As for:
{quote}
2. driver name (as to be used in datasource definition) should be logged with the log message above.
{quote}
I think that's a reasonable enhancement. If not as part of that log message, maybe we should add a new log message which writes out the driver name. Of course if it isn't already being done.
I'll leave it to the JCA team to decide about this though. I'll set the right component of this JIRA so that it gets handled by the JCA team.
> jdbc driver deployed inside ear takes name of ear
> -------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.1.Final
> Reporter: Tom Eicher
>
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6548) To add salve node dynamicaly
by hitesh yadav (JIRA)
[ https://issues.jboss.org/browse/AS7-6548?page=com.atlassian.jira.plugin.s... ]
hitesh yadav edited comment on AS7-6548 at 2/20/13 1:09 AM:
------------------------------------------------------------
I have created cluster of two nodes N1 + N2 .
Here N1 is domain controller.
I have deploy .war "First_JBOSS_APP.war" to the cluster(N1+N2).
In this case cluster(N1+N2) work properly in all case .
Then i try to add new slave node N3 to the cluster (N1+N2) .
I got the error at slave node N3 side
[Server:server-three] 16:54:06,847 ERROR [org.jboss.as.controller] (Controller Boot Thread) Operation ("add") failed - address: ([("deployment" => "First_JBOSS_APP.war")]) - failure description: "No deployment content with hash 89880ba22c4ea01c43c00e2ce528166a5629a2ff is available in the deployment content repository."
"Unstable" means
After add of slave node N3 to the cluster i am not able to remove/disable "First_JBOSS_APP.war" from the cluster (N1+N2+N3)
was (Author: hitesysony87):
I have created cluster of two nodes N1 + N2 .
Here N1 is domain controller.
I have deploy .war "First_JBOSS_APP.war" to the cluster(N1+N2).
In this case cluster(N1+N2) work properly in all case .
Then i try to add new slave node N3 to the cluster (N1+N2) .
I got the error at slave node N3 side
[Server:server-three] 16:54:06,847 ERROR [org.jboss.as.controller] (Controller Boot Thread) Operation ("add") failed - address: ([("deployment" => "First_JBOSS_APP.war")]) - failure description: "No deployment content with hash 89880ba22c4ea01c43c00e2ce528166a5629a2ff is available in the deployment content repository."
"Unstable" means
After that i am not able to remove/disable "First_JBOSS_APP.war" from the cluster (N1+N2+N3)
> To add salve node dynamicaly
> ----------------------------
>
> Key: AS7-6548
> URL: https://issues.jboss.org/browse/AS7-6548
> Project: Application Server 7
> Issue Type: Clarification
> Components: Clustering, ConfigAdmin, Domain Management, Server
> Affects Versions: 7.0.2.Final
> Environment: Linux , jboss-as-web-7.0.2.Final
> Reporter: hitesh yadav
> Assignee: Paul Ferraro
> Labels: jboss
>
> Once cluster(domain) is created and if we have deploy .war in cluster after that if we try to add new slave node cluster become unstable.
> We are not able to disable/remove .war from domain controller and also from slave .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6548) To add salve node dynamicaly
by hitesh yadav (JIRA)
[ https://issues.jboss.org/browse/AS7-6548?page=com.atlassian.jira.plugin.s... ]
hitesh yadav commented on AS7-6548:
-----------------------------------
I have created cluster of two nodes N1 + N2 .
Here N1 is domain controller.
I have deploy .war "First_JBOSS_APP.war" to the cluster(N1+N2).
In this case cluster(N1+N2) work properly in all case .
Then i try to add new slave node N3 to the cluster (N1+N2) .
I got the error at slave node N3 side
[Server:server-three] 16:54:06,847 ERROR [org.jboss.as.controller] (Controller Boot Thread) Operation ("add") failed - address: ([("deployment" => "First_JBOSS_APP.war")]) - failure description: "No deployment content with hash 89880ba22c4ea01c43c00e2ce528166a5629a2ff is available in the deployment content repository."
"Unstable" means
After that i am not able to remove/disable "First_JBOSS_APP.war" from the cluster (N1+N2+N3)
> To add salve node dynamicaly
> ----------------------------
>
> Key: AS7-6548
> URL: https://issues.jboss.org/browse/AS7-6548
> Project: Application Server 7
> Issue Type: Clarification
> Components: Clustering, ConfigAdmin, Domain Management, Server
> Affects Versions: 7.0.2.Final
> Environment: Linux , jboss-as-web-7.0.2.Final
> Reporter: hitesh yadav
> Assignee: Paul Ferraro
> Labels: jboss
>
> Once cluster(domain) is created and if we have deploy .war in cluster after that if we try to add new slave node cluster become unstable.
> We are not able to disable/remove .war from domain controller and also from slave .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6566) -ds.xml file using driver-class silently ignored
by Tom Eicher (JIRA)
Tom Eicher created AS7-6566:
-------------------------------
Summary: -ds.xml file using driver-class silently ignored
Key: AS7-6566
URL: https://issues.jboss.org/browse/AS7-6566
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Tom Eicher
When a datasource is defined within a {{*-ds.xml}} file, it is supposed to provide a {{<driver>}} element and not a {{<driver-class>}} (at least that is what the forum reference sais.)
Anyways, a such a datasource is completely silently ignored.
The failed datasource deployment should be recognized, logged and handled as such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear
by Tom Eicher (JIRA)
Tom Eicher created AS7-6565:
-------------------------------
Summary: jdbc driver deployed inside ear takes name of ear
Key: AS7-6565
URL: https://issues.jboss.org/browse/AS7-6565
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Tom Eicher
Including a JDBC driver, in this case PostgreSQL, in an ear like
{code}
myapp.ear:
lib/postgresql-9.1-901.jdbc4.jar
{code}
does deploy the driver:
{code}
23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
{code}
however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
but it's {{myapp_ear}}.
(Seen in admin console, and this is the only value accepted in my -ds.xml file.)
1. JDBC driver service should pick name of innermost jar, not of containing ear
2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6557) Verify operation within a security manager
by Anil Saldhana (JIRA)
[ https://issues.jboss.org/browse/AS7-6557?page=com.atlassian.jira.plugin.s... ]
Anil Saldhana commented on AS7-6557:
------------------------------------
David Lloyd - agree that we should discuss about the SM operations at the modules level.
> Verify operation within a security manager
> ------------------------------------------
>
> Key: AS7-6557
> URL: https://issues.jboss.org/browse/AS7-6557
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: David Lloyd
> Assignee: Anil Saldhana
> Fix For: 8.0.0.Alpha1
>
>
> As per the Java EE 7 spec, all Java EE products must be capable of running within a Java security manager. Test each Java EE configuration including application client for security manager operability.
> Discuss with [~dmlloyd] options around modules integration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months