[JBoss-user] [Management, JMX/JBoss] - MBeanException: Exception in MBean operation 'start()'

2004-04-06 Thread Amresh
We use the jmx RMIAdaptor with in JBoss to stop and start a MDB once every day.

The MBean has been working without any problem for 3-4 months except twice when we got 
the following exception.

Caused by: MBeanException: Exception in MBean operation 'start()'
  | Cause: javax.naming.NameAlreadyBoundException; remaining name 'env'
  | at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:303)
  | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
  | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | at 
org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:249)
  | at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source)
  | at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:324)
  | at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
  | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
  | at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
  | at 
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:90)
  | at 
org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:58)
  | at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45)
  | at 
org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:55)
  | at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
  | at $Proxy20.invoke(Unknown Source)


Has anyone come across similar problem? The relevant code is:

 String name = "jmx/rmi/RMIAdaptor";
  |  InitialContext ic = new InitialContext();
  |  RMIAdaptor rmiAdaptor = (RMIAdaptor) ic.lookup(name);
  |  rmiAdaptor.invoke("jboss.j2ee:jndiName=local/testmdb,service=EJB", "start", null, 
null);


Amresh


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3829471#3829471

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3829471


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - Re: MDB ACTIVE but stops consuming

2004-03-29 Thread Amresh
Thanks

I will have give this a  try.

Amresh

http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827874#3827874";>View 
the original post

http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827874>Reply 
to the post


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - Re: MDB ACTIVE but stops consuming

2004-03-26 Thread Amresh
Hi Adrian,

With reference to the previous posts.

We moved to JBoss3.2.3 a month back. All was going fine till today morning when we 
received alerts stating messages building up inspite of the MDB being active.

On investigating the logs I found 

2004-03-26 07:50:04,217 INFO  Thread Pool Worker-496 MDB received JMS object message 
with JMS ID ID:31-1080287404179103
2004-03-26 07:50:04,429 INFO  Thread Pool Worker-496  Processing of message 
[JMSMessageId=ID:31-1080287404179103] succeeded
2004-03-26 07:56:00,542 INFO  Thread Pool Worker-498 MDB received JMS object message 
with JMS ID ID:29-1080287760462649

The single instance of MDB that we have was using different threads from Thread Pool 
Worker pool. Most of the time the switch was quick however in this case the MDB took 6 
minutes to move to a new thread. 

During these 6 minutes there were around 800 messages piled up on the queue.

To make things worst there were similar pauses immediately afterwards too (ranging 
from 40 sec to 3 mins).

Is this a case of an instance of MDB being destroyed by the container to start a new 
instance?

Or is it the server starving of execute threads?


Any help would be highly appreciated.

Rgds,

Amresh








http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827639#3827639";>View 
the original post

http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827639>Reply 
to the post


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - Re: During startup server tries to load all messages in a JM

2004-02-26 Thread Amresh
Adrian thanks for your reply.

It would be good to know your ideas on this. If possible I would like try adding this 
feature myself. 

When you say sybase config to you mean the sybase-jdbc2-service.xml. If yes here it is:




  | 
  | 
  | 
  | 
  | 
  |   
  |   
  |   
  |   
  | 
  |   
  |   
  | jboss.mq:service=MessageCache
  | jboss.mq:service=PersistenceManager
  | jboss.mq:service=StateManager
  |   
  | 
  |   
  |   
  | 50
  | 60
  | jboss.mq:service=PersistenceManager
  |   
  | 
  |   
  |   
  |   
  |   
  | 
  |   jboss.mq:service=MessageCache
  |   jboss.jca:service=LocalTxCM,name=jdbc/JMSLocalTxDataSource
  |   
  | BLOB_TYPE=BYTES_BLOB
  |   INSERT_TX = INSERT INTO dbo.JMS_TRANSACTIONS (TXID) values(?)
  |   INSERT_MESSAGE = INSERT INTO dbo.JMS_MESSAGES (MESSAGEID, 
DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
  |   SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM dbo.JMS_TRANSACTIONS
  |   SELECT_MAX_TX = SELECT MAX(TXID) FROM dbo.JMS_MESSAGES
  |   SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM 
dbo.JMS_MESSAGES WHERE DESTINATION=?
  |   SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM dbo.JMS_MESSAGES 
WHERE MESSAGEID=? AND DESTINATION=?
  |   MARK_MESSAGE = UPDATE dbo.JMS_MESSAGES SET TXID=?, TXOP=? WHERE 
MESSAGEID=? AND DESTINATION=?
  |   UPDATE_MESSAGE = UPDATE dbo.JMS_MESSAGES SET MESSAGEBLOB=? WHERE 
MESSAGEID=? AND DESTINATION=?
  |   UPDATE_MARKED_MESSAGES = UPDATE dbo.JMS_MESSAGES SET TXID=?, TXOP=? 
WHERE TXOP=?
  |   UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE dbo.JMS_MESSAGES SET TXID=?, 
TXOP=? WHERE TXOP=? AND TXID=?
  |   DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM dbo.JMS_MESSAGES WHERE 
TXID IN (SELECT TXID FROM dbo.JMS_TRANSACTIONS) AND TXOP=?
  |   DELETE_TX = DELETE FROM dbo.JMS_TRANSACTIONS WHERE TXID = ?
  |   DELETE_MARKED_MESSAGES = DELETE FROM dbo.JMS_MESSAGES WHERE TXID=? 
AND TXOP=?
  |   DELETE_MESSAGE = DELETE FROM dbo.JMS_MESSAGES WHERE MESSAGEID=? AND 
DESTINATION=?
  |   CREATE_MESSAGE_TABLE = CREATE TABLE dbo.JMS_MESSAGES ( MESSAGEID 
INTEGER NOT NULL, \
  |  DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER NULL, TXOP 
CHAR(1), \
  |  MESSAGEBLOB IMAGE, PRIMARY KEY (MESSAGEID, DESTINATION) )
  | CREATE_TX_TABLE = CREATE TABLE dbo.JMS_TRANSACTIONS ( TXID INTEGER 
)
  | SELECT_MARKED_MESSAGES_WITH_TX = SELECT MESSAGEID, MESSAGEBLOB, 
TXID, TXOP FROM dbo.JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM dbo.JMS_TRANSACTIONS) 
AND TXOP=?
  | INSERT_MARKED_MESSAGES_WITH_TX = INSERT INTO 
dbo.SAVED_JMS_MESSAGES SELECT * FROM dbo.JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM 
dbo.JMS_TRANSACTIONS) AND TXOP=?
  |   
  | 
  | 

And here is the datasource config:


  | jdbc/JMSLocalTxDataSource
  | jdbc:sybase:Tds:dev.gb.xxx.com:7300
  | com.sybase.jdbc2.jdbc.SybDriver
  | aaa
  | bbb
  | 5
  | 15
  | 



Rgds,

Amresh

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3823115#3823115

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3823115


---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - Re: During startup server tries to load all messages in a JM

2004-02-25 Thread Amresh
Thanks Stephane

Any idea when is JBoss 3.2.4 expected to be rolled out?

Also is this fix on Adrian's MUST HAVE list or NICE TO HAVE list.

Rgds,

Amresh

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822890#3822890

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822890


---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [Messaging, JMS & JBossMQ] - During startup server tries to load all messages in a JMS qu

2004-02-25 Thread Amresh
We are using JBoss 3.2.3 with Sybase as the JMS Store

If we restart JBoss with a significant number of messages (for eg above 15000) on any 
of the JMS queues. It takes very long time to start up. 

Logs suggest that the server is trying to load the JMS queue (one with a very high 
queue depth). At one point the the startup took a very long time and resulted in an 
out of memory exception. The only way we could get the server to start was by 
increasing the heap size from 256 to 512 (the other option was to delete/drain the 
queue).

Is there configuration to configure the server to not load the entire queue during 
startup?

Rgds,

Amresh


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822867#3822867

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822867


---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user