[JBoss JIRA] Created: (JBAS-8671) ClassNotFoundException when a EJB Timer with custom info is deserialized
by Sipatha Shoko (JIRA)
ClassNotFoundException when a EJB Timer with custom info is deserialized
------------------------------------------------------------------------
Key: JBAS-8671
URL: https://jira.jboss.org/browse/JBAS-8671
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.1.0.GA
Environment: WinXP 32 bit, Ubuntu 10.04 32 bit, SunOS 5.10 sparc
Reporter: Sipatha Shoko
Assignee: Carlo de Wolf
When an EJB3 Timer is created, you can optionally specify information pertaining to the timer. The information object must be serializable. A TimerVo (packaged in the same jar as the EJB) object thats serializable is used as the information. The EJB is first deployed, the timer is correctly created. However if the server is restarted, a ClassNotFoundException for TimerVo is thrown when the previously saved timer is deserialised.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (AS7-1156) The JMX-AS7 Protocol should default to Remote
by Aslak Knutsen (JIRA)
The JMX-AS7 Protocol should default to Remote
---------------------------------------------
Key: AS7-1156
URL: https://issues.jboss.org/browse/AS7-1156
Project: Application Server 7
Issue Type: Feature Request
Components: Test Suite
Affects Versions: 7.0.0.CR1
Reporter: Aslak Knutsen
Currently the user has to provide this config for Arquillian to work with AS7
{code}
<container qualifier="jboss7" default="true">
<protocol type="jmx-as7">
<property name="executionType">REMOTE</property>
</protocol>
</container>
{code}
With out that, they will get a nasty exception:
{code}
java.lang.reflect.UndeclaredThrowableException
at $Proxy17.runTestMethodEmbedded(Unknown Source)
at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:78)
at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(
{code}
Since Embedded mode is currently not used at all, Remote should be default. Possible the protocol can figure this out on it's own at runtime.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (AS7-1361) Arquillian AS7 Container force a dependency on Arquillian Service in manifest.mf
by Aslak Knutsen (JIRA)
Arquillian AS7 Container force a dependency on Arquillian Service in manifest.mf
--------------------------------------------------------------------------------
Key: AS7-1361
URL: https://issues.jboss.org/browse/AS7-1361
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.0.0.Final
Reporter: Aslak Knutsen
Assignee: Andrew Rubinger
Fix For: 7.0.1.Final
When trying to e.g. use the Servlet Protocol instead of the jmx-as7 protocol you will get the following exception:
["jboss.deployment.unit.\"624b14c4-2bb2-4d44-be9e-1168c4d29164.war\".CONFIGURE_MODULE missing [ jboss.module.information.service.\"deployment.arquillian-service\".main ]
The AS7 container adds a dependency to the Arquillian Service using ApplicationArchiveProcessors which is a general purpose archive processor and it not tied to the Protocol itself. This handling needs to be moved to the DeploymentPackager.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBAS-8923) WAR with bundled Mojarra 2.1.0-b11
by Lukas Fryc (JIRA)
WAR with bundled Mojarra 2.1.0-b11
----------------------------------
Key: JBAS-8923
URL: https://issues.jboss.org/browse/JBAS-8923
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JSF
Affects Versions: 6.0.0.Final
Environment: RichFaces 4.0.0.20110227-CR1 r.21967
Mojarra 2.1.0-FCS
JBoss AS 6.0.0.Final (default profile)
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
http://anonsvn.jboss.org/repos/richfaces/modules/tests/metamer/tags/metam...
Reporter: Lukas Fryc
Assignee: Stan Silvert
When new profile Mojarra-2.1 (with 2.1.0-b11 libs) is created and WAR without jsf-libs is deployed, application works fine.
But when JSF is bundled into WAR (and use WAR_BUNDLES_JSF_IMPL param) and deployed onto default Mojarra-2.0 profile, it doesn't work with exception bellow.
Shortened stacktrace:
17:42:14,288 ERROR [[/metamer]] Error configuring application listener of class com.sun.faces.application.ServletContextSensitiveSingletonStore: java.lang.InstantiationException: com.sun.faces.application.ServletContextSensitiveSingletonStore
at java.lang.Class.newInstance0(Class.java:357) [:1.6.0_20]
at java.lang.Class.newInstance(Class.java:325) [:1.6.0_20]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:280) [:6.0.0.Final]
at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInstance(TomcatInjectionContainer.java:264) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3319) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_20]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_20]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_20]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months