[JBoss JIRA] (DROOLS-1114) Add ConversationId http header/jms property to allow dynamic routing of requests
by Maciej Swiderski (JIRA)
Maciej Swiderski created DROOLS-1114:
----------------------------------------
Summary: Add ConversationId http header/jms property to allow dynamic routing of requests
Key: DROOLS-1114
URL: https://issues.jboss.org/browse/DROOLS-1114
Project: Drools
Issue Type: Feature Request
Components: kie server
Affects Versions: 6.4.0.CR2
Reporter: Maciej Swiderski
Assignee: Edson Tirelli
to be able to implement rolling updates on openshift there is need to provide additional information so routing can properly navigate between server instances.
Kie Server (both server and client) should use conversation id that is composed of:
- kie server id
- container id
- release id (resolved release id if present)
- unique UUID string
all of these values are separated with : so it can be easily parsed. ReleaseId is by itself separated with : as it's GAV (group : artifact : version)
Entire conversationId is URL encoded so it can be easily transferred over the wire.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1464) LogContexts are not removed for ear subdeployments
by Aaron Ogburn (JIRA)
Aaron Ogburn created WFCORE-1464:
------------------------------------
Summary: LogContexts are not removed for ear subdeployments
Key: WFCORE-1464
URL: https://issues.jboss.org/browse/WFCORE-1464
Project: WildFly Core
Issue Type: Bug
Components: Logging
Affects Versions: 2.1.0.Final
Reporter: Aaron Ogburn
Assignee: James Perkins
Attachments: app.ear
If an ear does not have its own LogContext created, but a subdeployment in it does, the subdeployment never has its LogContext cleaned up upon undeploy, leading to PermGen leaks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6495) Wildfly SSL Setup Fails on HSM-Backed Keystore
by Gregory Ramsperger (JIRA)
Gregory Ramsperger created WFLY-6495:
----------------------------------------
Summary: Wildfly SSL Setup Fails on HSM-Backed Keystore
Key: WFLY-6495
URL: https://issues.jboss.org/browse/WFLY-6495
Project: WildFly
Issue Type: Bug
Components: Domain Management
Affects Versions: 9.0.2.Final, 8.2.1.Final, 10.1.0.Final
Environment: Any host environment with an HSM for key management
Reporter: Gregory Ramsperger
Assignee: Brian Stansberry
Using a keystore type that does not allow or returns empty from getEncoded() on private keys causes a KeyStoreException at startup. This is common in HSM-backed key operations.
Storing SSL keys and certs in an HSM is a common method of securing keys and offloading SSL overhead.
FileKeyStore.java copies a KeyStore.Entry value into a JKS KeyStore but JKS and PKCS12 KeyStore implementations maintain a copy of the encoded PKCS#8 data for private keys. When applying a KeyStore.Entry from a source that does not return the data for security reasons, the import fails.
While it's still not guaranteed to work with all KeyStore providers, switching {{KeyStore.getInstance("JKS")}} to {{KeyStore.getInstance(provider)}} fixes the issue for SafeNet "Luna" and SunPKCS11 "PKCS11" KeyStore implementations while not breaking the "PKCS12" and "JKS" cases.
See [https://github.com/wildfly/wildfly-core/blob/master/domain-management/src...]
Log output:
{noformat}
2016-04-04 18:53:51,100 i-4b6f79d1 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.server.controller.management.security_realm.test.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.test.key-manager: JBAS015229: Unable to start service
at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:148)
at org.jboss.as.domain.management.security.FileKeyManagerService.start(FileKeyManagerService.java:119)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
Caused by: java.security.KeyStoreException: Cannot get key bytes, not PKCS#8 encoded
at sun.security.provider.KeyProtector.protect(KeyProtector.java:174) [rt.jar:1.8.0_60]
at sun.security.provider.JavaKeyStore.engineSetKeyEntry(JavaKeyStore.java:267) [rt.jar:1.8.0_60]
at sun.security.provider.JavaKeyStore$JKS.engineSetKeyEntry(JavaKeyStore.java:56) [rt.jar:1.8.0_60]
at java.security.KeyStoreSpi.engineSetEntry(KeyStoreSpi.java:537) [rt.jar:1.8.0_60]
at sun.security.provider.KeyStoreDelegator.engineSetEntry(KeyStoreDelegator.java:179) [rt.jar:1.8.0_60]
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineSetEntry(JavaKeyStore.java:70) [rt.jar:1.8.0_60]
at java.security.KeyStore.setEntry(KeyStore.java:1557) [rt.jar:1.8.0_60]
at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:136)
... 6 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-4146) Cache add operation should automatically create its child resources
by Maxim Karavaev (JIRA)
[ https://issues.jboss.org/browse/WFLY-4146?page=com.atlassian.jira.plugin.... ]
Maxim Karavaev commented on WFLY-4146:
--------------------------------------
Of course, sorry for this. [https://developer.jboss.org/message/954012]
BTW, it didn't work for me.
> Cache add operation should automatically create its child resources
> -------------------------------------------------------------------
>
> Key: WFLY-4146
> URL: https://issues.jboss.org/browse/WFLY-4146
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 10.0.0.Alpha6
>
>
> There is effectively no difference between the behavior of a cache that does not contain a given child resource (e.g. transaction, locking, etc) and one that contains the child resource, but with default attribute values.
> Consequently, the cache add operation should automatically create these resources (and the cache remove operation should automatically remove them). We can treat the child add operations as no-ops, and the child remove operations as a series of undefine-attribute operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6485) add JPA dependency in subdeployments to avoid NPE
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6485?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-6485:
-------------------------------
Description:
WeldDeploymentProcessor only processes top level deployments (jpa dependencies for subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
{quote}
Caused by: java.lang.NullPointerException
at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
{quote}
Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
was:
WeldDeploymentProcessor only processes top level deployments (subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
{quote}
Caused by: java.lang.NullPointerException
at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
{quote}
Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
> add JPA dependency in subdeployments to avoid NPE
> --------------------------------------------------
>
> Key: WFLY-6485
> URL: https://issues.jboss.org/browse/WFLY-6485
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 10.1.0.Final
>
>
> WeldDeploymentProcessor only processes top level deployments (jpa dependencies for subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
> We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
> {quote}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
> at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
> {quote}
> Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-4146) Cache add operation should automatically create its child resources
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-4146?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-4146:
------------------------------------
[~Maxoid] JIRA is not the appropriate venue for support questions. Please use the forums.
To answer your question, you should inject your cache directly, e.g. @Resource(lookup="java:jboss/infinispan/cache/cacheContainer/test") Cache<K, V> cache;
> Cache add operation should automatically create its child resources
> -------------------------------------------------------------------
>
> Key: WFLY-4146
> URL: https://issues.jboss.org/browse/WFLY-4146
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 10.0.0.Alpha6
>
>
> There is effectively no difference between the behavior of a cache that does not contain a given child resource (e.g. transaction, locking, etc) and one that contains the child resource, but with default attribute values.
> Consequently, the cache add operation should automatically create these resources (and the cache remove operation should automatically remove them). We can treat the child add operations as no-ops, and the child remove operations as a series of undefine-attribute operations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6485) add JPA dependency in subdeployments to avoid NPE
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6485?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-6485:
-------------------------------
Fix Version/s: 10.1.0.Final
> add JPA dependency in subdeployments to avoid NPE
> --------------------------------------------------
>
> Key: WFLY-6485
> URL: https://issues.jboss.org/browse/WFLY-6485
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 10.1.0.Final
>
>
> WeldDeploymentProcessor only processes top level deployments (subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
> We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
> {quote}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
> at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
> {quote}
> Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6485) add JPA dependency in subdeployments to avoid NPE
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6485?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-6485:
-------------------------------
Priority: Blocker (was: Major)
> add JPA dependency in subdeployments to avoid NPE
> --------------------------------------------------
>
> Key: WFLY-6485
> URL: https://issues.jboss.org/browse/WFLY-6485
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Blocker
>
> WeldDeploymentProcessor only processes top level deployments (subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
> We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
> {quote}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
> at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
> {quote}
> Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6485) add JPA dependency in subdeployments to avoid NPE
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-6485?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-6485:
------------------------------------
That's great :-)
> add JPA dependency in subdeployments to avoid NPE
> --------------------------------------------------
>
> Key: WFLY-6485
> URL: https://issues.jboss.org/browse/WFLY-6485
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 10.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
>
> WeldDeploymentProcessor only processes top level deployments (subdeployments are skipped). This means that subdeployments that CDI inject a persistence unit/context, will not add a dependency on the JPA PersistenceUnitService. As a result, the PersistenceUnitService is referenced before it is started (which leads to PersistenceUnitService.entityManagerFactory being null).
> We should avoid the following NPE by ensuring that dependencies on the JPA persistence unit are added for all sub-deployments.
> {quote}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186)
> at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:91)
> at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:212)
> {quote}
> Potential fix is at [https://github.com/scottmarlow/wildfly/tree/jpaNPE]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month