[JBossMQ] - Can you help me?
by gp_len
When i learn JMS use and seting,I experience some problems
First,I explain the environment,i'm using:
jboss-4.0.5GA
Windows xp
jdk 1.5.0_04
the JMS service is configured to store messages via Mysql5.0.
the datasource is: MySqlDS
the following questions:
10:22:45,986 ERROR [MainDeployer] Could not create deployment: file:/D:/GreenSoft/jboss-4.2.2.GA/server/default/deploy/jms/mysql-jdbc2-service.xml
org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq:service=DestinationManager
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
======================
\server\default\deploy\jms\jbossmq-destinations-service.xml
Content:
-------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort $ -->
<!--
| This file defines the default Queues and Topics that JBossMQ
| ships with. The default Queues and Topics are used by the
| JBoss test suite and by the sample jms programs.
|
| You can add other destinations to this file, or you can create other
| *-service.xml files to contain your application's destinations.
-->
<!-- Destination without a configured SecurityManager or without a
a SecurityConf will default to role guest with read=true, write=true,
create=false.
-->
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
-1
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
------------------End--------------------
\server\default\deploy\jms\mysql-jdbc2-service.xml
Content:
--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: mysql-jdbc2-service.xml 39343 2005-12-29 16:32:35Z ltexier $ -->
<!-- ==================================================================== -->
<!-- Persistence and caching using MySQL -->
<!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
<!-- -->
<!-- ==================================================================== -->
<!--
| The destination manager is the core service within JBossMQ
-->
<depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache
<depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager
<depends optional-attribute-name="StateManager">jboss.mq:service=StateManager
<!--
| The MessageCache decides where to put JBossMQ message that
| are sitting around waiting to be consumed by a client.
|
| The memory marks are in Megabytes. Once the JVM memory usage hits
| the high memory mark, the old messages in the cache will start getting
| stored in the DataDirectory. As memory usage gets closer to the
| Max memory mark, the amount of message kept in the memory cache aproaches 0.
-->
50
60
jboss.mq:service=PersistenceManager
<!-- The PersistenceManager is used to store messages to disk. -->
<!--
| The jdbc2 PersistenceManager is the new improved JDBC implementation.
| This implementation allows you to control how messages are stored in
| the database.
|
| This jdbc2 PM configuration has was supplied by Stephane Nicoll in the forums as an example for MySQL
-->
<depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=MySqlDS
BLOB_TYPE=BYTES_BLOB
INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
DELETE_MARKED_MESSAGES_WITH_TX = DELETE JMS_MESSAGES FROM JMS_MESSAGES, JMS_TRANSACTIONS WHERE JMS_MESSAGES.TXID = JMS_TRANSACTIONS.TXID AND JMS_MESSAGES.TXOP=?
DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB LONGBLOB, PRIMARY KEY (MESSAGEID, DESTINATION))
CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
CREATE_TABLES_ON_STARTUP = TRUE
<!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
<!--attribute name="RecoveryTimeout">0</attribute-->
<!-- The number of blobs to load at once during message recovery -->
1
-------------------------------------------------------------------------
Anybody can help?
THX
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207197#4207197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207197
17 years, 3 months
[JBoss Portal] - Re: The curious case of the magical portlet ...
by guybedo
yes the roles defined are correct.
Actually i have solved one my two issues: the portletB / portletA problem.
It seems that portletB was not really correctly deployed, even if the portlet was displayed and behaved correctly.
There was a bean naming error in the spring applicationContext.
The strange thing is that portletB was correctly deployed, displayed and was fully functionnal. But it seems that this spring configuration error prevented the portletA from being deployed as it was the next portlet in the deployment order.
There was nothing in the server logs related to this error.
Well i now have one problem left, the real magical portlet, as this one is displayed if and only if it is the only one portlet in the portal.
It must be some kind of configuration problem too but the real pain is the total lack of log.
I can't understand why there is nothing in the server logs, even in debug mode.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207187#4207187
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207187
17 years, 3 months
[Clustering/JBoss] - TomcatClusteringCache & Session replication
by ozguy
Hi,
I am using Jboss 4.2.3 and jboss-portal-ha.sar 2.6 in a clustered environment where i have 2 nodes.
I have WebMUX load balancer infront of the jboss nodes.
When i access my portlet application , i can see the session replication details in the jTomcatClusteringCache is present in both the nodes with the same sessionid.
Onces i shut down the node that was handling the request before, i expect the another node to take over and continue from where it was left. This doesn't seem to happen.
When call getPortletSession(false) in the another node, it returns null. For some reason portlet is not able to access the Session it suppose to.
The Tomcat cache looks like this onces the other node was shut down:
JSESSION
/localhost
/LoginGenerator
/f4oMmaFoWGJfhI8PsN-C8g**
VERSION: 47
f4oMmaFoWGJfhI8PsN-C8g**: [B@173cf45
/portal
/f4oMmaFoWGJfhI8PsN-C8g**
VERSION: 16
f4oMmaFoWGJfhI8PsN-C8g**: [B@2cf42d
/SSO
/E652F58BAAA8F69E96BC42DE3D9233AE
/sessions
key: []
/credentials
key: org.jboss.web.tomcat.service.sso.TreeCacheSSOClusterManager$SSOCredentials@11addf0
Session id that should contain the object is present in the cache f4oMmaFoWGJfhI8PsN-C8g** but the object i expect to be in there is null.
jboss-web.xml:
<replication-config>
<replication-trigger>SET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
web.xml:
i have
<listener-class>org.jboss.portal.portlet.session.SessionListener</listener-class>
jboss-portlet.xml:
<portlet-name>LoginGeneratorPortlet</portlet-name>
<header-content>
</header-content>
<session-config>
true
</session-config>
Any help will be appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207185#4207185
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207185
17 years, 3 months