[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-11720:
-----------------------------------
wildfly-core currently has jboss-marshalling version 2.0.6.Final, which was released in Aug 2018. By looking at the commits for JBMAR-216, they were commits from Jan-Feb 2018. So it appears the fix should already be included in jboss-marshalling 2.0.6.Final (the version used in wildfly-core). I have to admit, not being familiar with jboss-marshalling, I could be totally wrong here.
jboss-ejb-client currently has jboss-marshalling version 2.0.1.Final, which was released in 2017. Could the error be caused by the older version of jboss-marshalling brought in by jboss-ejb-client? We'll need to check how the test app is set up and run.
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Assignee: Cheng Fang
> Priority: Critical
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-11720:
-----------------------------------
[~jkasik], can you provide a reproducer test?
What is the version of jboss-marshalling in use?
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Assignee: Cheng Fang
> Priority: Critical
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11731) IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11731?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11731:
---------------------------------------
Assignee: Jeff Mesnil (was: Brian Stansberry)
> IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-11731
> URL: https://issues.jboss.org/browse/WFLY-11731
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Major
>
> CI failure due to $subject -- ConstantRoleMapperTestCase in https://ci.wildfly.org/viewLog.html?buildId=139312&buildTypeId=WFPR&tab=b...
> {code}
> &#27;[0m&#27;[31m11:45:07,066 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: org.jboss.msc.service.StartException in service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
> at io.smallrye.metrics.MetricsRegistryImpl.register(MetricsRegistryImpl.java:113)
> at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:54)
> at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:38)
> at io.smallrye.metrics.setup.JmxRegistrar.init(JmxRegistrar.java:30)
> at org.wildfly.extension.microprofile.metrics.MetricsRegistrationService.start(MetricsRegistrationService.java:91)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> ... 6 more
> {code}
> I have a feeling this has already been reported but simple searching didn't find it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11731) IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11731:
---------------------------------------
Summary: IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
Key: WFLY-11731
URL: https://issues.jboss.org/browse/WFLY-11731
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Reporter: Brian Stansberry
Assignee: Brian Stansberry
CI failure due to $subject -- ConstantRoleMapperTestCase in https://ci.wildfly.org/viewLog.html?buildId=139312&buildTypeId=WFPR&tab=b...
{code}
&#27;[0m&#27;[31m11:45:07,066 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: org.jboss.msc.service.StartException in service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists
at io.smallrye.metrics.MetricsRegistryImpl.register(MetricsRegistryImpl.java:113)
at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:54)
at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:38)
at io.smallrye.metrics.setup.JmxRegistrar.init(JmxRegistrar.java:30)
at org.wildfly.extension.microprofile.metrics.MetricsRegistrationService.start(MetricsRegistrationService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
... 6 more
{code}
I have a feeling this has already been reported but simple searching didn't find it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4333) async-handler not working / logging.properties incompletely updated
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4333?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4333:
---------------------------------------
It does look like this a bug. However if you use CLI or the management console this issue won't be seen.
Example CLI:
{code}
/subsystem=logging/async-handler=async:add(queue-length=512, overflow-action=BLOCK, subhandlers=[FILE])
/subsystem=logging/root-logger=ROOT:remove-handler(name=FILE)
/subsystem=logging/root-logger=ROOT:add-handler(name=async)
{code}
> async-handler not working / logging.properties incompletely updated
> -------------------------------------------------------------------
>
> Key: WFCORE-4333
> URL: https://issues.jboss.org/browse/WFCORE-4333
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.0.10.Final
> Reporter: Marco Schulze
> Assignee: James Perkins
> Priority: Major
>
> The {{logging.properties}} file which is generated from the {{standalone.xml}} is not correctly updated. When switching to asynchronous logging by renaming the {{"FILE"}} handler to {{"FILE.sync"}} and then introducing an {{async-handler}} named {{"FILE"}} referencing {{"FILE.sync"}} in its {{subhandlers}}, the {{logging.properties}} then lacks the following line:
> {quote}handler.FILE.handlers=FILE.sync{quote}
> I tested this with WildFly 10 and 11, but this bug might affect more (and newer) versions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11729) Add Admin Guide section on using expressions in the configuration
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11729?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11729:
------------------------------------
Description:
Reading the discussion on WFLY-9452 I realized that our docs don't explicitly cover how management model expressions work! Stuff like expression resolution sources, how to determine if an attribute supports and expression, the fact that updating the resolution source does not affect previously resolved values, etc.
It would be good to have something about the ConfigMap scenario covered in the WFLY-9452 discussion as well.
A section under http://docs.wildfly.org/15/Admin_Guide.html#Management_tasks seems like a reasonable spot.
was:
Reading the discussion on WFLY-9452 I realized that our docs don't explicitly cover how management model expressions work! Stuff like expression resolution sources, how to determine if an attribute supports and expression, the fact that updating the resolution source does not affect previously resolved values, etc.
It would be good to have something about the ConfigMap scenario covered in the WFLY-9452 discussion as well.
> Add Admin Guide section on using expressions in the configuration
> -----------------------------------------------------------------
>
> Key: WFLY-11729
> URL: https://issues.jboss.org/browse/WFLY-11729
> Project: WildFly
> Issue Type: Enhancement
> Components: Documentation, Management
> Reporter: Brian Stansberry
> Assignee: Jeff Mesnil
> Priority: Major
>
> Reading the discussion on WFLY-9452 I realized that our docs don't explicitly cover how management model expressions work! Stuff like expression resolution sources, how to determine if an attribute supports and expression, the fact that updating the resolution source does not affect previously resolved values, etc.
> It would be good to have something about the ConfigMap scenario covered in the WFLY-9452 discussion as well.
> A section under http://docs.wildfly.org/15/Admin_Guide.html#Management_tasks seems like a reasonable spot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11730) Do not record Galleon provisioned state and log provisioning time
by Alexey Loubyansky (Jira)
Alexey Loubyansky created WFLY-11730:
----------------------------------------
Summary: Do not record Galleon provisioned state and log provisioning time
Key: WFLY-11730
URL: https://issues.jboss.org/browse/WFLY-11730
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Provisioned state stored in .galleon directory is not really useful in WildFly build and so it can be removed.
Also as previously discussed with [~brian.stansberry] it will be useful to log provisioning time just to keep track how it changes over time.
Both of these changes have already been merged into WildFly Core.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-1169) SQLServerXADataSource IntegratedSecurity not working when adding XA JNDI datasource
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-1169?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-1169:
--------------------------------------
Issue Type: Bug (was: Feature Request)
Component/s: JCA
(was: Server)
Assignee: Stefano Maestri (was: Jason Greene)
My guess here is the problem relates to the fact that the setIntegratedSecurity method takes a boolean not a string.
This would be an Enhancement if no type conversions were possible, but if this works in the non-XA case that implies type conversions are done there so perhaps there is a bug.
> SQLServerXADataSource IntegratedSecurity not working when adding XA JNDI datasource
> -----------------------------------------------------------------------------------
>
> Key: WFLY-1169
> URL: https://issues.jboss.org/browse/WFLY-1169
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Environment: Windows
> Reporter: Vedran Mikulcic
> Assignee: Stefano Maestri
> Priority: Major
>
> When setting the IntegratedSecurity in the XA datasource on JBoss to true, Microsoft's JDBC driver doesn't resolve the 'true' setting to boolean value but throws an error:
> {code}
> java.lang.NoSuchMethodException:
> com.microsoft.sqlserver.jdbc.SQLServerXADataSource.setIntegratedSecurity(java.lang.String)
> {code}
> This is only the issue when using the XA datasource, non XA datasources work normally.
> Steps to reproduce:
> 1. In the JBoss AS configuration\standalone\standalone.xml add a new xa-datasource to JNDI:
> {code}
> <xa-datasource jta="true" jndi-name="java:jboss/datasources/jndiName" pool-name="poolName" enabled="true" use-java-context="true" use-ccm="true">
> <!-- this should work but doesn't -->
> <xa-datasource-property name="IntegratedSecurity">
> true
> </xa-datasource-property>
> <xa-datasource-property name="ServerName">
> localhost
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> MyDbName
> </xa-datasource-property>
> <xa-datasource-property name="SelectMethod">
> cursor
> </xa-datasource-property>
> <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
> <driver>sqljdbc</driver>
> <xa-pool>
> <is-same-rm-override>false</is-same-rm-override>
> </xa-pool>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"/>
> </validation>
> </xa-datasource>
> {code}
> 2. Restart JBoss AS
> 3. Try to execute a query using the configured JNDI connection:
> {code}
> InitialContext ic = new InitialContext();
> DataSource ds = (DataSource) ic.lookup("java:jboss/datasources/jndiName");
> Connection conn = null;
> try {
> conn = ds.getConnection();
>
> // try to execute something
> CallableStatement stmt = conn.prepareCall("{? = call some_stored_procedure()}");
> stmt.execute();
> } finally {
> if (conn != null)
> conn.close();
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months