[JBoss JIRA] (WFLY-9168) Log error org.jboss.security.annotation.SecurityDomain annotation is used in EJB
by Panagiotis Sotiropoulos (JIRA)
[ https://issues.jboss.org/browse/WFLY-9168?page=com.atlassian.jira.plugin.... ]
Panagiotis Sotiropoulos updated WFLY-9168:
------------------------------------------
Comment: was deleted
(was: A comment with security level 'Red Hat Employee' was removed.)
> Log error org.jboss.security.annotation.SecurityDomain annotation is used in EJB
> --------------------------------------------------------------------------------
>
> Key: WFLY-9168
> URL: https://issues.jboss.org/browse/WFLY-9168
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Critical
> Fix For: 12.0.0.Alpha1
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The annotation *{{org.jboss.security.annotation.SecurityDomain}}* is present in the legacy security packages and documented in 7.1 [Javadoc|https://access.redhat.com/webassets/avalon/d/red-hat-jboss-enterp...]:
> {quote}
> Annotation for specifying the JBoss security domain for EJBs.
> {quote}
> Nevertheless this annotation doesn't work and the one from another package has to be used instead - {{org.jboss.ejb3.annotation.SecurityDomain}}.
> Server doesn't log an error or warning when the legacy one is used.
> *Suggested fix:*
> Add a deployment processor which will log error when the legacy annotation is used in the deployment.
> Another possibility how to fix this would be to add support for the legacy annotation too.
> I'll create a separate JIRA for JavaDoc update in the legacy annotation class.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9800) ASM version divergence after org.apache.cxf:cxf-rt-bindings-xml version upgrade
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-9800:
---------------------------------------
Summary: ASM version divergence after org.apache.cxf:cxf-rt-bindings-xml version upgrade
Key: WFLY-9800
URL: https://issues.jboss.org/browse/WFLY-9800
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 12.0.0.Alpha1
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Minor
The version of the ASM library pulled by cxf-rt-bindings-xml 3.3.2 is different from the one from org.jboss.ws.cxf:jbossws-cxf-client:5.2.0.
The solution would be to exclude it from the dependencies and define it properly using the newest org.ow2.asm:asm 6.0
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-9096:
-----------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/10323
> JMS client fails to connect with SSL on IBM JDK 8
> -------------------------------------------------
>
> Key: WFLY-9096
> URL: https://issues.jboss.org/browse/WFLY-9096
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 11.0.0.Alpha1
> Environment: IBM JDK 8:
> {code}
> $ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled)
> J9VM - R28_20170314_2309_B340265
> JIT - tr.r14.java.green_20170314_134138
> GC - R28_20170314_2309_B340265
> J9CL - 20170314_340265)
> JCL - 20170318_01 based on Oracle jdk8u121-b13
> {code}
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Labels: eap7.1-risks-mitigation
>
> If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with:
> {code}
> ERROR: AMQ214016: Failed to create netty connection
> java.nio.channels.ClosedChannelException
> at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source)
> Producer got exception and ended:javax.jms.JMSException: Failed to create session factory
> javax.jms.JMSException: Failed to create session factory
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260)
> at ProducerTransSession.run(ProducerTransSession.java:75)
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755)
> ... 3 more
> {code}
> If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully.
> Issue is under investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9788) EJB over HTTP fails...
by Heiko Lettmann (JIRA)
[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ]
Heiko Lettmann edited comment on WFLY-9788 at 2/12/18 4:34 AM:
---------------------------------------------------------------
Basically the problem occurs when I add and execute this to the Stateful Bean in the test:
(old and new!)
public List<String> test2(String[] s1, String[] s2) {
return null;
}
Like this the client...
System.out.println(statefulRemoteCounter.test2(new String[0], new String[0]));
was (Author: grafzal):
Basically the problem occurs when I add and execute this to the Stateful Bean in the test:
(old and new!)
public List<String> test2(String[] s1, String[] s2) {
return null;
}
> EJB over HTTP fails...
> ----------------------
>
> Key: WFLY-9788
> URL: https://issues.jboss.org/browse/WFLY-9788
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Heiko Lettmann
> Priority: Blocker
> Attachments: Test.zip
>
>
> I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it!
> Exception is on the client side:
> Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128)
> at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126)
> ... 4 more
> Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9788) EJB over HTTP fails...
by Heiko Lettmann (JIRA)
[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ]
Heiko Lettmann edited comment on WFLY-9788 at 2/12/18 4:34 AM:
---------------------------------------------------------------
Basically the problem occurs when I add and execute this to the Stateful Bean in the test:
(old and new!)
public List<String> test2(String[] s1, String[] s2) {
return null;
}
Like this the on client...
System.out.println(statefulRemoteCounter.test2(new String[0], new String[0]));
was (Author: grafzal):
Basically the problem occurs when I add and execute this to the Stateful Bean in the test:
(old and new!)
public List<String> test2(String[] s1, String[] s2) {
return null;
}
Like this the client...
System.out.println(statefulRemoteCounter.test2(new String[0], new String[0]));
> EJB over HTTP fails...
> ----------------------
>
> Key: WFLY-9788
> URL: https://issues.jboss.org/browse/WFLY-9788
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Heiko Lettmann
> Priority: Blocker
> Attachments: Test.zip
>
>
> I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it!
> Exception is on the client side:
> Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128)
> at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126)
> ... 4 more
> Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9788) EJB over HTTP fails...
by Heiko Lettmann (JIRA)
[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ]
Heiko Lettmann commented on WFLY-9788:
--------------------------------------
Basically the problem occurs when I add and execute this to the Stateful Bean in the test:
(old and new!)
public List<String> test2(String[] s1, String[] s2) {
return null;
}
> EJB over HTTP fails...
> ----------------------
>
> Key: WFLY-9788
> URL: https://issues.jboss.org/browse/WFLY-9788
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Reporter: Heiko Lettmann
> Priority: Blocker
> Attachments: Test.zip
>
>
> I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it!
> Exception is on the client side:
> Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128)
> at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126)
> ... 4 more
> Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months