[JBoss JIRA] (WFLY-3831) Securing EJB comunitication via SSL is failed
by Jonhny Jonhny (JIRA)
[ https://issues.jboss.org/browse/WFLY-3831?page=com.atlassian.jira.plugin.... ]
Jonhny Jonhny updated WFLY-3831:
--------------------------------
Description:
I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local"/>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
</ssl>
</server-identities>
<authentication>
<jaas name="ybxiang-forum-jaas-security-domain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
Client log
!ENTRY com 0 0 2014-09-09 15:52:05.124
!MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
at com.model.connection.ServerLink.login(ServerLink.java:325)
at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
... 7 more
Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
... 9 more"
Server log
2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
was:
I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local"/>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
</ssl>
</server-identities>
<authentication>
<jaas name="ybxiang-forum-jaas-security-domain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
Client log
!ENTRY com 0 0 2014-09-09 15:52:05.124
!MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
at com.model.connection.ServerLink.login(ServerLink.java:325)
at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
... 7 more
Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
... 9 more"
Server log
2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> Securing EJB comunitication via SSL is failed
> ----------------------------------------------
>
> Key: WFLY-3831
> URL: https://issues.jboss.org/browse/WFLY-3831
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Jonhny Jonhny
> Assignee: David Lloyd
>
> I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server:
> <management>
> <security-realms>
> <security-realm name="ManagementRealm">
> <authentication>
> <local default-user="$local"/>
> <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
> </authentication>
> </security-realm>
> <security-realm name="ApplicationRealm">
> <server-identities>
> <ssl>
> <keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
> </ssl>
> </server-identities>
> <authentication>
> <jaas name="ybxiang-forum-jaas-security-domain"/>
> </authentication>
> </security-realm>
> </security-realms>
> <management-interfaces>
> <native-interface security-realm="ManagementRealm">
> <socket-binding native="management-native"/>
> </native-interface>
> <http-interface security-realm="ManagementRealm">
> <socket-binding http="management-http"/>
> </http-interface>
> </management-interfaces>
> </management>
> Client log
> !ENTRY com 0 0 2014-09-09 15:52:05.124
> !MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
> java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
> at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
> at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
> at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
> at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
> at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
> at com.model.connection.ServerLink.login(ServerLink.java:325)
> at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
> at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
> at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
> at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
> ... 7 more
> Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
> at javax.naming.InitialContext.lookup(InitialContext.java:411)
> at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
> ... 9 more"
>
>
> Server log
> 2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> 2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3831) Securing EJB comunitication via SSL is failed
by Jonhny Jonhny (JIRA)
Jonhny Jonhny created WFLY-3831:
-----------------------------------
Summary: Securing EJB comunitication via SSL is failed
Key: WFLY-3831
URL: https://issues.jboss.org/browse/WFLY-3831
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: JBoss AS7 7.2.0.Final
Reporter: Jonhny Jonhny
Assignee: David Lloyd
I added the SSL configuration for ApplicationRealm as the guide in Jboss document, but It's failed when trying connection to server:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local"/>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<server-identities>
<ssl>
<keystore path="server.keystore" relative-to="jboss.server.config.dir" keystore-password="ybxiang_keystore_password"/>
</ssl>
</server-identities>
<authentication>
<jaas name="ybxiang-forum-jaas-security-domain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
Client log
!ENTRY com 0 0 2014-09-09 15:52:05.124
!MESSAGE (Timezone is ICT.) ;3556; com.model.connection.ServerLink logged : "could not connect:
java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://172.41.211.111:4447]
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:455)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:295)
at com.RemoteJMXDispatcher.<init>(RemoteJMXDispatcher.java:288)
at com.model.connection.SecuredRemoteJMXDispatcher.<init>(SecuredRemoteJMXDispatcher.java:39)
at com.model.connection.SecuredRemoteJMXDispatcher.create(SecuredRemoteJMXDispatcher.java:86)
at com.model.connection.ServerLink.login(ServerLink.java:325)
at com.login.ConnectToServerRunnable.run(ConnectToServerRunnable.java:60)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.RuntimeException: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:108)
at com.JMSUtil.createRemoteConnection(JMSUtil.java:78)
at com.RemoteJMXDispatcher.connectToJMS(RemoteJMXDispatcher.java:404)
... 7 more
Caused by: javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://192.168.95.111:4447]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:144)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:125)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:241)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at com.JMSUtil.getRemoteConnectionFactory(JMSUtil.java:101)
... 9 more"
Server log
2014-09-09 15:59:42,758 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:00:42,762 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:01:42,766 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:02:42,770 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:03:42,773 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:04:42,777 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
2014-09-09 16:05:42,781 ERROR [Remoting "config-based-naming-client-endpoint" read-1]-[org.jboss.remoting.remote.connection] JBREM000200: Remote connection failed: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-498) Memory leak in stateful session after retracting facts
by Massinissa BOUZIAD (JIRA)
[ https://issues.jboss.org/browse/DROOLS-498?page=com.atlassian.jira.plugin... ]
Massinissa BOUZIAD commented on DROOLS-498:
-------------------------------------------
Hi,
When I try to delete a fact through its facthandle and then call to fireAllRules, the rules still continue to match on the deleted fact.
I'm using StateFullSession.
My code looks like that :
{code:java}
KieSession ksession = newSession();
FactHandle baksetFactHandle = ksession.insert(basket);
// Control the activation flow by group
Agenda agenda = ksession.getAgenda();
agenda.getAgendaGroup("apply-result").setFocus();
agenda.getAgendaGroup("basket").setFocus();
agenda.getAgendaGroup("apply-result").setFocus();
agenda.getAgendaGroup("lines").setFocus();
long startTime = System.currentTimeMillis();
ksession.fireAllRules();
if (LOGGER.isDebugEnabled()) {
long duration = System.currentTimeMillis() - startTime;
LOGGER.debug("Drools basket evaluation in : {} milliseconds", duration);
}
//Remove basket from session before returning the session to the pool
ksession.delete(baksetFactHandle);
List<Advantage> advantages = (List<Advantage>)ksession.getGlobal("advantages");
{code}
This code is called on a per customer basis and state full session are reused.
But between two subsequent call, I get the same result as the previous call doesn't actually delete the customer basket from the session.
Need help !
> Memory leak in stateful session after retracting facts
> ------------------------------------------------------
>
> Key: DROOLS-498
> URL: https://issues.jboss.org/browse/DROOLS-498
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.0.1.Final
> Reporter: Vitaly Lomov
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 6.1.0.Final
>
> Attachments: gcRoot.png, memory-leak2.zip, screenshot1.png
>
>
> After adding many simple facts into the stateful session and then removing them, the factHandles for the removed facts are still referenced by the session. Eventually getting "java.lang.OutOfMemoryError: GC overhead limit exceeded" with the stack trace (sometimes) similar to DROOLS-411.
> Someone on StackOverflow suggested iterating through whatever factHandles remain after deletion and delete those, but I get no factHandles (correct, since I removed all facts).
> See screenshot for objects in memory _after_ deleting all facts.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-228) TS: Migrate from Surefire to Failsafe maven plugin.
by Jakub Senko (JIRA)
[ https://issues.jboss.org/browse/WFLY-228?page=com.atlassian.jira.plugin.s... ]
Jakub Senko updated WFLY-228:
-----------------------------
Assignee: (was: Jakub Senko)
> TS: Migrate from Surefire to Failsafe maven plugin.
> ---------------------------------------------------
>
> Key: WFLY-228
> URL: https://issues.jboss.org/browse/WFLY-228
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Ondrej Zizka
> Fix For: Awaiting Volunteers
>
> Attachments: AS7-failsafe-surefire.html.zip
>
>
> Surefire aims at unit testing.
> Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify.
> That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae).
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3830) Use external-context for remote TIBCO ems lookup
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-3830:
---------------------------------
Summary: Use external-context for remote TIBCO ems lookup
Key: WFLY-3830
URL: https://issues.jboss.org/browse/WFLY-3830
Project: WildFly
Issue Type: Bug
Components: Naming
Affects Versions: 8.1.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
If an users uses the generic JMS RA with the TIBCO EMS messaging server, he has to duplicate all the JNDI parameters in the MDB annotations.
Instead, he should be able to use a naming's external-context to connect to the Remote TIBCO server with the following configuration:
{noformat}
<bindings>
<external-context name="java:global/tibco" module="com.tibco" class="javax.naming.InitialContext">
<environment>
<property name="java.naming.factory.initial" value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"/>
<property name="java.naming.provider.url" value="tcp://<tibco_server>:<tibco_port>"/>
<property name="java.naming.factory.url.pkgs" value="com.tibco.tibjms.naming"/>
</environment>
</external-context>
</bindings>
{noformat}
With these settings, the user only needs to pass the expected connection factory and destination lookup in the MDB:
{noformat}
@ActivationConfigProperty(propertyName = "connectionFactory", propertyValue = "java:global/tibco/XACF"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "java:global/tibco/Q1"),
{noformat}
The local JNDI lookup "java:global/tibco/Q1" will then use the external context (bound to "java:global/tibco") to lookup the "Q1" name on the TIBCO EMS.
There are a few bugs in the ExternalObjectFactory that prevents to use this configuration with a regular javax.naming.InitialContext to build the external context.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month