[Installation, Configuration & DEPLOYMENT] - MBeans waiting for other MBeans
by aroeder
I am running a JBoss 4.2.3 AS and I keep getting these errors, but everything seems to work. What can I do against these errors:
anonymous wrote :
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=Invoker
| jboss.web:service=WebServer
|
| ObjectName: jboss:service=juddi
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=DefaultDS
|
| ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| jboss.jca:service=DataSourceBinding,name=DefaultDS
|
| ObjectName: jboss.mq:service=StateManager
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=DefaultDS
| Depends On Me:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq:service=DestinationManager
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=MessageCache
| jboss.mq:service=PersistenceManager
| jboss.mq:service=StateManager
| jboss.mq:service=ThreadPool
| jboss:service=Naming
| Depends On Me:
| jboss.mq.destination:service=Topic,name=testTopic
| jboss.mq.destination:service=Topic,name=securedTopic
| jboss.mq.destination:service=Topic,name=testDurableTopic
| jboss.mq.destination:service=Queue,name=testQueue
| jboss.mq.destination:service=Queue,name=A
| jboss.mq.destination:service=Queue,name=B
| jboss.mq.destination:service=Queue,name=C
| jboss.mq.destination:service=Queue,name=D
| jboss.mq.destination:service=Queue,name=ex
| jboss.mq:service=SecurityManager
| jboss.mq.destination:service=Queue,name=DLQ
|
| ObjectName: jboss.mq:service=PersistenceManager
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=DefaultDS
| Depends On Me:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq.destination:service=Topic,name=testTopic
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
|
| ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
|
| ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=testQueue
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=A
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=B
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=C
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=D
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq.destination:service=Queue,name=ex
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
|
| ObjectName: jboss.mq:service=Invoker
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=TracingInterceptor
| jboss:service=Naming
| Depends On Me:
| jboss.mq:service=InvocationLayer,type=HTTP
| jboss.mq:service=InvocationLayer,type=JVM
| jboss.mq:service=InvocationLayer,type=UIL2
|
| ObjectName: jboss.mq:service=TracingInterceptor
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=SecurityManager
| Depends On Me:
| jboss.mq:service=Invoker
|
| ObjectName: jboss.mq:service=SecurityManager
| State: CONFIGURED
| I Depend On:
| jboss.security:service=JaasSecurityManager
| jboss.mq:service=DestinationManager
| Depends On Me:
| jboss.mq.destination:service=Topic,name=testTopic
| jboss.mq.destination:service=Topic,name=securedTopic
| jboss.mq.destination:service=Topic,name=testDurableTopic
| jboss.mq.destination:service=Queue,name=testQueue
| jboss.mq:service=TracingInterceptor
| jboss.mq.destination:service=Queue,name=DLQ
|
| ObjectName: jboss.mq.destination:service=Queue,name=DLQ
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=DestinationManager
| jboss.mq:service=SecurityManager
|
| ObjectName: jboss.mq:service=InvocationLayer,type=JVM
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=Invoker
|
| ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
| State: CONFIGURED
| I Depend On:
| jboss.mq:service=Invoker
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
| State: NOTYETINSTALLED
| Depends On Me:
| jboss:service=juddi
| jboss:service=KeyGeneratorFactory,type=HiLo
| jboss.mq:service=StateManager
| jboss.mq:service=PersistenceManager
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207629#4207629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207629
17 years, 4 months
[JCA/JBoss] - MESSAGE DRIVEN BEAN USING mail-ra.rar STOPS WORKING
by pjr444
Hi.
(NOTE : I have posted this in the EJB3 Forum too)
I've been using a simple Message Driven Bean to grab new emails from an imap account for the last 18 months very successfully on 4.2.1 GA
Bean code :
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.mail.Message;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import org.jboss.annotation.ejb.ResourceAdapter;
import org.jboss.resource.adapter.mail.inflow.MailListener;
/**
* EJB3 Message-Driven Bean (MDB).
* Called for every email received to an IMAP account
*
*/
@MessageDriven(activationConfig={
@ActivationConfigProperty(propertyName="mailServer", propertyValue="mail.philips.local"),
// @ActivationConfigProperty(propertyName="port", propertyValue="10143"),
@ActivationConfigProperty(propertyName="mailFolder", propertyValue="INBOX"),
@ActivationConfigProperty(propertyName="storeProtocol", propertyValue="imap"),
@ActivationConfigProperty(propertyName="userName", propertyValue="anemailadd(a)somewhere.org.uk"),
@ActivationConfigProperty(propertyName="password", propertyValue="????????"),
@ActivationConfigProperty(propertyName="debug", propertyValue="false"),
@ActivationConfigProperty(propertyName="pollingInterval", propertyValue="30000"),
@ActivationConfigProperty(propertyName="maxMessages", propertyValue="5")
})
@ResourceAdapter("mail-ra.rar")
public class ReceiverMDB implements MailListener
{
@PersistenceContext(unitName = "default")
private EntityManager em;
public void onMessage(Message msg)
{
ReceiveTools.receiveForm(msg, em);
}
(NOTE : I believe 'maxMessages' is ignored, so doesn't do anything)
Recently, we have been doing some testing on upgrading to 4.2.3 and something seems to be effecting this bean on our live server - Now when JBoss starts the bean triggers once and will happily devour 450 emails. But once it's finished getting the first block of pending emails, it never triggers again.
There's no exceptions. The bean's 'onMessage' never seems to get triggered. Even going onto the JBoss Console and stopping/starting/destroying/creating etc doesn't get the bean working.
Worse still going back to 4.2.1 doesn't seem to help. And only restarting JBoss clears the pending emails.
Does anyone have experience of similar issues with MDBs, especially with the mail-ra.rar resource? Or can anyone help?
THANKS
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207627#4207627
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207627
17 years, 4 months
[Installation, Configuration & DEPLOYMENT] - Re: DefaultDS - Replacing HSQL with Oracle
by bpradhan
Hi, Please refer chapter 14 in installation and getting started guide for Jboss 4.2.2/5.0. ( from jboss.org)
If you retain 'DefaultDS' name for oracle, ( you may prefer it as it does not require changing configuration of those services using database using DefaultDS)
For this you may have to remove hsql ds xml from deploy dir..and put oracle-ds-xml..
a) Yes, you will see many tables created by Jboss in your databse as 'DefaultDS' is used as data source in other Jboss servicess such as messaging, JAAS, etc...
b) You may create a simple database client test app as follows.. create a test.jsp with following contents..
| <%@page contentType="text/html"
| import="java.util.*,javax.naming.*,javax.sql.DataSource,java.sql.*"
| %>
| <%
| DataSource ds = null;
| Connection con = null;
| PreparedStatement pr = null;
| InitialContext ic;
| try {
| ic = new InitialContext();
| ds = (DataSource)ic.lookup( "java:/DefaultDS" );
| con = ds.getConnection();
| pr = con.prepareStatement("SELECT col1, col2 FROM <your table name in oracle DB>"); // any test sql, or its variant
| ResultSet rs = pr.executeQuery();
| while (rs.next()) {
| out.println("<br> " +rs.getString("col1") + " | " +rs.getString("col2"));
| }
| rs.close();
| pr.close();
| }catch(Exception e){
| out.println("Exception thrown " +e);
| }finally{
| if(con != null){
| con.close();
| }
| } %>
|
|
create a directory test.war in $JBOSS_HOME\server\{your svr confg such as default}\deploy\
Put this test.jsp under test.war
test the jsp at http://localhost:8080/test/test.jsp
hope this helps..
Cheers,
bpradhan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207624#4207624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207624
17 years, 4 months