[JBoss JIRA] (WFLY-4259) ClassNotFound exception when connecting a remote HornetQ client over SSL
by Jon Kranes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4259?page=com.atlassian.jira.plugin.... ]
Jon Kranes updated WFLY-4259:
-----------------------------
Workaround Description: The issue can be worked around in 8.2.0.Final by modifying the module.xml file as noted in the issue description. However this workaround does not seem to fix the issue in 8.1.0.Final (was: The issue can be worked around in 8.2.0.Final by modifying the module.xml file as noted above. However this workaround does not seem to fix the issue in 8.1.0.Final)
> ClassNotFound exception when connecting a remote HornetQ client over SSL
> ------------------------------------------------------------------------
>
> Key: WFLY-4259
> URL: https://issues.jboss.org/browse/WFLY-4259
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Jon Kranes
> Assignee: Jeff Mesnil
>
> When using HornetQ with a remote client connecting with SSL (using a netty-connector with ssl-enabled=true) the server throws an exception in ModuleClassLoader when the client attempts to connect. The exception is:
> java.lang.ClassNotFoundException: javax.net.SSLException
> After doing some investigation I was able to resolve this issue by adding a dependency in the io.netty module.xml file
> <dependencies>
> <module name="javax.api"/>
> <dependencies
> Without this dependency, it appear that Netty is unable to load classes that it needs from javax.net.ssl.
> NOTE: adding this dependency resolves the issue in Wildfly 8.2.0.Final. However, it does NOT resolve the issue in 8.1.0.Final. Even after adding this dependency I still got the ClassNotFoundException.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4259) ClassNotFound exception when connecting a remote HornetQ client over SSL
by Jon Kranes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4259?page=com.atlassian.jira.plugin.... ]
Jon Kranes updated WFLY-4259:
-----------------------------
Steps to Reproduce:
Configure Wildfly to use HornetQ messaging similar to the following:
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<security-enabled>false</security-enabled>
<connectors>
<netty-connector name="netty-ssl-connector" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="xxx"/>
<param key="host" value="localhost"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<acceptors>
<netty-acceptor name="netty-ssl-acceptor" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="password"/>
<param key="host" value="localhost"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<jms-connection-factories>
<connection-factory name="ConnectionFactory">
<connectors>
<connector-ref connector-name="netty-ssl-connector"/>
</connectors>
<entries>
<entry name="java:/jboss/exported/jms/ConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
</hornetq-server>
Create a remote JMS client to connect to the server using the exported connection obtained from JNDI (using http-remoting). When the client attempts to connect the server throws the ClassNotFound exception mentioned above and the connection fails.
was:
Configure Wildfly to use HornetQ messaging similar to the following:
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<security-enabled>false</security-enabled>
<connectors>
<netty-connector name="netty-ssl-connector" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="xxx"/>
<param key="host" value="localhost"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<acceptors>
<netty-acceptor name="netty-ssl-acceptor" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="password"/>
<param key="host" value="localhost"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<jms-connection-factories>
<connection-factory name="ConnectionFactory">
<connectors>
<connector-ref connector-name="netty-ssl-connector"/>
</connectors>
<entries>
<entry name="java:/jboss/exported/jms/ConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
</hornetq-server>
Create a remote JMS client to connect to the sever using the exported connection obtained from JNDI (using http-remoting). When the client attempts to connect the server throws the ClassNotFound exception mentioned above and the connection fails.
> ClassNotFound exception when connecting a remote HornetQ client over SSL
> ------------------------------------------------------------------------
>
> Key: WFLY-4259
> URL: https://issues.jboss.org/browse/WFLY-4259
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Jon Kranes
> Assignee: Jeff Mesnil
>
> When using HornetQ with a remote client connecting with SSL (using a netty-connector with ssl-enabled=true) the server throws an exception in ModuleClassLoader when the client attempts to connect. The exception is:
> java.lang.ClassNotFoundException: javax.net.SSLException
> After doing some investigation I was able to resolve this issue by adding a dependency in the io.netty module.xml file
> <dependencies>
> <module name="javax.api"/>
> <dependencies
> Without this dependency, it appear that Netty is unable to load classes that it needs from javax.net.ssl.
> NOTE: adding this dependency resolves the issue in Wildfly 8.2.0.Final. However, it does NOT resolve the issue in 8.1.0.Final. Even after adding this dependency I still got the ClassNotFoundException.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4259) ClassNotFound exception when connecting a remote HornetQ client over SSL
by Jon Kranes (JIRA)
[ https://issues.jboss.org/browse/WFLY-4259?page=com.atlassian.jira.plugin.... ]
Jon Kranes updated WFLY-4259:
-----------------------------
Steps to Reproduce:
Configure Wildfly to use HornetQ messaging similar to the following:
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<security-enabled>false</security-enabled>
<connectors>
<netty-connector name="netty-ssl-connector" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="xxx"/>
<param key="host" value="localhost"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<acceptors>
<netty-acceptor name="netty-ssl-acceptor" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="password"/>
<param key="host" value="localhost"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<jms-connection-factories>
<connection-factory name="ConnectionFactory">
<connectors>
<connector-ref connector-name="netty-ssl-connector"/>
</connectors>
<entries>
<entry name="java:/jboss/exported/jms/ConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
</hornetq-server>
Create a remote JMS client to connect to the sever using the exported connection obtained from JNDI (using http-remoting). When the client attempts to connect the server throws the ClassNotFound exception mentioned above and the connection fails.
was:
Configure Wildfly to use HornetQ messaging similar to the following:
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<security-enabled>false</security-enabled>
<connectors>
<netty-connector name="netty-connector" socket-binding="messaging-tcp"/>
<netty-connector name="netty-ssl-connector" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="xxx"/>
<param key="host" value="localhost"/>
</netty-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<acceptors>
<netty-acceptor name="netty-ssl-acceptor" socket-binding="https">
<param key="ssl-enabled" value="true"/>
<param key="trust-store-path" value="/foo/trust.jks"/>
<param key="trust-store-password" value="xxx"/>
<param key="key-store-path" value="/foo/key.jks"/>
<param key="key-store-password" value="password"/>
<param key="host" value="localhost"/>
</netty-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<jms-connection-factories>
<connection-factory name="ConnectionFactory">
<connectors>
<connector-ref connector-name="netty-ssl-connector"/>
</connectors>
<entries>
<entry name="java:/jboss/exported/jms/ConnectionFactory"/>
</entries>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
</hornetq-server>
Create a remote JMS client to connect to the sever using the connection obtained from JNDI (using http-remoting). When the client attempts to connect the server throws the ClassNotFound exception mentioned above and the connection fails.
> ClassNotFound exception when connecting a remote HornetQ client over SSL
> ------------------------------------------------------------------------
>
> Key: WFLY-4259
> URL: https://issues.jboss.org/browse/WFLY-4259
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.1.0.Final, 8.2.0.Final
> Reporter: Jon Kranes
> Assignee: Jeff Mesnil
>
> When using HornetQ with a remote client connecting with SSL (using a netty-connector with ssl-enabled=true) the server throws an exception in ModuleClassLoader when the client attempts to connect. The exception is:
> java.lang.ClassNotFoundException: javax.net.SSLException
> After doing some investigation I was able to resolve this issue by adding a dependency in the io.netty module.xml file
> <dependencies>
> <module name="javax.api"/>
> <dependencies
> Without this dependency, it appear that Netty is unable to load classes that it needs from javax.net.ssl.
> NOTE: adding this dependency resolves the issue in Wildfly 8.2.0.Final. However, it does NOT resolve the issue in 8.1.0.Final. Even after adding this dependency I still got the ClassNotFoundException.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4259) ClassNotFound exception when connecting a remote HornetQ client over SSL
by Jon Kranes (JIRA)
Jon Kranes created WFLY-4259:
--------------------------------
Summary: ClassNotFound exception when connecting a remote HornetQ client over SSL
Key: WFLY-4259
URL: https://issues.jboss.org/browse/WFLY-4259
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 8.2.0.Final, 8.1.0.Final
Reporter: Jon Kranes
Assignee: Jeff Mesnil
When using HornetQ with a remote client connecting with SSL (using a netty-connector with ssl-enabled=true) the server throws an exception in ModuleClassLoader when the client attempts to connect. The exception is:
java.lang.ClassNotFoundException: javax.net.SSLException
After doing some investigation I was able to resolve this issue by adding a dependency in the io.netty module.xml file
<dependencies>
<module name="javax.api"/>
<dependencies
Without this dependency, it appear that Netty is unable to load classes that it needs from javax.net.ssl.
NOTE: adding this dependency resolves the issue in Wildfly 8.2.0.Final. However, it does NOT resolve the issue in 8.1.0.Final. Even after adding this dependency I still got the ClassNotFoundException.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-691) Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
by Rares Vernica (JIRA)
[ https://issues.jboss.org/browse/DROOLS-691?page=com.atlassian.jira.plugin... ]
Rares Vernica commented on DROOLS-691:
--------------------------------------
The bug seems to be triggering when there is a rule that matches the GIVEN facts and the rule creates a new Goz.
> Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
> -----------------------------------------------------------------------
>
> Key: DROOLS-691
> URL: https://issues.jboss.org/browse/DROOLS-691
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Reporter: Rares Vernica
> Assignee: Mark Proctor
>
> This is a bug with Workflow Test Scenario. I have two types:
> org.foo.Bar
> goz
> org.foo.Goz
> g1
> g2
> Bar has a member of type Goz called goz. Goz has two members g1 and g2 which have predefined values in an enumeration and g2 depends on the value of g1. I have a rule using them and the rule is fine.
> The problem is when I create a Test Scenario using them. The scenario has Goz and a Bar in the GIVEN section. Both are blinded to variable names and the goz member of Bar is initialized with the Goz instance.
> I first create Goz in the GIVEN section. I add g1 and g2 and assign literal values to them.
> Then I create Bar in the given section as well. Without any further changes I "Run scenario" and I get:
> Reporting:
> There were test failures
> Text
> Test : org.foo.Bar cannot be cast to org.foo.Bar
> It might be relate to DROOLS-689 which I reported earlier.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-691) Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
by Rares Vernica (JIRA)
Rares Vernica created DROOLS-691:
------------------------------------
Summary: Workflow Test Scenario error: org.foo.Bar cannot be cast to org.foo.Bar
Key: DROOLS-691
URL: https://issues.jboss.org/browse/DROOLS-691
Project: Drools
Issue Type: Bug
Affects Versions: 6.1.0.Final
Reporter: Rares Vernica
Assignee: Mark Proctor
This is a bug with Workflow Test Scenario. I have two types:
org.foo.Bar
goz
org.foo.Goz
g1
g2
Bar has a member of type Goz called goz. Goz has two members g1 and g2 which have predefined values in an enumeration and g2 depends on the value of g1. I have a rule using them and the rule is fine.
The problem is when I create a Test Scenario using them. The scenario has Goz and a Bar in the GIVEN section. Both are blinded to variable names and the goz member of Bar is initialized with the Goz instance.
I first create Goz in the GIVEN section. I add g1 and g2 and assign literal values to them.
Then I create Bar in the given section as well. Without any further changes I "Run scenario" and I get:
Reporting:
There were test failures
Text
Test : org.foo.Bar cannot be cast to org.foo.Bar
It might be relate to DROOLS-689 which I reported earlier.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFCORE-493) Automatically index static modules as required
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFCORE-493?page=com.atlassian.jira.plugin... ]
Tomasz Adamski edited comment on WFCORE-493 at 1/16/15 2:32 PM:
----------------------------------------------------------------
Added a function to CompositeIndexProcessor which calculates index on the fly, when it is not attached by module creator:
{code}
private Index calculateModuleIndex(final Module module) throws ModuleLoadException, IOException {
final Indexer indexer = new Indexer();
final PathFilter filter = PathFilters.getDefaultImportFilter();
Iterator<Resource> iterator = module.iterateResources(filter);
while (iterator.hasNext()) {
Resource resource = iterator.next();
indexer.index(resource.openStream());
}
return indexer.complete();
}
{code}
TODO:
* if index was attached, but was calculated using previous jandex version it should be recalculated (waiting for jandex api update)
* disscuss wheter indexes should be cached
was (Author: tomekadamski):
Added a function to CompositeIndexProcessor which calculates index on the fly, when it is not attached by module creator:
{code}
private Index calculateModuleIndex(final Module module) throws ModuleLoadException, IOException {
final Indexer indexer = new Indexer();
final PathFilter filter = PathFilters.getDefaultImportFilter();
Iterator<Resource> iterator = module.iterateResources(filter);
while (iterator.hasNext()) {
Resource resource = iterator.next();
indexer.index(resource.openStream());
}
return indexer.complete();
}
{code}
> Automatically index static modules as required
> ----------------------------------------------
>
> Key: WFCORE-493
> URL: https://issues.jboss.org/browse/WFCORE-493
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Reporter: Stuart Douglas
> Assignee: Tomasz Adamski
>
> If a static module has an annotation import it should be automatically indexed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFCORE-493) Automatically index static modules as required
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFCORE-493?page=com.atlassian.jira.plugin... ]
Tomasz Adamski commented on WFCORE-493:
---------------------------------------
Added a function to CompositeIndexProcessor which calculates index on the fly, when it is not attached by module creator:
{code}
private Index calculateModuleIndex(final Module module) throws ModuleLoadException, IOException {
final Indexer indexer = new Indexer();
final PathFilter filter = PathFilters.getDefaultImportFilter();
Iterator<Resource> iterator = module.iterateResources(filter);
while (iterator.hasNext()) {
Resource resource = iterator.next();
indexer.index(resource.openStream());
}
return indexer.complete();
}
{code}
> Automatically index static modules as required
> ----------------------------------------------
>
> Key: WFCORE-493
> URL: https://issues.jboss.org/browse/WFCORE-493
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Reporter: Stuart Douglas
> Assignee: Tomasz Adamski
>
> If a static module has an annotation import it should be automatically indexed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months