[JBoss JIRA] (HIBERNATE-157) InvocationTargetException when opening hibernate structure
by Amenel Voglozin (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-157?page=com.atlassian.jira.plu... ]
Amenel Voglozin commented on HIBERNATE-157:
-------------------------------------------
[~koen.aers] Have you had some time to look into the example project I've attached?
> InvocationTargetException when opening hibernate structure
> ----------------------------------------------------------
>
> Key: HIBERNATE-157
> URL: https://issues.jboss.org/browse/HIBERNATE-157
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: MacOS10.11.6(El Capitan), Eclipse4.6.0(Neon)
> Reporter: Yasuyuki Inoue
> Assignee: Koen Aers
> Attachments: hibernate-157.zip
>
>
> InvocationTargetException occured when opening existing Hibernate structure.
> !ENTRY org.hibernate.eclipse.console 4 2 2016-09-06 15:19:57.154
> !MESSAGE java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2016-09-06 15:19:57.154
> !MESSAGE java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> !STACK 0
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:78)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadata(MetadataHelper.java:16)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:167)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:105)
> at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:272)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildMappings(ConsoleConfiguration.java:270)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:44)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:231)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:72)
> ... 12 more
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.JPAConfiguration.getMetadata(JPAConfiguration.java:36)
> ... 17 more
> !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2016-09-06 15:19:57.154
> !MESSAGE java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> !STACK 0
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:78)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadata(MetadataHelper.java:16)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:167)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:105)
> at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:272)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildMappings(ConsoleConfiguration.java:270)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:44)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:231)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:72)
> ... 12 more
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.JPAConfiguration.getMetadata(JPAConfiguration.java:36)
> ... 17 more
> !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2016-09-06 15:19:57.154
> !MESSAGE java.lang.reflect.InvocationTargetException: <no message>
> !STACK 0
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:72)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadata(MetadataHelper.java:16)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:167)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:105)
> at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:272)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildMappings(ConsoleConfiguration.java:270)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:44)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:231)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.JPAConfiguration.getMetadata(JPAConfiguration.java:36)
> ... 17 more
> Root exception:
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.JPAConfiguration.getMetadata(JPAConfiguration.java:36)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:72)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadata(MetadataHelper.java:16)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:167)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:105)
> at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:272)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildMappings(ConsoleConfiguration.java:270)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:44)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:231)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2016-09-06 15:19:57.154
> !MESSAGE java.lang.NullPointerException: <no message>
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.JPAConfiguration.getMetadata(JPAConfiguration.java:36)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadataFromMethod(MetadataHelper.java:72)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.MetadataHelper.getMetadata(MetadataHelper.java:16)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.getMetadata(ConfigurationFacadeImpl.java:167)
> at org.jboss.tools.hibernate.runtime.v_5_1.internal.ConfigurationFacadeImpl.buildMappings(ConfigurationFacadeImpl.java:105)
> at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:272)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildMappings(ConsoleConfiguration.java:270)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:44)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:231)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-1438) Elytron integration with logging subsystem
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1438?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-1438:
---------------------------------------
Currently the default {{syslog-handler}} is fairly limited. It can however be defined as a {{custom-handler}}. However the {{syslog-handler}} management resource should be redesigned, it's the goal of https://issues.jboss.org/browse/WFCORE-109. Once we do that we should consider integration with Elytron.
However the syslog-handler for the audit-logger does expose some TLS abilities. This may be included in another JIRA, but something worth mentioning.
> Elytron integration with logging subsystem
> ------------------------------------------
>
> Key: WFCORE-1438
> URL: https://issues.jboss.org/browse/WFCORE-1438
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: Darran Lofthouse
> Assignee: James Perkins
> Fix For: 3.0.0.Alpha18
>
>
> This is primarily an investigation task to start with, Logging can use syslog, Syslog access can be protected with TLS, Elytron is providing unified SSL configuration - do we need to bring these together.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7858) The batch subsystem configuration doesn't validate in standalone-elytron.xml profile
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-7858?page=com.atlassian.jira.plugin.... ]
James Perkins moved JBEAP-8137 to WFLY-7858:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7858 (was: JBEAP-8137)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Batch
Security
(was: Batch)
(was: Security)
Affects Version/s: (was: 7.1.0.DR10)
> The batch subsystem configuration doesn't validate in standalone-elytron.xml profile
> ------------------------------------------------------------------------------------
>
> Key: WFLY-7858
> URL: https://issues.jboss.org/browse/WFLY-7858
> Project: WildFly
> Issue Type: Bug
> Components: Batch, Security
> Reporter: James Perkins
> Assignee: James Perkins
>
> The {{security-domain}} element in {{batch-jberet}} subsystem is not placed correctly in {{standalone-elytron.xml}} profile.
> The current configuration in the profile is:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:batch-jberet:2.0">
> <default-job-repository name="in-memory"/>
> <security-domain name="ApplicationDomain"/>
> <default-thread-pool name="batch"/>
> <job-repository name="in-memory">
> <in-memory/>
> </job-repository>
> <thread-pool name="batch">
> <max-threads count="10"/>
> <keepalive-time time="30" unit="seconds"/>
> </thread-pool>
> </subsystem>
> {code}
> And XSD ({{wildfly-batch-jberet_2_0.xsd}}) says:
> {code:xml}
> <xs:sequence>
> <xs:element name="default-job-repository" type="namedType" minOccurs="1" maxOccurs="1">
> </xs:element>
> <xs:element name="default-thread-pool" type="namedType" minOccurs="1" maxOccurs="1">
> </xs:element>
> <xs:element name="restart-jobs-on-resume" type="booleanType" minOccurs="0" maxOccurs="1">
> </xs:element>
> <xs:element name="security-domain" type="namedType" minOccurs="0" maxOccurs="1">
> </xs:element>
> <xs:element name="job-repository" type="job-repositoryType" minOccurs="1" maxOccurs="unbounded"/>
> <xs:element name="thread-pool" type="thread-poolType" minOccurs="1" maxOccurs="unbounded"/>
> <xs:element name="thread-factory" type="threads:thread-factory" minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> {code}
> As a result the profile XML validation ends with error:
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'security-domain'. One of '{"urn:jboss:domain:batch-jberet:2.0":default-thread-pool}' is expected.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh
by Dennis Reed (JIRA)
Dennis Reed created WFCORE-2160:
-----------------------------------
Summary: Incorrect JBOSS_HOME warning in vault.sh
Key: WFCORE-2160
URL: https://issues.jboss.org/browse/WFCORE-2160
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Affects Versions: 3.0.0.Alpha16
Reporter: Dennis Reed
Assignee: Tomaz Cerar
Priority: Minor
vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly.
SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd`
if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then
The check will always fail because of the incorrect "/..", which should be removed.
The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2089) Infinite wildfly boot on StartException in service start
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-2089:
-----------------------------------------
Assignee: ehsavoie Hugonnet (was: Brian Stansberry)
> Infinite wildfly boot on StartException in service start
> --------------------------------------------------------
>
> Key: WFCORE-2089
> URL: https://issues.jboss.org/browse/WFCORE-2089
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Jan Kalina
> Assignee: ehsavoie Hugonnet
> Priority: Blocker
> Attachments: threads-2.txt, threads.txt
>
>
> Following exception (and probably similar too) will cause wildfly frozing during start. Visible especially during integration tests (which will never ends), but reproducible directly too (see steps).
> {code:java}
> 15:59:37,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185)
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> *Update:* This problem with infinite boot will occure everytime the start() method of some service throws StartException(). Not an Elytron problem.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7857) Unable to create http-acceptors with same name for 2 different server
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-7857?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil moved JBEAP-8133 to WFLY-7857:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7857 (was: JBEAP-8133)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
Affects Version/s: 10.1.0.Final
(was: 7.0.3.GA)
> Unable to create http-acceptors with same name for 2 different server
> ---------------------------------------------------------------------
>
> Key: WFLY-7857
> URL: https://issues.jboss.org/browse/WFLY-7857
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.1.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> To reproduce, create 2 messaging-activemq's server with the same configuration of http-acceptor:
> {code}
> <server name="default">
> ....
> <http-acceptor name="http-acceptor" http-listener="default"/>
> ...
> </server>
> <server name="other">
> ...
> <http-acceptor name="http-acceptor" http-listener="default"/>
> ...
> </server>
> {code}
> WildFly starts with the error:
> {code}
> 16:24:47,503 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "other"),
> ("http-acceptor" => "http-acceptor")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.messaging-activemq.http-upgrade-service.http-acceptor is already registered
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-6936) RebindTestCase fails with security manager
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFLY-6936?page=com.atlassian.jira.plugin.... ]
Ingo Weiss updated WFLY-6936:
-----------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/9460 (was: https://github.com/wildfly-security/wildfly-elytron/pull/598, https://github.com/wildfly/wildfly-core/pull/2010, https://github.com/wildfly/wildfly/pull/9460)
> RebindTestCase fails with security manager
> ------------------------------------------
>
> Key: WFLY-6936
> URL: https://issues.jboss.org/browse/WFLY-6936
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Jan Tymel
> Assignee: Ingo Weiss
> Fix For: 11.0.0.Alpha1
>
>
> *org.jboss.as.test.integration.naming.RebindTestCase#testRebinding*
> *org.jboss.as.test.integration.naming.RebindTestCase#testRebindingLookup*
> *org.jboss.as.test.integration.naming.RebindTestCase#testRebindingObjectFactory*
> {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.naming.RebindTestCase#testRebinding -Dsecurity.manager}}
> Fails with:
> {code}
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.jboss.remoting3.security.RemotingPermission" "createEndpoint")" in code source "(vfs:/content/RebindTestCase.jar <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:85)
> at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:120)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:64)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:139)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:114)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 145 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1399) Comparison of DRL changes should not consider spaces during incremental compilation
by Marcus Carvalho (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1399?page=com.atlassian.jira.plugi... ]
Marcus Carvalho updated DROOLS-1399:
------------------------------------
Comment: was deleted
(was: Hi Matteo, please confirm if I am correct. In that pull request, when a drl file is changed with blank spaces the matched rule will not be fired again after a incremental compilation. Am I right?
)
> Comparison of DRL changes should not consider spaces during incremental compilation
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1399
> URL: https://issues.jboss.org/browse/DROOLS-1399
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Beta5
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Priority: Minor
>
> During incremental compilation the equivalent DRL file contains only a modification with a new space character in a non-rule, non-resource line. Currently, this triggers the incremental compilation to rebuild all the resources associated in that DRL file anyway. Consequently, a rule in that DRL file might be actually UNchanged; but following the explanation above, it will match and fire again, like it's a new/modified rule.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2159) worker=default:read-resource(include-runtime) wrong values in domain mode
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2159?page=com.atlassian.jira.plugi... ]
Claudio Miranda updated WFCORE-2159:
------------------------------------
Description:
In domain mode the following command assigns error message to values.
{code}
/profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
{
"outcome" => "success",
"result" => {
"io-threads" => "WFLYIO006: no metrics available",
"stack-size" => "WFLYIO006: no metrics available",
"task-keepalive" => "WFLYIO006: no metrics available",
"task-max-threads" => "WFLYIO006: no metrics available",
"server" => undefined
}
}
{code}
it should show configured values when it is executed on profile
Also, may be related
{code}
/subsystem=io/worker=test123:add(io-threads=11,stack-size=12,task-keepalive=13,task-max-threads=14)
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=io/worker=test123:read-resource
{
"outcome" => "success",
"result" => {
"io-threads" => undefined,
"stack-size" => undefined,
"task-keepalive" => undefined,
"task-max-threads" => undefined,
"server" => undefined
}
}
{code}
was:
In domain mode the following command assigns error message to values.
{code}
/profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
{
"outcome" => "success",
"result" => {
"io-threads" => "WFLYIO006: no metrics available",
"stack-size" => "WFLYIO006: no metrics available",
"task-keepalive" => "WFLYIO006: no metrics available",
"task-max-threads" => "WFLYIO006: no metrics available",
"server" => undefined
}
}
{code}
it should show configured values when it is executed on profile
> worker=default:read-resource(include-runtime) wrong values in domain mode
> -------------------------------------------------------------------------
>
> Key: WFCORE-2159
> URL: https://issues.jboss.org/browse/WFCORE-2159
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Reporter: Claudio Miranda
> Assignee: Tomaz Cerar
>
> In domain mode the following command assigns error message to values.
> {code}
> /profile=full-ha/subsystem=io/worker=default:read-resource(include-runtime)
> {
> "outcome" => "success",
> "result" => {
> "io-threads" => "WFLYIO006: no metrics available",
> "stack-size" => "WFLYIO006: no metrics available",
> "task-keepalive" => "WFLYIO006: no metrics available",
> "task-max-threads" => "WFLYIO006: no metrics available",
> "server" => undefined
> }
> }
> {code}
> it should show configured values when it is executed on profile
> Also, may be related
> {code}
> /subsystem=io/worker=test123:add(io-threads=11,stack-size=12,task-keepalive=13,task-max-threads=14)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=io/worker=test123:read-resource
> {
> "outcome" => "success",
> "result" => {
> "io-threads" => undefined,
> "stack-size" => undefined,
> "task-keepalive" => undefined,
> "task-max-threads" => undefined,
> "server" => undefined
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months