[JBoss JIRA] (WFLY-1469) Mail Service should be restarted after server is added/modifed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1469?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1469:
------------------------------
Summary: Mail Service should be restarted after server is added/modifed (was: Mail Service does not honor remote socket binding without config reload)
> Mail Service should be restarted after server is added/modifed
> --------------------------------------------------------------
>
> Key: WFLY-1469
> URL: https://issues.jboss.org/browse/WFLY-1469
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Mail
> Affects Versions: 8.0.0.Alpha1
> Reporter: Andrew Rubinger
> Assignee: Tomaz Cerar
>
> I'm finding that the mail service is not honoring the association with a specific outbound socket binding.
> Configuration of Mail Session and Socket Binding:
> {code}[standalone@localhost:9990 /] /subsystem=mail/mail-session=java\:jboss\/mail\/ALR/server=smtp:read-resource
> {
> "outcome" => "success",
> "result" => {
> "outbound-socket-binding-ref" => "mail-smtp-25000",
> "password" => undefined,
> "ssl" => false,
> "tls" => false,
> "username" => undefined
> }
> }
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=mail-smtp-25000:read-resource(recursive="true")
> {
> "outcome" => "success",
> "result" => {
> "fixed-source-port" => false,
> "host" => "localhost",
> "port" => 25000,
> "source-interface" => undefined,
> "source-port" => undefined
> }
> }{code}
> Code to inject the Mail Session:
> {code}@Resource(lookup = "java:jboss/mail/ALR")
> private Session mailSession;{code}
> This injection succeeds, as I'd expect based on the tests:
> https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi...
> However, when using this to send mail, getting the default port of "25", not "25000" as I've specified in the config:
> {code}[0m[0m23:54:17,102 INFO [stdout] (default task-1) DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Oracle]
> [0m[0m23:54:17,103 INFO [stdout] (default task-1) DEBUG SMTP: useEhlo true, useAuth false
> [0m[0m23:54:17,103 INFO [stdout] (default task-1) DEBUG SMTP: trying to connect to host "localhost", port 25, isSSL false{code}
> I don't see anything in the testsuite attempting to broker mail through a non-default configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2499) JMSBridge FailureHandler does not load from specified module
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-2499:
---------------------------------
Summary: JMSBridge FailureHandler does not load from specified module
Key: WFLY-2499
URL: https://issues.jboss.org/browse/WFLY-2499
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS
Affects Versions: 8.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.CR1
If an error occurs and the JMS bridge tries to reconnect to the JMS provider to look up the JMS resources from its FailureHandler, it fails with the exception:
Stack trace:
{noformat}
10:37:02,546 INFO [org.hornetq.jms.server] (pool-3-thread-3) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 1,000 ms
10:37:03,547 WARN [org.hornetq.jms.server] (pool-3-thread-3) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.apache.qpid.jndi.PropertiesFileInitialContextFactory from classloader ModuleClassLoader for Module "org.hornetq:main" from local module loader @ac44b88 (finder: local module finder @5d3ad33d (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
at org.jboss.as.naming.InitialContextFactoryBuilder.createInitialContextFactory(InitialContextFactoryBuilder.java:64)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:681) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.init(InitialContext.java:240) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.<init>(InitialContext.java:214) [rt.jar:1.6.0_24]
at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1222) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1460) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2000(JMSBridgeImpl.java:83) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2049) [hornetq-jms-server.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
{noformat}
The issue is that the ExecutorService executing the FailureHandler is created when the JMSBridge is instantiated and will not use the ClassLoader from the specified module that gives access to the JMS provider's classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (DROOLS-2) Knowledge Agent resets the Rules that are using Negative Patterns to delaying with Fusion
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2?page=com.atlassian.jira.plugin.s... ]
Mario Fusco reassigned DROOLS-2:
--------------------------------
Assignee: Mario Fusco
> Knowledge Agent resets the Rules that are using Negative Patterns to delaying with Fusion
> -----------------------------------------------------------------------------------------
>
> Key: DROOLS-2
> URL: https://issues.jboss.org/browse/DROOLS-2
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Adrian Paredes
> Assignee: Mario Fusco
> Labels: Guvnor, KnowledgeAgent, KnowledgeBase, TemporalOperators
>
> If I had a rule of this style in progress:
> rule "Basic Rule"
> dialect 'mvel'
> when
> $eventA: EventA($aId: id) from entry-point "time stream"
> not EventB($aId == id, this after [0s,5m] $eventA) from entry-point "time stream"
> then
> System.out.println("Event A " + $aId + " at " + $eventA.timestamp);
> end
> And this rule had been activated 2 minutes ago... When the KnowledgeAgent updates the StatefulKnowledgeSession, after someone updates the KnowledgeBase from Guvnor, the time intervals resets to zero, because all the activated rules are canceled and activated again later.
> The result is that the System.out fires 7 minutes after the event was inserted... 2 minutes later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (DROOLS-2) Knowledge Agent resets the Rules that are using Negative Patterns to delaying with Fusion
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2?page=com.atlassian.jira.plugin.s... ]
Mario Fusco resolved DROOLS-2.
------------------------------
Resolution: Cannot Reproduce Bug
> Knowledge Agent resets the Rules that are using Negative Patterns to delaying with Fusion
> -----------------------------------------------------------------------------------------
>
> Key: DROOLS-2
> URL: https://issues.jboss.org/browse/DROOLS-2
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Adrian Paredes
> Assignee: Mario Fusco
> Labels: Guvnor, KnowledgeAgent, KnowledgeBase, TemporalOperators
>
> If I had a rule of this style in progress:
> rule "Basic Rule"
> dialect 'mvel'
> when
> $eventA: EventA($aId: id) from entry-point "time stream"
> not EventB($aId == id, this after [0s,5m] $eventA) from entry-point "time stream"
> then
> System.out.println("Event A " + $aId + " at " + $eventA.timestamp);
> end
> And this rule had been activated 2 minutes ago... When the KnowledgeAgent updates the StatefulKnowledgeSession, after someone updates the KnowledgeBase from Guvnor, the time intervals resets to zero, because all the activated rules are canceled and activated again later.
> The result is that the System.out fires 7 minutes after the event was inserted... 2 minutes later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (DROOLS-57) Split packages: OSGi packaging issue/conflict with Kie API & Kie Internal
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-57?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-57.
-------------------------------
Fix Version/s: 6.0.0.Final
Resolution: Done
> Split packages: OSGi packaging issue/conflict with Kie API & Kie Internal
> -------------------------------------------------------------------------
>
> Key: DROOLS-57
> URL: https://issues.jboss.org/browse/DROOLS-57
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Charles Moulliard
> Assignee: Mario Fusco
> Fix For: 6.0.0.Final
>
>
> Due to overlap of packages between module kie-api & kie-internal, some classes of kie-internal are not found by kie-api
> example :
> Caused by: java.lang.ClassNotFoundException: org.kie.KieBaseConfiguration not found by org.kie.api [88] = KIE API
> The class org.kie.KieBaseConfiguration should be exported by the bundle kie-internal and imported by kie-api on OSGI platform and this is not the case as both bundles import/export same package org.kie
> {code}
> Bundle 88 = kie api & bundle 89 = kie internal
> karaf@root> packages:exports 88
> ID Packages
> 88 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.command; version=6.0.0.SNAPSHOT
> 88 org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> 88 org.kie.definition; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.process; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.event.process; version=6.0.0.SNAPSHOT
> 88 org.kie.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.help; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.management; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.type; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.io; version=6.0.0.SNAPSHOT
> 88 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 88 org.kie.builder.model; version=6.0.0.SNAPSHOT
> 88 org.kie.time; version=6.0.0.SNAPSHOT
> 88 org.kie; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.process; version=6.0.0.SNAPSHOT
> 88 org.kie.logger; version=6.0.0.SNAPSHOT
> 88 org.kie.builder; version=6.0.0.SNAPSHOT
> 88 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 88 org.kie.cdi; version=6.0.0.SNAPSHOT
> 88 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 88 org.kie.osgi.api; version=6.0.0.SNAPSHOT
> 88 org.kie.event; version=6.0.0.SNAPSHOT
> karaf@root> packages:exports 89
> ID Packages
> 89 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 89 org.kie.command; version=6.0.0.SNAPSHOT
> 89 org.kie.internal.utils; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime.helper; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent; version=6.0.0.SNAPSHOT
> 89 org.kie.definition; version=6.0.0.SNAPSHOT
> 89 org.kie.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.help; version=6.0.0.SNAPSHOT
> 89 org.kie.io; version=6.0.0.SNAPSHOT
> 89 org.kie.event.io; version=6.0.0.SNAPSHOT
> 89 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent.test; version=6.0.0.SNAPSHOT
> 89 org.kie.agent.conf; version=6.0.0.SNAPSHOT
> 89 org.kie; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime; version=6.0.0.SNAPSHOT
> 89 org.kie.simulation; version=6.0.0.SNAPSHOT
> 89 org.kie.event.knowledgeagent; version=6.0.0.SNAPSHOT
> 89 org.kie.logger; version=6.0.0.SNAPSHOT
> 89 org.kie.builder; version=6.0.0.SNAPSHOT
> 89 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 89 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 89 org.kie.agent; version=6.0.0.SNAPSHOT
> 89 org.kie.event; version=6.0.0.SNAPSHOT
> 89 org.kie.task.service; version=6.0.0.SNAPSHOT
> karaf@root> packages:imports 89
> System Bundle (0): javax.xml.bind; version=2.2.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.7.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.6.6
> OPS4J Pax Logging - API (4): org.slf4j; version=1.5.11
> OPS4J Pax Logging - API (4): org.slf4j; version=1.4.3
> Apache ServiceMix :: Bundles :: xstream (57): com.thoughtworks.xstream; version=1.4.3
> KIE API (88): org.kie.event.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.command; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.help; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.management; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.type; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.io; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.marshalling; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder.model; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.time; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.logger; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.concurrent; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.cdi; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.osgi.api; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event; version=6.0.0.SNAPSHOT
> camel-core (229): org.apache.camel.spi; version=2.10.3
> camel-core (229): org.apache.camel; version=2.10.3
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months