[JBoss JIRA] (WFLY-6405) Performance: WeldDeployment.getBeanDeploymentArchive method is synchronized
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-6405?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-6405:
-------------------------------------
I've added a follow up PR, https://github.com/wildfly/wildfly/pull/9021, as {{ConcurrentHashMap}}'s don't allow null keys. {{Class.getClassLoader()}} may return {{null}} if the class was loaded on the bootstrap class loader. e.g. {{java.lang.Integer}}.
> Performance: WeldDeployment.getBeanDeploymentArchive method is synchronized
> ---------------------------------------------------------------------------
>
> Key: WFLY-6405
> URL: https://issues.jboss.org/browse/WFLY-6405
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Class Loading
> Affects Versions: 10.0.0.Final
> Reporter: Panos Grigoropoulos
> Assignee: Stuart Douglas
>
> (Wildfly 10.0.0.FINAL)
> During the performance test of my app (50 concurrent users with jmeter) I am running into the following issue:
> There are locked threads in the method WeldDeployment.getBeanDeploymentArchive(). Looking the code, this method is synchronized, so it makes sense. The question is, is this the expected behavior or this is a bug. In both cases is there any workaround to overcome this limitation?
> STACK TRACE:
> ....
> org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():73
> org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():93
> org.jboss.as.weld.deployment.WeldDeployment.getBeanDeploymentArchive():226
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-1914) S3_PING doesn't work with S3 buckets created in Frankfurt region
by Mark Morris (JIRA)
[ https://issues.jboss.org/browse/JGRP-1914?page=com.atlassian.jira.plugin.... ]
Mark Morris commented on JGRP-1914:
-----------------------------------
I have submitted a pull request that contains support for AWS Authentication Version 4 RESTful API. Use the new protocol class, S3_PING2 for access to ALL AWS regions. Run and review the several JUnit tests that exercise the code. Until the pull request is accepted you can access the code at:
URL: https://github.com/TarantulaTechnology/JGroups.git
Branch: S3_PING2_rc1.
> S3_PING doesn't work with S3 buckets created in Frankfurt region
> -----------------------------------------------------------------
>
> Key: JGRP-1914
> URL: https://issues.jboss.org/browse/JGRP-1914
> Project: JGroups
> Issue Type: Bug
> Reporter: Gleb Leonov
> Assignee: Bela Ban
> Fix For: 4.1
>
> Attachments: AWS4.png
>
>
> I tried to use S3_PING with access and secret key pair. However, I got 400 (Bad Request) error. After some investigation, I found that modern S3 buckets created in Frankfurt needs amazon v4 authentication, which needs hmac-sha256. But now S3_PING supports only hmac-sha1, so I see no way to use S3_PING with buckets in Frankfurt region.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6800) Database ignored in Postgres JDBC URL
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6800?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-6800:
------------------------------------
thanks Mickaël, I'll close this as a duplicate of WFLY-6200.
> Database ignored in Postgres JDBC URL
> -------------------------------------
>
> Key: WFLY-6800
> URL: https://issues.jboss.org/browse/WFLY-6800
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Environment: java 8
> windows 7
> postgresql 9.4
> Reporter: Mickaël Vera
> Assignee: Scott Marlow
>
> I created a data source like this
> {code:xml}
> <datasource jndi-name="java:jboss/datasources/crawlRuntimeDS" pool-name="crawlRuntimePool" enabled="true" use-java-context="true">
> <connection-url>jdbc:postgresql://localhost:5432/runtimedb</connection-url>
> <driver>postgresDD</driver>
> <security>
> <user-name>postgres</user-name>
> <password>postgres</password>
> </security>
> </datasource>
> {code}
> {code:xml}
> I reference it in a persistent unit:
> <persistence-unit name="crawl-runtime-pu">
> <jta-data-source>java:jboss/datasources/crawlRuntimeDS</jta-data-source>
> <class>org.mvera.webscrap.model.crawl.runtime.CrawlEntity</class>
> <class>org.mvera.webscrap.model.crawl.runtime.PageCrawlStatusEntity</class>
> <exclude-unlisted-classes>true</exclude-unlisted-classes>
> <properties>
> <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> <property name="javax.persistence.schema-generation.database.action"
> value="none" />
> <property name="javax.persistence.schema-generation.scripts.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.scripts.create-target"
> value="D:/mvera/crawl-runtime-pu-create.sql" />
> <property name="javax.persistence.schema-generation.scripts.drop-target"
> value="D:/mvera/crawl-runtime-pu-drop.sql" />
> </properties>
> </persistence-unit>
> {code}
> I thought for a moment that all was working right. My data was persisted and I could read it from within an EJB using this datasource. But then I discovered that my data was not persisted at all in the database "crawlRuntimeDS" specified on the jdbc URL of the datasource but in the database "postgres" (a default database created during install of postgres).
> This is a real problem as my application uses serveral databases (several persistence units). The workaround today is to put all entities in the same "postgres" database.
> In the datasource, I can put any name as the database name, it is ignored, even if the database doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6800) Database ignored in Postgres JDBC URL
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6800?page=com.atlassian.jira.plugin.... ]
Scott Marlow closed WFLY-6800.
------------------------------
Resolution: Duplicate Issue
> Database ignored in Postgres JDBC URL
> -------------------------------------
>
> Key: WFLY-6800
> URL: https://issues.jboss.org/browse/WFLY-6800
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Environment: java 8
> windows 7
> postgresql 9.4
> Reporter: Mickaël Vera
> Assignee: Scott Marlow
>
> I created a data source like this
> {code:xml}
> <datasource jndi-name="java:jboss/datasources/crawlRuntimeDS" pool-name="crawlRuntimePool" enabled="true" use-java-context="true">
> <connection-url>jdbc:postgresql://localhost:5432/runtimedb</connection-url>
> <driver>postgresDD</driver>
> <security>
> <user-name>postgres</user-name>
> <password>postgres</password>
> </security>
> </datasource>
> {code}
> {code:xml}
> I reference it in a persistent unit:
> <persistence-unit name="crawl-runtime-pu">
> <jta-data-source>java:jboss/datasources/crawlRuntimeDS</jta-data-source>
> <class>org.mvera.webscrap.model.crawl.runtime.CrawlEntity</class>
> <class>org.mvera.webscrap.model.crawl.runtime.PageCrawlStatusEntity</class>
> <exclude-unlisted-classes>true</exclude-unlisted-classes>
> <properties>
> <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> <property name="javax.persistence.schema-generation.database.action"
> value="none" />
> <property name="javax.persistence.schema-generation.scripts.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.scripts.create-target"
> value="D:/mvera/crawl-runtime-pu-create.sql" />
> <property name="javax.persistence.schema-generation.scripts.drop-target"
> value="D:/mvera/crawl-runtime-pu-drop.sql" />
> </properties>
> </persistence-unit>
> {code}
> I thought for a moment that all was working right. My data was persisted and I could read it from within an EJB using this datasource. But then I discovered that my data was not persisted at all in the database "crawlRuntimeDS" specified on the jdbc URL of the datasource but in the database "postgres" (a default database created during install of postgres).
> This is a real problem as my application uses serveral databases (several persistence units). The workaround today is to put all entities in the same "postgres" database.
> In the datasource, I can put any name as the database name, it is ignored, even if the database doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6804) Where to define thread-factory for thread-pool in ejb3 subsystem
by Claudio Miranda (JIRA)
Claudio Miranda created WFLY-6804:
-------------------------------------
Summary: Where to define thread-factory for thread-pool in ejb3 subsystem
Key: WFLY-6804
URL: https://issues.jboss.org/browse/WFLY-6804
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Claudio Miranda
Priority: Minor
There is an attribute "thread-factory" in /subsystem=ejb3/thread-pool=default.
Looking at jboss-as-ejb3_2_0.xsd it references jboss-as-threads.xsd, but there is no jboss-as-threads subsystem, it was removed in Wildfly 10.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6800) Database ignored in Postgres JDBC URL
by Mickaël Vera (JIRA)
[ https://issues.jboss.org/browse/WFLY-6800?page=com.atlassian.jira.plugin.... ]
Mickaël Vera commented on WFLY-6800:
------------------------------------
This issue is the same as this one : WFLY-6200
> Database ignored in Postgres JDBC URL
> -------------------------------------
>
> Key: WFLY-6800
> URL: https://issues.jboss.org/browse/WFLY-6800
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Environment: java 8
> windows 7
> postgresql 9.4
> Reporter: Mickaël Vera
> Assignee: Scott Marlow
>
> I created a data source like this
> {code:xml}
> <datasource jndi-name="java:jboss/datasources/crawlRuntimeDS" pool-name="crawlRuntimePool" enabled="true" use-java-context="true">
> <connection-url>jdbc:postgresql://localhost:5432/runtimedb</connection-url>
> <driver>postgresDD</driver>
> <security>
> <user-name>postgres</user-name>
> <password>postgres</password>
> </security>
> </datasource>
> {code}
> {code:xml}
> I reference it in a persistent unit:
> <persistence-unit name="crawl-runtime-pu">
> <jta-data-source>java:jboss/datasources/crawlRuntimeDS</jta-data-source>
> <class>org.mvera.webscrap.model.crawl.runtime.CrawlEntity</class>
> <class>org.mvera.webscrap.model.crawl.runtime.PageCrawlStatusEntity</class>
> <exclude-unlisted-classes>true</exclude-unlisted-classes>
> <properties>
> <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect" />
> <property name="hibernate.show_sql" value="true" />
> <property name="hibernate.format_sql" value="true" />
> <property name="javax.persistence.schema-generation.database.action"
> value="none" />
> <property name="javax.persistence.schema-generation.scripts.action"
> value="drop-and-create" />
> <property name="javax.persistence.schema-generation.scripts.create-target"
> value="D:/mvera/crawl-runtime-pu-create.sql" />
> <property name="javax.persistence.schema-generation.scripts.drop-target"
> value="D:/mvera/crawl-runtime-pu-drop.sql" />
> </properties>
> </persistence-unit>
> {code}
> I thought for a moment that all was working right. My data was persisted and I could read it from within an EJB using this datasource. But then I discovered that my data was not persisted at all in the database "crawlRuntimeDS" specified on the jdbc URL of the datasource but in the database "postgres" (a default database created during install of postgres).
> This is a real problem as my application uses serveral databases (several persistence units). The workaround today is to put all entities in the same "postgres" database.
> In the datasource, I can put any name as the database name, it is ignored, even if the database doesn't exist.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6200) connection-url is required even when not used
by Mickaël Vera (JIRA)
[ https://issues.jboss.org/browse/WFLY-6200?page=com.atlassian.jira.plugin.... ]
Mickaël Vera commented on WFLY-6200:
------------------------------------
I reproduce this problem on wildfly-10.0.0.Final with postgresql.
<datasource jndi-name="java:jboss/datasources/crawlResultDS" pool-name="crawlResultPool" enabled="true" use-java-context="true">
<connection-url>jdbc:postgresql://localhost:5432/resultdb</connection-url>
<driver>postgresDD</driver>
<security>
<user-name>postgres</user-name>
<password>postgres</password>
</security>
</datasource>
<drivers>
<driver name="postgresDD" module="org.postgresql">
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
<datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class>
</driver>
</drivers>.
I can replace
<connection-url>jdbc:postgresql://localhost:5432/resultdb</connection-url>
with
<connection-url>anything</connection-url>
Wildfly ignores it.
> connection-url is required even when not used
> ---------------------------------------------
>
> Key: WFLY-6200
> URL: https://issues.jboss.org/browse/WFLY-6200
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Lin Gao
>
> Per the comments on WFLY-6157 and WFLY-6198, connection-url is ignored in a datasource if datasource-class is defined. However, connection-url is currently mandatory. If it is not present, WildFly fails to start:
> {noformat}
> 09:51:18,216 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 8) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "GamingPortalDS")
> ]) - failure description: "WFLYCTL0155: connection-url may not be null"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ELY-580) Add the ability to filter out unavailable mechanisms using the MechanismConfigurationSelector once the host name and protocol name are known
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-580?page=com.atlassian.jira.plugin.sy... ]
Farah Juma commented on ELY-580:
--------------------------------
Instead of the approach in the description, as mentioned in [PR #460|https://github.com/wildfly-security/wildfly-elytron/pull/460], we can select the {{MechanismConfiguration}} when setting the {{MechanismInformation}}. This allows {{createSaslServer}} to just return {{null}} if the {{MechanismConfiguration}} cannot be resolved. For the HTTP case, we can just return if the {{MechanismConfiguration}} cannot be resolved when evaluating an HTTP request.
> Add the ability to filter out unavailable mechanisms using the MechanismConfigurationSelector once the host name and protocol name are known
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-580
> URL: https://issues.jboss.org/browse/ELY-580
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Authentication Mechanisms, HTTP
> Reporter: Farah Juma
> Assignee: Farah Juma
>
> We could modify the {{HttpServerAuthenticationMechanism}} mechanism supplier to take an {{HttpServerRequest}} parameter in order to filter out unavailable mechanisms. (For HTTP auth, the host name and protocol name are obtained using the {{HttpServerRequest}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1635) Write attribute on a new deployment scanner fails in batch
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1635?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1635:
------------------------------------------
Probably better than catching and ignoring an ISE though is wrapping logic in an if (controller.getState() == UP) { ... } block.
> Write attribute on a new deployment scanner fails in batch
> ----------------------------------------------------------
>
> Key: WFCORE-1635
> URL: https://issues.jboss.org/browse/WFCORE-1635
> Project: WildFly Core
> Issue Type: Bug
> Components: Deployment Scanner, Domain Management
> Affects Versions: 3.0.0.Alpha3
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> Creating a new deployment-scanner and altering it's attribute fails if done in single batch. Running the commands without batch or running batch on CLI embed-server works fine.
> *reproduce*
> {noformat}
> batch
> /subsystem=deployment-scanner/scanner=scan:add(path=log, relative-to="jboss.server.base.dir", auto-deploy-exploded=false, scan-enabled=false)
> /subsystem=deployment-scanner/scanner=scan:write-attribute(name=scan-interval, value=6000)
> run-batch
> {noformat}
> fails with
> {noformat}
> 08:09:19,076 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("subsystem" => "deployment-scanner"),
> ("scanner" => "scan")
> ]): java.lang.IllegalStateException
> at org.jboss.as.server.deployment.scanner.DeploymentScannerService.getValue(DeploymentScannerService.java:234)
> at org.jboss.as.server.deployment.scanner.DeploymentScannerService.getValue(DeploymentScannerService.java:62)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceController.getValue(OperationContextImpl.java:2282)
> at org.jboss.as.server.deployment.scanner.AbstractWriteAttributeHandler.applyUpdateToRuntime(AbstractWriteAttributeHandler.java:58)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:104)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
> at java.security.AccessController.doPrivileged(AccessController.java:686)
> at javax.security.auth.Subject.doAs(Subject.java:569)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> using the embed server works
> {noformat}
> embed-server
> batch
> /subsystem=deployment-scanner/scanner=scan:add(path=log, relative-to="jboss.server.base.dir", auto-deploy-exploded=false, scan-enabled=false)
> /subsystem=deployment-scanner/scanner=scan:write-attribute(name=scan-interval, value=6000)
> run-batch
> {noformat}
> Setting only as minor as there is no real use case behind this (scan-interval can be set while adding a new scanner) - run into it quite accidentally. No regression against previous release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months