buildbot success in on tomee-1.7.x-ubuntu
The Buildbot has detected a restored build on builder tomee-1.7.x-ubuntu while building . Full details are available at: https://ci.apache.org/builders/tomee-1.7.x-ubuntu/builds/131 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: forced: by IRC user on channel #openejb: None Build Source Stamp: HEAD Blamelist: Build succeeded! Sincerely, -The Buildbot
buildbot failure in on tomee-trunk-ubuntu-jvm8
The Buildbot has detected a new failure on builder tomee-trunk-ubuntu-jvm8 while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/382 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-jvm8-commit' triggered this build Build Source Stamp: [branch master] 21ee2b6f8500be3dd1e682b1c77a304904898693 Blamelist: Romain manni-Bucau BUILD FAILED: failed test Sincerely, -The Buildbot
[jira] [Commented] (TOMEE-1865) NPE when injected request used in bean called from JASPIC SAM
[
https://issues.apache.org/jira/browse/TOMEE-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374742#comment-15374742
]
Romain Manni-Bucau commented on TOMEE-1865:
---
[~arjan.tijms] you did an awesome job to spot it out and let us reproduce it so
was the least we can do
> NPE when injected request used in bean called from JASPIC SAM
> -
>
> Key: TOMEE-1865
> URL: https://issues.apache.org/jira/browse/TOMEE-1865
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.1
>Reporter: Arjan Tijms
>Assignee: Romain Manni-Bucau
> Labels: security
> Fix For: 7.0.2
>
>
> When a CDI bean is called from a JASPIC SAM ({{validateRequest}} or
> {{secureResponse}}), and this bean has an injected {{HttpServletRequest}},
> then a proxy is indeed injected, but when any method is called on this proxy
> a NullPointerException is thrown:
> {noformat}
> java.lang.NullPointerException
> at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.openejb.cdi.Proxys$ThreadLocalHandler.invoke(Proxys.java:95)
> at com.sun.proxy.$Proxy15.setAttribute(Unknown Source)
> at
> org.javaee7.jaspic.invoke.bean.CDIBean.setTextViaInjectedRequest(CDIBean.java:20)
> at
> org.javaee7.jaspic.invoke.bean.CDIBean$$OwbNormalScopeProxy0.setTextViaInjectedRequest(org/javaee7/jaspic/invoke/bean/CDIBean.java)
> at
> org.javaee7.jaspic.invoke.sam.TestServerAuthModule.callCDIBean(TestServerAuthModule.java:113)
> at
> org.javaee7.jaspic.invoke.sam.TestServerAuthModule.validateRequest(TestServerAuthModule.java:57)
> at
> org.javaee7.jaspic.common.TestServerAuthContext.validateRequest(TestServerAuthContext.java:36)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.authenticate(AuthenticatorBase.java:706)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:599)
> {noformat}
> The same exception is thrown when a SAM doesn't call a CDI bean directly, but
> forwards to a Servlet, which is injected with the same kind of CDI bean.
> For using the bean directly from a SAM I've extended the existing test case
> here:
> https://github.com/javaee-samples/javaee7-samples/tree/master/jaspic/invoke-ejb-cdi
> The expected output is:
> {noformat}
> validateRequest: Called from CDI
> validateRequest: Called from CDI via injected request
> Resource invoked
> cleanSubject: Called from CDI
> cleanSubject: Called from CDI via injected request
> secureResponse: Called from CDI
> secureResponse: Called from CDI via injected request
> {noformat}
> But on TomEE 7.0.1 it's:
> {noformat}validateRequest: Called from CDI
> Resource invoked
> cleanSubject: Called from CDI
> cleanSubject: Called from CDI via injected request
> secureResponse: Called from CDI
> {noformat}
> On JBoss EAP 7/WildFly 10.0.0 and Payara 4.1.1.162 the output is as expected.
> The CDI bean looks as follows:
> {code:java}
> @Named
> @RequestScoped
> public class CDIBean {
>
> @Inject
> private HttpServletRequest request;
> public String getText() {
> return "Called from CDI";
> }
>
> public void setTextViaInjectedRequest() {
> request.setAttribute("text", "Called from CDI via injected request");
> }
>
> }
> {code}
> The call to this bean from a SAM is essentially this:
> {code:java}
> CDIBean cdiBean = CDI.current().select(CDIBean.class).get();
> cdiBean.setTextViaInjectedRequest();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TOMEE-1865) NPE when injected request used in bean called from JASPIC SAM
[
https://issues.apache.org/jira/browse/TOMEE-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374736#comment-15374736
]
Arjan Tijms commented on TOMEE-1865:
That's a really quick fix, thanks Romain!
> NPE when injected request used in bean called from JASPIC SAM
> -
>
> Key: TOMEE-1865
> URL: https://issues.apache.org/jira/browse/TOMEE-1865
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
>Affects Versions: 7.0.1
>Reporter: Arjan Tijms
>Assignee: Romain Manni-Bucau
> Labels: security
> Fix For: 7.0.2
>
>
> When a CDI bean is called from a JASPIC SAM ({{validateRequest}} or
> {{secureResponse}}), and this bean has an injected {{HttpServletRequest}},
> then a proxy is indeed injected, but when any method is called on this proxy
> a NullPointerException is thrown:
> {noformat}
> java.lang.NullPointerException
> at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.openejb.cdi.Proxys$ThreadLocalHandler.invoke(Proxys.java:95)
> at com.sun.proxy.$Proxy15.setAttribute(Unknown Source)
> at
> org.javaee7.jaspic.invoke.bean.CDIBean.setTextViaInjectedRequest(CDIBean.java:20)
> at
> org.javaee7.jaspic.invoke.bean.CDIBean$$OwbNormalScopeProxy0.setTextViaInjectedRequest(org/javaee7/jaspic/invoke/bean/CDIBean.java)
> at
> org.javaee7.jaspic.invoke.sam.TestServerAuthModule.callCDIBean(TestServerAuthModule.java:113)
> at
> org.javaee7.jaspic.invoke.sam.TestServerAuthModule.validateRequest(TestServerAuthModule.java:57)
> at
> org.javaee7.jaspic.common.TestServerAuthContext.validateRequest(TestServerAuthContext.java:36)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.authenticate(AuthenticatorBase.java:706)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:599)
> {noformat}
> The same exception is thrown when a SAM doesn't call a CDI bean directly, but
> forwards to a Servlet, which is injected with the same kind of CDI bean.
> For using the bean directly from a SAM I've extended the existing test case
> here:
> https://github.com/javaee-samples/javaee7-samples/tree/master/jaspic/invoke-ejb-cdi
> The expected output is:
> {noformat}
> validateRequest: Called from CDI
> validateRequest: Called from CDI via injected request
> Resource invoked
> cleanSubject: Called from CDI
> cleanSubject: Called from CDI via injected request
> secureResponse: Called from CDI
> secureResponse: Called from CDI via injected request
> {noformat}
> But on TomEE 7.0.1 it's:
> {noformat}validateRequest: Called from CDI
> Resource invoked
> cleanSubject: Called from CDI
> cleanSubject: Called from CDI via injected request
> secureResponse: Called from CDI
> {noformat}
> On JBoss EAP 7/WildFly 10.0.0 and Payara 4.1.1.162 the output is as expected.
> The CDI bean looks as follows:
> {code:java}
> @Named
> @RequestScoped
> public class CDIBean {
>
> @Inject
> private HttpServletRequest request;
> public String getText() {
> return "Called from CDI";
> }
>
> public void setTextViaInjectedRequest() {
> request.setAttribute("text", "Called from CDI via injected request");
> }
>
> }
> {code}
> The call to this bean from a SAM is essentially this:
> {code:java}
> CDIBean cdiBean = CDI.current().select(CDIBean.class).get();
> cdiBean.setTextViaInjectedRequest();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
buildbot exception in on tomee-trunk-ubuntu
The Buildbot has detected a build exception on builder tomee-trunk-ubuntu while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/415 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-commit' triggered this build Build Source Stamp: [branch master] 21ee2b6f8500be3dd1e682b1c77a304904898693 Blamelist: Romain manni-Bucau BUILD FAILED: exception interrupted Sincerely, -The Buildbot
tomee git commit: trimStackTrace=false for surefire in parent pom
Repository: tomee Updated Branches: refs/heads/master 21ee2b6f8 -> 74fdd3341 trimStackTrace=false for surefire in parent pom Project: http://git-wip-us.apache.org/repos/asf/tomee/repo Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/74fdd334 Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/74fdd334 Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/74fdd334 Branch: refs/heads/master Commit: 74fdd3341b1e2d99206b2b8c23248a25b05c1507 Parents: 21ee2b6 Author: Romain manni-Bucau Authored: Wed Jul 13 11:03:17 2016 +0200 Committer: Romain manni-Bucau Committed: Wed Jul 13 11:03:17 2016 +0200 -- pom.xml | 1 + 1 file changed, 1 insertion(+) -- http://git-wip-us.apache.org/repos/asf/tomee/blob/74fdd334/pom.xml -- diff --git a/pom.xml b/pom.xml index b05ed99..80c4ce8 100644 --- a/pom.xml +++ b/pom.xml @@ -353,6 +353,7 @@ org.apache.maven.plugins maven-surefire-plugin + false false
[jira] [Resolved] (OPENEJB-2131) could not load library
[
https://issues.apache.org/jira/browse/OPENEJB-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau resolved OPENEJB-2131.
-
Resolution: Not A Problem
> could not load library
> --
>
> Key: OPENEJB-2131
> URL: https://issues.apache.org/jira/browse/OPENEJB-2131
> Project: OpenEJB
> Issue Type: Bug
>Reporter: Pascal Knüppel
>Priority: Critical
>
> I am somehow stuck with an UnsatisfiedLinkError I am not able to resolve. It
> showed up out of the blue when initializing the open ejb context. It worked
> before I have no idea what happened to justify this error
> {code:title=OpenEjbTest.java|borderStyle=solid}
> public abstract class OpenEjbTest {
> protected Context initialContext;
> @EJB
> protected OpenEjbTransactionCaller transactionCaller;
> @Before
> public void setUp() throws NamingException {
> Properties p = new Properties();
> p.put("log4j.rootLogger", "fatal,C");
> p.put("log4j.category.OpenEJB", "error");
> p.put("log4j.category.OpenEJB.options", "error");
> p.put("log4j.category.OpenEJB.server", "error");
> p.put("log4j.category.OpenEJB.startup", "error");
> p.put("log4j.category.OpenEJB.startup.service", "error");
> p.put("log4j.category.OpenEJB.startup.config", "error");
> p.put("log4j.category.OpenEJB.hsql", "error");
> p.put("log4j.category.CORBA-Adapter", "error");
> p.put("log4j.category.Transaction", "error");
> p.put("log4j.category.org.apache.activemq", "error");
> p.put("log4j.category.org.apache.geronimo", "error");
> p.put("log4j.category.openjpa", "error");
> p.put("log4j.appender.C", "org.apache.log4j.ConsoleAppender");
> p.put("log4j.appender.C.layout", "org.apache.log4j.SimpleLayout");
> p.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> "org.apache.openejb.client.LocalInitialContextFactory");
> initialContext = new InitialContext(p);
> initialContext.bind("inject", this);// ***the error
> line*
> }
> @After
> public void cleanUp() throws NamingException {
> initialContext.unbind("inject");
> initialContext.close();
> }
> }
> {code}
> {code:title=test.java.java|borderStyle=solid}
> @LocalClient
> public class test extends OpenEjbTest {
> @Test
> public void test() {
> // when executing this empty test the error occurs
> }
> }
> {code}
> {noformat}
> java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no
> jansi32-1.8 in java.library.path, no jansi-1.8 in java.library.path, no jansi
> in java.library.path, Native Library
> C:\Users\praktikant\AppData\Local\Temp\jansi-32-1.8.dll already loaded in
> another classloader]
> at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:184)
> at org.fusesource.hawtjni.runtime.Library.load(Library.java:142)
> at org.fusesource.jansi.internal.Kernel32.(Kernel32.java:37)
> at
> org.fusesource.jansi.WindowsAnsiOutputStream.(WindowsAnsiOutputStream.java:52)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.getOutputStream(ConsoleAppender.java:204)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.getManager(ConsoleAppender.java:178)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.createDefaultAppenderForLayout(ConsoleAppender.java:109)
> at
> org.apache.logging.log4j.core.config.DefaultConfiguration.(DefaultConfiguration.java:62)
> at
> org.apache.logging.log4j.core.LoggerContext.(LoggerContext.java:70)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:145)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:70)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:57)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:142)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:175)
> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:426)
> at
> de.fiverx.backend.service.LadeRzZertifikatRessource.(Lad
[jira] [Commented] (OPENEJB-2131) could not load library
[
https://issues.apache.org/jira/browse/OPENEJB-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374500#comment-15374500
]
Pascal Knüppel commented on OPENEJB-2131:
-
as you said. problem solved. thx a lot :-)
> could not load library
> --
>
> Key: OPENEJB-2131
> URL: https://issues.apache.org/jira/browse/OPENEJB-2131
> Project: OpenEJB
> Issue Type: Bug
>Reporter: Pascal Knüppel
>Priority: Critical
>
> I am somehow stuck with an UnsatisfiedLinkError I am not able to resolve. It
> showed up out of the blue when initializing the open ejb context. It worked
> before I have no idea what happened to justify this error
> {code:title=OpenEjbTest.java|borderStyle=solid}
> public abstract class OpenEjbTest {
> protected Context initialContext;
> @EJB
> protected OpenEjbTransactionCaller transactionCaller;
> @Before
> public void setUp() throws NamingException {
> Properties p = new Properties();
> p.put("log4j.rootLogger", "fatal,C");
> p.put("log4j.category.OpenEJB", "error");
> p.put("log4j.category.OpenEJB.options", "error");
> p.put("log4j.category.OpenEJB.server", "error");
> p.put("log4j.category.OpenEJB.startup", "error");
> p.put("log4j.category.OpenEJB.startup.service", "error");
> p.put("log4j.category.OpenEJB.startup.config", "error");
> p.put("log4j.category.OpenEJB.hsql", "error");
> p.put("log4j.category.CORBA-Adapter", "error");
> p.put("log4j.category.Transaction", "error");
> p.put("log4j.category.org.apache.activemq", "error");
> p.put("log4j.category.org.apache.geronimo", "error");
> p.put("log4j.category.openjpa", "error");
> p.put("log4j.appender.C", "org.apache.log4j.ConsoleAppender");
> p.put("log4j.appender.C.layout", "org.apache.log4j.SimpleLayout");
> p.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> "org.apache.openejb.client.LocalInitialContextFactory");
> initialContext = new InitialContext(p);
> initialContext.bind("inject", this);// ***the error
> line*
> }
> @After
> public void cleanUp() throws NamingException {
> initialContext.unbind("inject");
> initialContext.close();
> }
> }
> {code}
> {code:title=test.java.java|borderStyle=solid}
> @LocalClient
> public class test extends OpenEjbTest {
> @Test
> public void test() {
> // when executing this empty test the error occurs
> }
> }
> {code}
> {noformat}
> java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no
> jansi32-1.8 in java.library.path, no jansi-1.8 in java.library.path, no jansi
> in java.library.path, Native Library
> C:\Users\praktikant\AppData\Local\Temp\jansi-32-1.8.dll already loaded in
> another classloader]
> at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:184)
> at org.fusesource.hawtjni.runtime.Library.load(Library.java:142)
> at org.fusesource.jansi.internal.Kernel32.(Kernel32.java:37)
> at
> org.fusesource.jansi.WindowsAnsiOutputStream.(WindowsAnsiOutputStream.java:52)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.getOutputStream(ConsoleAppender.java:204)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.getManager(ConsoleAppender.java:178)
> at
> org.apache.logging.log4j.core.appender.ConsoleAppender.createDefaultAppenderForLayout(ConsoleAppender.java:109)
> at
> org.apache.logging.log4j.core.config.DefaultConfiguration.(DefaultConfiguration.java:62)
> at
> org.apache.logging.log4j.core.LoggerContext.(LoggerContext.java:70)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:145)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:70)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:57)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:142)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:175)
> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:426)
> a
