[JBoss JIRA] (WFLY-10333) jboss.ejb.default-local-transport-provider missing in appclient mode
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-10333?page=com.atlassian.jira.plugin... ]
Lin Gao updated WFLY-10333:
---------------------------
Labels: downstream_dependency (was: )
> jboss.ejb.default-local-transport-provider missing in appclient mode
> --------------------------------------------------------------------
>
> Key: WFLY-10333
> URL: https://issues.jboss.org/browse/WFLY-10333
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Lin Gao
> Assignee: Bartosz Baranowski
> Labels: downstream_dependency
> Attachments: app-client.ear
>
>
> After the fix for JBEAP-14243, when trying to run an ejb client using the appclient mode, the client server fails with the following error:
> {code}
> 14:55:01,920 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "app-client.ear" (runtime-name: "app-client.ear")
> 14:55:01,973 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb.jar")
> 14:55:01,973 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "simpleClient.jar")
> 14:55:02,045 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'StatelessSessionBean' in deployment unit 'subdeployment "ejb.jar" of deployment "app-client.ear"' are as follows:
> java:global/app-client/ejb/StatelessSessionBean!org.jboss.as.quickstarts.appclient.server.ejb.StatelessSession
> java:app/ejb/StatelessSessionBean!org.jboss.as.quickstarts.appclient.server.ejb.StatelessSession
> java:module/StatelessSessionBean!org.jboss.as.quickstarts.appclient.server.ejb.StatelessSession
> java:jboss/exported/app-client/ejb/StatelessSessionBean!org.jboss.as.quickstarts.appclient.server.ejb.StatelessSession
> java:global/app-client/ejb/StatelessSessionBean
> java:app/ejb/StatelessSessionBean
> java:module/StatelessSessionBean
> 14:55:02,058 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.2.GA (WildFly Core 3.0.13.Final-redhat-1) started (with errors) in 1734ms - Started 208 of 247 services (7 services failed or missing dependencies, 47 services are lazy, passive or on-demand)
> 14:55:02,061 ERROR [org.jboss.as.controller.management-operation] (Thread-40) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "app-client.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.ejb.default-local-transport-provider"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.ejbClientContext.deployment.\"app-client.ear\" is missing [jboss.ejb.default-local-transport-provider]"]
> }
> 14:55:02,062 ERROR [org.jboss.as.server] (Thread-40) WFLYSRV0021: Deploy of deployment "app-client.ear" was rolled back with the following failure message:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.ejb.default-local-transport-provider"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.ejbClientContext.deployment.\"app-client.ear\" is missing [jboss.ejb.default-local-transport-provider]"]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10331) The standalone-minimalistic.xml example config has wrong attribute order and a comment
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-10331:
---------------------------------------
Summary: The standalone-minimalistic.xml example config has wrong attribute order and a comment
Key: WFLY-10331
URL: https://issues.jboss.org/browse/WFLY-10331
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Correct the file to put the http-interface element attributes in xsd order and to remove the comment that can't be persisted.
Besides being correct this will eliminate a diff to the version galleon will create.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2528) GIT clone ssh not working with java 8 > u111 in drools workbench
by Alexander Revkov (JIRA)
Alexander Revkov created DROOLS-2528:
----------------------------------------
Summary: GIT clone ssh not working with java 8 > u111 in drools workbench
Key: DROOLS-2528
URL: https://issues.jboss.org/browse/DROOLS-2528
Project: Drools
Issue Type: Bug
Affects Versions: 7.7.0.Final, 7.5.0.Final, 6.5.0.Final
Environment: CentOS 7, Java 8 u111, Java 8 u161, Java 9, Java 10
Reporter: Alexander Revkov
Assignee: Edson Tirelli
Priority: Critical
I cloned my repo by git-ssh ssh://my_ip:8080/myrepo
If i run drools workbench with java 8 u111. This work is fine. But when i try run workbench with latest version of java 8u161, 9 or 10. clone with ssh not working. I see this exception in log:
{code:java}
Exception caught: java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size
at sun.security.provider.DSA.checkKey(DSA.java:111)
at sun.security.provider.DSA.engineInitSign(DSA.java:143)
at java.security.Signature$Delegate.engineInitSign(Signature.java:1178)
at java.security.Signature.initSign(Signature.java:531)
at org.apache.sshd.common.signature.AbstractSignature.init(AbstractSignature.java:47)
at org.apache.sshd.server.kex.AbstractDHGServer.next(AbstractDHGServer.java:91)
at org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:393)
at org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:295)
at org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:731)
at org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:277)
at org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)
at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:187)
at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:173)
at org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)
at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
at sun.nio.ch.Invoker$2.run(Invoker.java:218)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
Maybe this is related to this? http://www.oracle.com/technetwork/java/javase/8u151-relnotes-3850493.html
If yes what users need do to fix it? Else, please fix it. Thank you.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Hlulani Mhlongo (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Hlulani Mhlongo commented on WFLY-6789:
---------------------------------------
Nevermind, just got it
Thanks
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-6789) 'xa-datasource-properties' is not found among the supported properties
by Hlulani Mhlongo (JIRA)
[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ]
Hlulani Mhlongo commented on WFLY-6789:
---------------------------------------
What if you are running on a Non-Interactive Mode:
./jboss-cli -c --command='...'
How does this work then?
I'm writing a script to automate creating the resources
> 'xa-datasource-properties' is not found among the supported properties
> ----------------------------------------------------------------------
>
> Key: WFLY-6789
> URL: https://issues.jboss.org/browse/WFLY-6789
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Reporter: Kylin Soong
> Assignee: Stefano Maestri
> Priority: Critical
>
> WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost])
> {code}
> will throw a exception
> {code}
> 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout]
> {code}
> If execute without xa-datasource-properties which like previous version
> {code}
> /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true)
> {code}
> the exception like
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource",
> "rolled-back" => true
> }
> {code}
> To create with xa-data-source add command is a workaround
> {code}
> xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]
> {code}
> but most users expect the tree-structure cli and xa-data-source compatible.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10020) Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10020?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10020:
-------------------------------------
This is looking more like a WildFly 14 thing, continuing integration effort on a new topic branch (yeah, would be better if I didn't keep changing the branch name, sorry) via [https://github.com/scottmarlow/wildfly/tree/jpa22_orm53_hibernatetesting_...]. This branch is currently using Infinispan 9.2.2.Final + Hibernate ORM 5.3.0.CR2.
> Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10020
> URL: https://issues.jboss.org/browse/WFLY-10020
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Migrating to 12 with Hibernate Custom slot causes NullPointer Exception.
> https://mvnrepository.com/artifact/org.hibernate/hibernate-orm-modules
> <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.13.Final" />
> 16:12:28,868 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for optoplus
> 16:12:29,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "optoplus-services-ear-1.0.18-SNAPSHOT.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.secondLevelCache.InfinispanCacheDeploymentListener.addCacheDependencies(InfinispanCacheDeploymentListener.java:129)
> at org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener.addCacheDependencies(CacheDeploymentListener.java:111)
> at org.jipijapa.event.impl.internal.Notification.addCacheDependencies(Notification.java:95)
> at org.jboss.as.jpa.hibernate5.HibernateSecondLevelCache.addSecondLevelCacheDependencies(HibernateSecondLevelCache.java:125)
> at org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(HibernatePersistenceProviderAdaptor.java:107)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:538)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:273)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> 16:12:29,155 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"optoplus-services-ear-1.0.18-SNAPSHOT.ear\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"optoplus-services-ear-1.0.18-SNAPSHOT.ear\"
> Caused by: java.lang.NullPointerException"}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months