[JBoss JIRA] (DROOLS-749) Events deserialization is broken
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-749?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-749:
------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1205666|https://bugzilla.redhat.com/show_bug.cgi?id=1205666] from MODIFIED to ON_QA
> Events deserialization is broken
> --------------------------------
>
> Key: DROOLS-749
> URL: https://issues.jboss.org/browse/DROOLS-749
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 6.3.0.Beta1
>
>
> When a KieSession is deserialized the events present in the old serialized session are reasserted into the new session. Then if one of this event causes a scheduler to be immediately triggered this is done in a callback out of the main evaluation loop. This implies that the left tuples resulting from the triggering of the scheduler aren't propagated to the sink of the TimerNode which created the scheduler itself. This missing propagation can, in some circumstances, cause a NullPointerException like the following:
> {code}
> java.lang.NullPointerException
> at org.drools.core.phreak.PhreakTimerNode.doLeftDeletes(PhreakTimerNode.java:197)
> at org.drools.core.phreak.PhreakTimerNode.doNode(PhreakTimerNode.java:63)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:364)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:163)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:118)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:254)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:108)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1022)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1352)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1318)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1301)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1280)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4490) Hard deployment using wildfly-maven-plugin
by Hitesh Saxena (JIRA)
[ https://issues.jboss.org/browse/WFLY-4490?page=com.atlassian.jira.plugin.... ]
Hitesh Saxena updated WFLY-4490:
--------------------------------
Fix Version/s: (was: No Release)
> Hard deployment using wildfly-maven-plugin
> ------------------------------------------
>
> Key: WFLY-4490
> URL: https://issues.jboss.org/browse/WFLY-4490
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 8.2.0.Final
> Environment: OS- WIndows7 64Bit, Eclipse Luna Service Release 1(4.4.1), Maven 3.1.1
> Reporter: Hitesh Saxena
> Assignee: Paul Gier
> Priority: Critical
> Labels: jboss
>
> We are migrating from JBOSS6 to Wildfly8. We are a new issue which could not be found anywhere in forums,so posting this question here.
>
> For hard deployment we were using the below configuration in pom.xml which actually copy and deploy ear file from ${JBOSS_HOME}/server/default/deploy directory of JBOSS6.
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jboss-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>deploy_ear</id>
> <phase>pre-integration-test</phase>
> <goals>
> <goal>hard-deploy</goal>
> </goals>
> <configuration>
> <deploySubDir>./</deploySubDir>
> <fileName>target/${project.build.finalName.full}</fileName>
> <unpack>true</unpack>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> But now as per wildlfy documents, we are using wildfly-maven-plugin to do the above and configured as below:
>
> <plugin>
> <groupId>org.wildfly.plugins</groupId>
> <artifactId>wildfly-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>deploy_ear</id>
> <phase>package</phase>
> <goals>
> <goal>deploy</goal>
> </goals>
> <configuration>
> <skip>false</skip>
> <filename>test.ear</filename>
> <targetDir>${project_directory}\target</targetDir>
> <domain>standalone</domain>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> But this maven configuration deploys into ${JBOSS_HOME}/standalone/data/content and also make an entry into standalone-full-ha.xml file as below
> <deployments>
> <deployment name="test.ear" runtime-name="test.ear">
> <content sha1="697809d5ebb7658fd7045dd6a8c41542cd3a0e02"/>
> </deployment>
> </deployments>
>
> Ideally it should copy and deploy from into ${JBOSS_HOME}/standalone/deployments folder.
>
> I tried to see the parameters from wildfly documents but could not get any parameter which can do the expected.
> reference: WildFly Maven Plugin - wildfly:deploy
>
> Help will be highly appreciated as we are struck into this stage.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4490) Hard deployment using wildfly-maven-plugin
by Hitesh Saxena (JIRA)
Hitesh Saxena created WFLY-4490:
-----------------------------------
Summary: Hard deployment using wildfly-maven-plugin
Key: WFLY-4490
URL: https://issues.jboss.org/browse/WFLY-4490
Project: WildFly
Issue Type: Bug
Components: Build System
Affects Versions: 8.2.0.Final
Environment: OS- WIndows7 64Bit, Eclipse Luna Service Release 1(4.4.1), Maven 3.1.1
Reporter: Hitesh Saxena
Assignee: Paul Gier
Priority: Critical
Fix For: No Release
We are migrating from JBOSS6 to Wildfly8. We are a new issue which could not be found anywhere in forums,so posting this question here.
For hard deployment we were using the below configuration in pom.xml which actually copy and deploy ear file from ${JBOSS_HOME}/server/default/deploy directory of JBOSS6.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-maven-plugin</artifactId>
<executions>
<execution>
<id>deploy_ear</id>
<phase>pre-integration-test</phase>
<goals>
<goal>hard-deploy</goal>
</goals>
<configuration>
<deploySubDir>./</deploySubDir>
<fileName>target/${project.build.finalName.full}</fileName>
<unpack>true</unpack>
</configuration>
</execution>
</executions>
</plugin>
But now as per wildlfy documents, we are using wildfly-maven-plugin to do the above and configured as below:
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<executions>
<execution>
<id>deploy_ear</id>
<phase>package</phase>
<goals>
<goal>deploy</goal>
</goals>
<configuration>
<skip>false</skip>
<filename>test.ear</filename>
<targetDir>${project_directory}\target</targetDir>
<domain>standalone</domain>
</configuration>
</execution>
</executions>
</plugin>
But this maven configuration deploys into ${JBOSS_HOME}/standalone/data/content and also make an entry into standalone-full-ha.xml file as below
<deployments>
<deployment name="test.ear" runtime-name="test.ear">
<content sha1="697809d5ebb7658fd7045dd6a8c41542cd3a0e02"/>
</deployment>
</deployments>
Ideally it should copy and deploy from into ${JBOSS_HOME}/standalone/deployments folder.
I tried to see the parameters from wildfly documents but could not get any parameter which can do the expected.
reference: WildFly Maven Plugin - wildfly:deploy
Help will be highly appreciated as we are struck into this stage.
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4198) NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4198?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski commented on WFLY-4198:
------------------------------------------
I did not apply this patch. Logging should not hide whats happening( obscure MDC contract ) - it should work on what it gets. PR is in the pool
> NullPointerException in LogDiagnosticContextRecoveryInterceptor when calling an asynchronous EJB
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-4198
> URL: https://issues.jboss.org/browse/WFLY-4198
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.0.Final
> Reporter: Sergiy Barlabanov
> Assignee: Bartosz Baranowski
> Attachments: patch.diff
>
>
> When trying to call an asynchronous EJB in a Web application using slf4j (1.7.5+) & logback(1.0.13+) for logging the following NullPointerException occurs (see below).
> The problem is in the line 67 of LogDiagnosticContextRecoveryInterceptor class, when it tries to access MDC map, which is null. According to SLF4J API the copy of MDC map may be null: see the javadoc of org.slf4j.MDC#getCopyOfContextMap.
> So LogDiagnosticContextRecoveryInterceptor or org.jboss.logging.Slf4jLoggerProvider have to check the map for null.
> Currently there is no workaround for that :(.
> {noformat}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.interceptors.LogDiagnosticContextRecoveryInterceptor.processInvocation(LogDiagnosticContextRecoveryInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.as.ejb3.component.interceptors.AsyncFutureInterceptorFactory$1$2.runInvocation(AsyncFutureInterceptorFactory.java:97)
> at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4489) NPE on missing name of <distributed-workmanager>
by Philippe Marschall (JIRA)
Philippe Marschall created WFLY-4489:
----------------------------------------
Summary: NPE on missing name of <distributed-workmanager>
Key: WFLY-4489
URL: https://issues.jboss.org/browse/WFLY-4489
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Philippe Marschall
Assignee: Jesper Pedersen
When the name attribute of {{<distributed-workmanager>}} is missing instead of a descriptive log message you get a {{NullPointerException}}. The issue is that the {{StringBuilder}} constructor is called with the value of the name attribute instead of the name of the name attribute ("name").
Something like this:
{code}
<subsystem xmlns="urn:jboss:domain:jca:2.0">
<distributed-workmanager/>
</subsystem>
{code}
Will produce a stack trace like this:
{code}
[org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
at org.jboss.as.server.ServerService.boot(ServerService.java:347)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at java.lang.StringBuilder.<init>(StringBuilder.java:112)
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.parseDistributedWorkManager(JcaExtension.java:560)
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:367)
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:119)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1199)
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:457)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:144)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:106)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
{code}
After the patch the stack trace looks like this:
{code}
org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.as.server.ServerService.boot(ServerService.java:347) [wildfly-server-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) [wildfly-controller-1.0.0.Beta2.jar:1.0.0.Beta2]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[274,13]
Message: WFLYCTL0133: Missing required attribute(s): name
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.parseDistributedWorkManager(JcaExtension.java:563)
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:368)
at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:120)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1199) [wildfly-server-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:457) [wildfly-server-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:144) [wildfly-server-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:106) [wildfly-server-1.0.0.Beta2.jar:1.0.0.Beta2]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-1.0.0.Beta2.jar:1.0.0.Beta2]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-623) ModelControllerClient.Factory lacks some variants
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFCORE-623?page=com.atlassian.jira.plugin... ]
Ladislav Thon reassigned WFCORE-623:
------------------------------------
Assignee: Brian Stansberry (was: Ladislav Thon)
> ModelControllerClient.Factory lacks some variants
> -------------------------------------------------
>
> Key: WFCORE-623
> URL: https://issues.jboss.org/browse/WFCORE-623
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Beta2
> Reporter: Ladislav Thon
> Assignee: Brian Stansberry
>
> In the {{ModelControllerClient.Factory}} class, each factory method in fact has two varians: with a {{protocol}} as a first parameter, and without it. There are two exceptions -- two methods are lacking a {{protocol}}-less variant:
> - {{ModelControllerClient create(final String protocol, final String hostName, final int port, final CallbackHandler handler, final SSLContext sslContext, final int connectionTimeout, final Map<String, String> saslOptions)}}
> - {{ModelControllerClient create(final String protocol, final String hostName, final int port, final CallbackHandler handler, final SSLContext sslContext, final int connectionTimeout, final Map<String, String> saslOptions, final String clientBindAddress)}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-623) ModelControllerClient.Factory lacks some variants
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFCORE-623?page=com.atlassian.jira.plugin... ]
Ladislav Thon updated WFCORE-623:
---------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/593, https://github.com/wildfly/wildfly-core/pull/600 (was: https://github.com/wildfly/wildfly-core/pull/593)
> ModelControllerClient.Factory lacks some variants
> -------------------------------------------------
>
> Key: WFCORE-623
> URL: https://issues.jboss.org/browse/WFCORE-623
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Beta2
> Reporter: Ladislav Thon
> Assignee: Ladislav Thon
>
> In the {{ModelControllerClient.Factory}} class, each factory method in fact has two varians: with a {{protocol}} as a first parameter, and without it. There are two exceptions -- two methods are lacking a {{protocol}}-less variant:
> - {{ModelControllerClient create(final String protocol, final String hostName, final int port, final CallbackHandler handler, final SSLContext sslContext, final int connectionTimeout, final Map<String, String> saslOptions)}}
> - {{ModelControllerClient create(final String protocol, final String hostName, final int port, final CallbackHandler handler, final SSLContext sslContext, final int connectionTimeout, final Map<String, String> saslOptions, final String clientBindAddress)}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months