[JBoss JIRA] Created: (JBAS-9422) Minimal server fails to start due to CNFE
by Shelly McGowan (JIRA)
Minimal server fails to start due to CNFE
-----------------------------------------
Key: JBAS-9422
URL: https://issues.jboss.org/browse/JBAS-9422
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
Fix For: 6.1.0
Failed to boot JBoss:
java.lang.Exception: Encountered exception in server startup
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.bootstrapMcAndDescriptors(AbstractMCServerBase.java:350)
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.doStart(AbstractMCServerBase.java:282)
at org.jboss.bootstrap.impl.as.server.AbstractJBossASServerBase.doStart(AbstractJBossASServerBase.java:381)
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:413)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: Incompletely deployed:
DEPLOYMENTS IN ERROR:
Deployment "DeclaredStructure" is in error due to: java.lang.ClassNotFoundException: org.jboss.deployment.ExplicitDeclaredStructure
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:278)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174)
at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.bootstrapMcAndDescriptors(AbstractMCServerBase.java:339)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBMESSAGING-1889) Duplicate messages are produced during cluster failover when a cluster node is shutdown
by Tom Ross (JIRA)
Duplicate messages are produced during cluster failover when a cluster node is shutdown
---------------------------------------------------------------------------------------
Key: JBMESSAGING-1889
URL: https://issues.jboss.org/browse/JBMESSAGING-1889
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.8.SP1
Environment: JBoss EAP 5.1.1
Reporter: Tom Ross
Assignee: Yong Hao Gao
The scenarion describes a set-up consisting of JBoss cluster and a stand alone JBoss instance hosting a MDB.
During the test the master node of the JBoss cluster is shutdown using CTRL/C or shutdown.sh script.
The following is a description of the events that hava happened that lead to duplicate messages.
- Message is delivered to a MDB from node-1 of the cluster to a MDB in a transaction. The transaction prepare has failed because the server peer of node-1 is shutting down.
- Message is rolled back and received again in another transaction. This happens at the client side only. Then the transaction is committed on node-2 as the client has failed over to node-2 of the cluster.
- Meanwhile the fact that node-1 is shutting down causes server side failover to happen and the message is failed over to node-2.
- node-2 redelivers the message to the MDB in a separate transaction and committs.
So the message is received twice.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1349) JAX-RS sub resources broken
by Jozef Hartinger (JIRA)
JAX-RS sub resources broken
---------------------------
Key: AS7-1349
URL: https://issues.jboss.org/browse/AS7-1349
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.0.0.Final
Reporter: Jozef Hartinger
Assignee: Stuart Douglas
Priority: Critical
Fix For: 7.0.1.Final
Having a root resource class
@Path("person")
public class PeopleResource {
@Path("{name}")
public PersonResource findPerson(@PathParam("name") String name)
{
return new PersonResource(name);
}
}
and a sub resource class
public class PersonResource {
private String name;
public PersonResource(String name) {
this.name = name;
}
@GET
public String getName()
{
return name;
}
@GET
@Path("/address")
public String getClassName()
{
return name + "'s address is unknown.";
}
}
The application fails with the following exception. Seems like during scanning the subresource is identified as a root resource (although it is not a root resource). Subsequently, RESTEasy's validation fails.
javax.servlet.ServletException: Servlet.init() for servlet org.jboss.resteasy.cdi.test.MyApplication threw exception
org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
java.lang.Thread.run(Thread.java:662)
root cause
java.lang.RuntimeException: Class is not a root resource. It, or one of its interfaces must be annotated with @Path: org.jboss.resteasy.cdi.test.Subresource implements: java.io.Serializable
org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:104)
org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:83)
org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:72)
org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:367)
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:225)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1373) Setting EJB's InjectionTarget does not work
by Jozef Hartinger (JIRA)
Setting EJB's InjectionTarget does not work
-------------------------------------------
Key: AS7-1373
URL: https://issues.jboss.org/browse/AS7-1373
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.0.0.Final
Reporter: Jozef Hartinger
Assignee: Stuart Douglas
Priority: Blocker
Fix For: 7.0.1.Final
Having an EJB
{code}
@Singleton
public class Bus {
private boolean initialized = false;
public boolean isInitialized() {
return initialized;
}
public void setInitialized(boolean initialized) {
this.initialized = initialized;
}
}
{code}
and a CDI extension that wraps EJB's InjectionTarget
{code}
public class WrappingExtension implements Extension {
public void wrapInjectionTarget(@Observes ProcessInjectionTarget<Bus> event)
{
final InjectionTarget<Bus> injectionTarget = event.getInjectionTarget();
event.setInjectionTarget(new ForwardingInjectionTarget<Bus>() {
@Override
public void inject(Bus instance, CreationalContext<Bus> ctx) {
super.inject(instance, ctx);
instance.setInitialized(true);
}
@Override
public InjectionTarget<Bus> getDelegate() {
return injectionTarget;
}
});
}
}
{code}
the InjectionTarget implementation is never invoked. When the Bus bean is changed to a CDI bean (@Singleton annotation is removed), the InjectionTarget implementation is invoked as expected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1385) make storeAsBinary configurable
by Michal Linhard (JIRA)
make storeAsBinary configurable
-------------------------------
Key: AS7-1385
URL: https://issues.jboss.org/browse/AS7-1385
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.0.0.Final
Reporter: Michal Linhard
Assignee: Paul Ferraro
Priority: Critical
we need be able to turn on/off these infinispan config options
infinispan.configuration.storeAsBinary.enabled
infinispan.configuration.lazyDeserialization.enabled
it's not yet known what causes performance degradation in JBPAPP-6865,
but we need to be able to eliminate effect of these params
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months