[JBoss Messaging] - Is the destination for DLQ mandatory?
by ckaushalya
Hi All,
I'm using JBoss [EAP] 4.3.0.GA_CP01 with clustering.
I have defined a new destination in the destinations-service.xml and commented all rest of the predefined destinations including the destination of the default dead letter queue (DLQ).
Now I'm getting the following error at deployment time. This error goes away when I un-comment the DLQ destination.
Is the DLQ destination mandatory? or enabling it just hides my real error, instead of solving it?
15:09:34,678 WARN [JMSContainerInvoker] JMS provider failure detected for My_Message_Driven _Bean_Name
| javax.naming.NameNotFoundException: queue/DLQ
| at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242)
| at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:192)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
| at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:664)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:991)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171451#4171451
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171451
17 years, 8 months
[JBoss Tools (users)] - Problems with CRUD - Application (Jboss Tools Eclipse)
by Smoeker
hi there,
i have some problems working with a jbosstools - generated Seam Crud Application :
I generated the xhtmls/entity Beans/ DAOs by reverse engineering from an existing database.
-> the Crud - pages work fine, but i have problems implementing my own logic :
i generated a new seam form "loginForm", in which i just wanted to test finding a database entry for an entered value using an Existing EntityQuery CustomerList (also generated from JbossTools).
heres the layout :
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:s="http://jboss.com/products/seam/taglib"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:rich="http://richfaces.org/rich"
xmlns:a="http://richfaces.org/a4j">
<h2 align="center"> Login Webshop</h2>
<h:messages globalOnly="true" styleClass="message"/>
<h:form id="loginFormForm" styleClass="edit">
<rich:simpleTogglePanel label="Customer search parameters" switchType="ajax">
<f:facet name="header">loginForm</f:facet>
<h:outputLabel value="Username" style="width:500">
</h:outputLabel>
<h:inputText id="email" value="#{customerList.customer.email}"/>
</rich:simpleTogglePanel>
<h:commandButton id="search" value="UserSearch" action="/loginForm.xhtml"/>
</h:form>
<rich:panel>
<h:outputText value="The search returned no results."
rendered="#{empty customerList.resultList}"/>
<h:dataTable id="customerList"
var="customer"
value="#{customerList.resultList}"
rendered="#{not empty customerList.resultList}">
<h:column>
<f:facet name="header">KundenKredit</f:facet>
#{customer.creditLimit}
</h:column>
<h:column>
<f:facet name="header">email</f:facet>
#{customer.email}
</h:column>
</h:dataTable>
</rich:panel>
</ui:composition>
The EntityQueryClass looks as follows :
package de.medint.webshop.session;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.framework.EntityQuery;
import de.medint.webshop.entity.*;
import java.util.List;
import java.util.Arrays;
@Name("customerList")
public class CustomerList extends EntityQuery {
private static final String[] RESTRICTIONS = {
"lower(customer.email) like concat(lower(#{customerList.customer.email}),'%')" };
private Customer customer = new Customer();
@Override
public String getEjbql() {
return "select customer from Customer customer";
}
@Override
public Integer getMaxResults() {
return 25;
}
public Customer getCustomer() {
return customer;
}
@Override
public List getRestrictions() {
return Arrays.asList(RESTRICTIONS);
}
}
When i call the layout via Browser, i always get the whole content of the table shown, even if i enter an invalid or valid value....
Watching the ConsoleLog it seems, as if my Querys is executed with a where clause, but directly after that, the same query is executed without where clause. (i think, the resultlist gets overwritten by the queryresult without where...)
Can somebody please explain me that behaviour?
thnx alot
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171449#4171449
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171449
17 years, 8 months
[Installation, Configuration & DEPLOYMENT] - Error [org.jboss.ha.framework.server.ClusterPartition]
by nareshgali
Hi,
I tried to start the jboss 3.2.7 server and i its failing to start up properly
its showing the following trace, Could anyone analyze the problem:
here the log:
2008-08-20 14:35:26,095 ERROR [org.jboss.ha.framework.server.ClusterPartition] Initialization failed jboss:service=DefaultPartition
ChannelException: unable to setup the protocol stack
at org.jgroups.JChannel.(JChannel.java:217)
at org.jgroups.JChannel.(JChannel.java:189)
at org.jboss.ha.framework.server.ClusterPartition.createService(ClusterPartition.java:230)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:219)
at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy18.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:327)
at org.jboss.system.ServiceController.create(ServiceController.java:272)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.create(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:213)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:415)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:191)
at org.jboss.Main$1.run(Main.java:480)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NumberFormatException: For input string: "@mcast_port@"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at org.jgroups.protocols.UDP.setProperties(UDP.java:404)
at org.jgroups.stack.Protocol.setPropertiesInternal(Protocol.java:219)
at org.jgroups.stack.Configurator$ProtocolConfiguration.createLayer(Configurator.java:611)
at org.jgroups.stack.Configurator.createProtocols(Configurator.java:265)
at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:55)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:114)
at org.jgroups.JChannel.(JChannel.java:214)
... 95 more
2008-08-20 14:35:34,515 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss:service=DefaultPartition
state: FAILED
I Depend On:
Depends On Me: jboss:service=HASessionState
jboss:service=HAJNDI
jboss.cache:service=InvalidationBridge,type=JavaGroups
MBeanException: ChannelException: unable to setup the protocol stack
Cause: ChannelException: unable to setup the protocol stack
ObjectName: jboss:service=HASessionState
state: CONFIGURED
I Depend On: jboss:service=DefaultPartition
Depends On Me:
ObjectName: jboss:service=HAJNDI
state: CONFIGURED
I Depend On: jboss:service=DefaultPartition
Depends On Me:
ObjectName: jboss.cache:service=InvalidationBridge,type=JavaGroups
state: CONFIGURED
I Depend On: jboss:service=DefaultPartition
jboss.cache:service=InvalidationManager
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss:service=DefaultPartition
state: FAILED
I Depend On:
Depends On Me: jboss:service=HASessionState
jboss:service=HAJNDI
jboss.cache:service=InvalidationBridge,type=JavaGroups
MBeanException: ChannelException: unable to setup the protocol stack
Cause: ChannelException: unable to setup the protocol stack
Thanks in Advance,
Naresh G
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171448#4171448
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171448
17 years, 8 months
[Clustering/JBoss] - Stateful Session replication not working......
by fmarchioni
Hello,
I'm trying a basic Cluster SFSB which autoincrements a fields....
@Stateful
| @Clustered
| public class HelloBean implements HelloBeanItf,Serializable {
| int counter = 0;
| public void doSomething() {
| counter++;
| System.out.println("Value of counter is " + counter);
|
| }
The code is recalled by a JSP
<%!
| HelloBeanItf ejb = null;
|
| public void jspInit () {
| try {
|
|
| InitialContext ctx = new InitialContext();
|
| ejb = (HelloBeanItf) ctx.lookup("cluster/HelloBean/local");
| }
| catch (Exception exc) { exc.printStackTrace();
| }
| }
|
|
| %>
|
| <%
| ejb.doSomething();
| %>
|
Unfortunately when I invoke the JSP the session seems not to replicate...in other words I can see the server is load balancing the calls between nodes but the value stays the same when moves from one node to the other
Node 1: 11:03:42,859 INFO [STDOUT] Value of counter is 11
| Node 2: 11:03:42,859 INFO [STDOUT] Value of counter is 11
| Node 1: 11:03:42,859 INFO [STDOUT] Value of counter is 12
| Node 2: 11:03:42,859 INFO [STDOUT] Value of counter is 12
The cluster works fine on the HTTP side (I have seen the HTTP session gets replicated) so the problem is only on SFSB.
Do I need any additional configuration besides the @Clustered notation ?
I'm using JBoss 4.2.0 version.
Thanks a lot
Francis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171446#4171446
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171446
17 years, 8 months