[JBoss Messaging] - Error running standalone configuration
by jaink
We are running JBM 1.2.0.GA on JBoss AS 4.0.4.GA. On using the "standalone" installation for installing bare minimum configuration we get the following error
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss:service=invoker,type=jrmp
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
|
| ObjectName: jboss:service=TransactionManager
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.web:service=WebServer
| jboss.messaging:service=PersistenceManager
| jboss.messaging:service=PostOffice
| jboss.messaging:service=JMSUserManager
| jboss.jca:service=WorkManager
| jboss.jca:service=RARDeployer
| jboss.jca:service=CachedConnectionManager
| jboss.jca:service=LocalTxCM,name=DefaultDS
|
| ObjectName: jboss.security:service=JaasSecurityManager
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.web:service=WebServer
|
| ObjectName: jboss:service=Naming
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
| jboss.jmx:alias=jmx/rmi/RMIAdaptor
|
| ObjectName: jboss.jdbc:service=metadata
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.jdbc:service=metadata,datasource=DefaultDS
|
| ObjectName: jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar'
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
|
|
Also looking at the logs, we see the following exception
| java.lang.NoSuchMethodException: org.jboss.jmx.connector.invoker.AuthenticationInterceptor.<init>(org.jboss.mx.server.MBeanInvoker)
| at java.lang.Class.getConstructor0(Class.java:2647)
| at java.lang.Class.getConstructor(Class.java:1629)
| at org.jboss.mx.modelmbean.ModelMBeanInvoker.getInterceptors(ModelMBeanInvoker.java:739)
| at
| org.jboss.mx.modelmbean.ModelMBeanInvoker.configureInterceptorStack(ModelMBeanInvoker.java:678)
| at org.jboss.mx.modelmbean.XMBean.configureInterceptorStack(XMBean.java:400)
| at org.jboss.mx.modelmbean.ModelMBeanInvoker.init(ModelMBeanInvoker.java:504)
| at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:486)
| at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
|
|
Its seems like there is a mismatch somewhere but we have not been able to nail it down.
Thanks for the help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030235#4030235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030235
19Â years, 1Â month
[JBoss jBPM] - Re: problem with deployment
by j.wozniakowski
1. Server deployer should be: "/jbpm/upload", but
2. There are two bugs in UploadServlet in JBPM web application, so probably this is why you are not able to deploy process:
a) wrong mime type check - I solved it by commenting this piece of code in UploadServlet:
/*
if (fileItem.getContentType().indexOf("application/x-zip-compressed") == -1) {
log.debug("Not a process archive");
return "Not a process archive";
}
*/
b) bad JbpmContext retrieve call (deprecated method returning null)- my solution:
in doDeployment method replace this:
JbpmContext jbpmContext = JbpmContext.getCurrentJbpmContext();
by this:
JbpmContext jbpmContext = JbpmConfiguration.getInstance().createJbpmContext();
[...method code here...]
jbpmContext.close();
Generally same errors exist in DeployServlet - after fixing DeployServlet you are able to deploy process through HTML form.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030230#4030230
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030230
19Â years, 1Â month
[JCA/JBoss] - Re: Jboss 4.2.0CR1 -
by omerlin
Hello Mark and weston,
First of all, thanks for your help - i really don't know what to do because this code is running without problem on Glassfish .
Mark,
I don't see anywhere in my trace that a transaction was previously marked as ROLLBACK-ONLY. When the error occurs, the transaction is rollbacked ( you can see this in my trace ) but before ... i saw nothing on this, neverthess ilooked for this in the whole trace and i have the maximum trace level set in jbossjta-properties.xml :
How can i see that the transaction was previously marked as rollback ?
Weston,
do we still speak of JBossTS - i believed JTA/Arjuna was new in 4.2.x ?
I don't see how to activate TRACE on JCA in my jboss-log4j.xml - nothing to uncomment ?
Here is my DS configuration file :
---------------------------------------------------
<local-tx-datasource>
<jndi-name>jdbc/otainfra-ds</jndi-name>
<use-java-context>false</use-java-context>
<connection-url>jdbc:oracle:thin:@londres:1521:MMSERVER</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>demo</user-name>
demo
<type-mapping>Oracle9i</type-mapping>
</local-tx-datasource>
-------------------------------------------------------------------------
Thx,
Olivier
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030228#4030228
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030228
19Â years, 1Â month
EJB3 MDB clustering and hasingleton
by Jeanmougin, Francois
Hi everybody,
I'm trying to configure JBoss to make an EJB3 MDB run only on the JBoss cluster member in which the JMS server is running. I need a pure failover cluster configuration for JBoss.
I tried several solutions using the 'barrier' dependency and trying to put the ejb ear file (alone and with te EJB deployers) in the deploy-hasingleton directory but none works.
The only thing that would work would be (for what I understood) to put the barrier on the deployers, but then, when the old EJB deployers wakes up, it tries to deploy the EJB and not the EJB3Deployer, and this old EJB deployer is not able to deploy the EJB3 MDB.
So, could anyone explain what is the cleanest way to clusterize such EJB3 MDB ?
Thank you,
François.
Context : jboss-4.0.5.GA, Red Hat Enterprise Linux ES release 4 (Nahant Update 4).
19Â years, 1Â month
