[JBoss JIRA] (JGRP-1993) ENCRYPTAsymmetricTest fails on IBM jdk 1.8
by Richard Janík (JIRA)
[ https://issues.jboss.org/browse/JGRP-1993?page=com.atlassian.jira.plugin.... ]
Richard Janík commented on JGRP-1993:
-------------------------------------
It's in /qa/tools/opt/ibm-java-80/bin/.
> ENCRYPTAsymmetricTest fails on IBM jdk 1.8
> ------------------------------------------
>
> Key: JGRP-1993
> URL: https://issues.jboss.org/browse/JGRP-1993
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.6
> Environment: IBM jdk 1.8
> Reporter: Richard Janík
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.8
>
>
> org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange fails on IBM jdk 1.8 (JGroups 3.6.6.Final):
> {code}
> Error Message
> expected [javax.crypto.spec.SecretKeySpec@174de] but found [com.ibm.crypto.provider.AESSecretKey@e562eaa8]
> Stacktrace
> java.lang.AssertionError
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:496)
> at org.testng.Assert.assertEquals(Assert.java:125)
> at org.testng.Assert.assertEquals(Assert.java:167)
> at org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange(ENCRYPTAsymmetricTest.java:404)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
> at org.testng.TestRunner.privateRun(TestRunner.java:774)
> at org.testng.TestRunner.run(TestRunner.java:624)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:359)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312)
> at org.testng.SuiteRunner.run(SuiteRunner.java:261)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
> at org.testng.TestNG.run(TestNG.java:1048)
> at org.testng.TestNG.privateMain(TestNG.java:1355)
> at org.testng.TestNG.main(TestNG.java:1324)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-1993) ENCRYPTAsymmetricTest fails on IBM jdk 1.8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1993?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1993:
--------------------------------
Yes, I can ssh to dev59. Where's the IBM java executable?
> ENCRYPTAsymmetricTest fails on IBM jdk 1.8
> ------------------------------------------
>
> Key: JGRP-1993
> URL: https://issues.jboss.org/browse/JGRP-1993
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.6
> Environment: IBM jdk 1.8
> Reporter: Richard Janík
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.8
>
>
> org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange fails on IBM jdk 1.8 (JGroups 3.6.6.Final):
> {code}
> Error Message
> expected [javax.crypto.spec.SecretKeySpec@174de] but found [com.ibm.crypto.provider.AESSecretKey@e562eaa8]
> Stacktrace
> java.lang.AssertionError
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:496)
> at org.testng.Assert.assertEquals(Assert.java:125)
> at org.testng.Assert.assertEquals(Assert.java:167)
> at org.jgroups.protocols.ENCRYPTAsymmetricTest.testKeyChangesDuringKeyServerChange(ENCRYPTAsymmetricTest.java:404)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
> at org.testng.TestRunner.privateRun(TestRunner.java:774)
> at org.testng.TestRunner.run(TestRunner.java:624)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:359)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312)
> at org.testng.SuiteRunner.run(SuiteRunner.java:261)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
> at org.testng.TestNG.run(TestNG.java:1048)
> at org.testng.TestNG.privateMain(TestNG.java:1355)
> at org.testng.TestNG.main(TestNG.java:1324)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5917?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reassigned WFLY-5917:
------------------------------------
Component/s: (was: CDI / Weld)
Assignee: Farah Juma (was: Stuart Douglas)
> numberOfLogicalViews not working
> --------------------------------
>
> Key: WFLY-5917
> URL: https://issues.jboss.org/browse/WFLY-5917
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 9.0.2.Final
> Reporter: Gabriel Vieira
> Assignee: Farah Juma
> Labels: cdi, jsf22, wildfly
>
> Theres a bug in wildfly 9 Final
> Even if a set on web.xml
> {code:java}
> <context-param>
> <param-name>com.sun.faces.numberOfLogicalViews</param-name>
> <param-value>3</param-value>
> </context-param>
> {code}
> It keep storing 25 views.
> I tried @Named (CDI) and @ManagedBean and the problem persisted.
> My workaround was use @ViewScoped from Omnifaces
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-519) Xalan Linkage error : TransformerConfigurationException
by Scott Bennett-McLeish (JIRA)
[ https://issues.jboss.org/browse/WFCORE-519?page=com.atlassian.jira.plugin... ]
Scott Bennett-McLeish commented on WFCORE-519:
----------------------------------------------
Confirmed working for Wildfly 9.0.1, Java 1.8.0_65 on Win7 & Amazon Linux.
Thanks to Barnabas for solution.
> Xalan Linkage error : TransformerConfigurationException
> -------------------------------------------------------
>
> Key: WFCORE-519
> URL: https://issues.jboss.org/browse/WFCORE-519
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Environment: Wildfly 8.1 & 8.2-Final
> JDK 1.7.0_45 & 1.7.0_71
> Windows & Linux
> Reporter: Stephen Kay
> Assignee: David Lloyd
> Priority: Critical
> Fix For: 1.0.0.Alpha16
>
>
> Please note that this bug wasn't present on JBoss 7.1 / same WAR artifact
> This is full staktrace from our applicaion.
> 11:13:32,130 SEVERE ch.mitsa.credoc.ui.views.messages.MessagesTable (default task-9) Error getting message payload: : javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:765) rt.jar:1.7.0_71
> at _redirected.TransformerFactory.newTransformer(_TransformerFactory.java:132) jboss-modules.jar:1.3.3.Final
> at ch.mitsa.credoc.format.swift.impl.SwiftFormatter.getPrettyPrintedPayload(SwiftFormatter.java:196)
> at ch.mitsa.credoc.engine.service.OutputService.getPrettyPrintedMessage(OutputService.java:54)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) rt.jar:1.7.0_71
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) rt.jar:1.7.0_71
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) rt.jar:1.7.0_71
> at java.lang.reflect.Method.invoke(Method.java:606) rt.jar:1.7.0_71
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) wildfly-weld-8.2.0.Final.jar:8.2.0.Final
> (...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5919:
-------------------------------
Affects Version/s: 10.0.0.CR5
> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
> Key: WFLY-5919
> URL: https://issues.jboss.org/browse/WFLY-5919
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.CR5
> Reporter: John Ament
> Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.... ]
Jason Greene reassigned WFLY-5919:
----------------------------------
Assignee: Scott Marlow (was: Jason Greene)
> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
> Key: WFLY-5919
> URL: https://issues.jboss.org/browse/WFLY-5919
> Project: WildFly
> Issue Type: Bug
> Reporter: John Ament
> Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by John Ament (JIRA)
John Ament created WFLY-5919:
--------------------------------
Summary: Wildfly 10 CR5 Regression - Schema not added to query
Key: WFLY-5919
URL: https://issues.jboss.org/browse/WFLY-5919
Project: WildFly
Issue Type: Bug
Reporter: John Ament
Assignee: Jason Greene
My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
{code}
2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
{code}
I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
The config looks like this
{code}
@Table(name = "types", schema = "config")
{code}
I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months