[Installation, Configuration & Deployment] - Re: unified invoker startup error
by bwarren
I've tried to get the attached code from here up and running
https://jira.jboss.org/jira/browse/JBPAPP-1274
I get this on startup:
| org.xml.sax.SAXException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". @ vfsfile:/C:/src/cbro/jboss-5.0.1.GA/server/default/deploy/http-uinvoker.sar/unified-invoker.war/WEB-INF/web.xml[195,11]
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
| at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
| at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257974#4257974
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257974
14 years, 7 months
[JBoss Cache Users] - Re: What is an invocation, and the related option override?
by alllle
Thanks for the reply.
So if I need to read a node, then write to it, such as:
| tm.begin();
| // force write lock even on read operations
| cache.getInvocationContext().getOptionOverrides().setForceWriteLock(true);
|
| // read node
| Object value = cache.get(myFqn, "key");
|
| // write node
| cache.put(myFqn, "key", "newValue");
|
| tm.commit();
|
Will the "setForceWriteLock(true)" applied to both cache.get() and cache.put() operations?
It looks like the InvocationContext is a ThreadLocal variable (looking at the CacheInvocationDelegate class), which means it lasts as long as the thread is still active. In other words, once I set the "setForceWriteLock(true)", all future cache related operations in this thread will see this option set to "true". And if a thread pool is used in my application for processing (such as a pool of JMS consumer threads), I won't know which options are set and which aren't.
Is my observation correct?
Thanks,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257971#4257971
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257971
14 years, 7 months
[JBoss Cache Users] - Re: JDBCCacheLoader failed to obtain connection with JNDI na
by schamarthi
I should have seen this before posting another similar issue. I have the same problem with jboss-common-core.jar with Jboss Portal 2.7.2(Base Jboss 4.2.3) , Spring 3.0.0.M3. When included, my other datasource, queue looks in Spring Context file are not recognized.
i been struggling for last two weeks to get around this problem.
However after removing the factory class from jar file as you have suggested in the JIRA issue, when I bind the cache to JNDI, I am getting the following exception
|
| caused by: java.io.NotSerializableException: org.jboss.cache.invocation.CacheInvocationDelegate
| at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
| at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
| at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
| at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
| at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
| at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
| at java.rmi.MarshalledObject.<init>(MarshalledObject.java:92)
| at org.jnp.interfaces.MarshalledValuePair.<init>(MarshalledValuePair.java:65)
| at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:508)
Can you tell me what is wrong with this ?
Appreciate any help in this regard.
thx & rgds,
Srinivas
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257969#4257969
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257969
14 years, 7 months
[jBPM Users] - Re: jbpm 4.1 installation problems on jboss 4.2.3
by pbaltz
Yes, I tried that, and it still has issues. Here's the relevant bean definition. (I tried the mbean name both the way you specified, and the way it shows up in JMX console.) Also, I've tried with and without the dataSource property specified in addition to the dependency.
| <bean name="org.jbpm:service=ProcessEngine"
| class="org.jbpm.integration.spi.JBPMService">
| <property name="serverConfig"><inject bean="org.jbpm:service=ServerConfig"/></property>
| <!--
| <property name="dataSource">
| <inject bean="jboss.jca:service=DataSourceBinding,name=JbpmDS" />
| </property>
| -->
| <depends>jboss.jca:name=JbpmDS,service=DataSourceBinding</depends>
| </bean>
|
This results in the following error with the ProcessEngine not bound in JNDI.
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbpm-service.sar#jbpm-service.beans'
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@17b51e8{name=file:/opt/jboss/jboss-4.2.3.GA/server/TDS/deploy/jbpm/jbpm-service.sar/jbpm-service.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData@13e6577{name=org.jbpm:service=KernelLocator bean=org.jbpm.integration.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData@1776d65{name=org.jbpm:service=ProcessEngine bean=org.jbpm.integration.spi.JBPMService properties=[serverConfig] constructor=null demands=[jboss.jca:name=JbpmDS,service=DataSourceBinding]}, AbstractBeanMetaData@1af1934{name=org.jbpm:service=ServerConfig bean=org.jbpm.integration.jboss4.mgmt.ServerConfig properties=[webServiceHost] constructor=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely deployed:
|
| *** DEPLOYMENTS MISSING DEPENDENCIES:
| org.jbpm:service=ProcessEngine -> org.jbpm:service=ServerConfig{Configured:Installed}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Create:NOT FOUND}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Start:NOT FOUND}
| )
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbpm-service.sar#jbpm-service.beans'
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@17b51e8{name=file:/opt/jboss/jboss-4.2.3.GA/server/TDS/deploy/jbpm/jbpm-service.sar/jbpm-service.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData@13e6577{name=org.jbpm:service=KernelLocator bean=org.jbpm.integration.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData@1776d65{name=org.jbpm:service=ProcessEngine bean=org.jbpm.integration.spi.JBPMService properties=[serverConfig] constructor=null demands=[jboss.jca:name=JbpmDS,service=DataSourceBinding]}, AbstractBeanMetaData@1af1934{name=org.jbpm:service=ServerConfig bean=org.jbpm.integration.jboss4.mgmt.ServerConfig properties=[webServiceHost] constructor=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely deployed:
|
| *** DEPLOYMENTS MISSING DEPENDENCIES:
| org.jbpm:service=ProcessEngine -> org.jbpm:service=ServerConfig{Configured:Installed}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Create:NOT FOUND}, jboss.jca:name=JbpmDS,service=DataSourceBinding{Start:NOT FOUND}
| )
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257967#4257967
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257967
14 years, 7 months
[Installation, Configuration & Deployment] - Re: JBOSS runs as a service, but will not autostart
by geneellis
Ok I see. I will make this changes tonight and let you know what I find. I am not using that exact script, but a simplified version. Basically this one:
#! /bin/sh
|
|
| start(){
| echo "Starting jboss.."
|
| # If using an SELinux system such as RHEL 4, use the command below
| # instead of the "su":
| # eval "runuser - jboss -c '/opt/jboss/current/bin/run.sh > /dev/null 2> /dev/null &'
| # if the 'su -l ...' command fails (the -l flag is not recognized by my su cmd) try:
| # sudo -u jboss /opt/jboss/bin/run.sh > /dev/null 2> /dev/null &
| su -l jboss -c '/opt/jboss/current/bin/run.sh > /dev/null 2> /dev/null &'
| }
|
| stop(){
| echo "Stopping jboss.."
|
| # If using an SELinux system such as RHEL 4, use the command below
| # instead of the "su":
| # eval "runuser - jboss -c '/opt/jboss/current/bin/shutdown.sh -S &'
| # if the 'su -l ...' command fails try:
| # sudo -u jboss /opt/jboss/bin/shutdown.sh -S &
| su -l jboss -c '/opt/jboss/current/bin/shutdown.sh -S &'
| }
|
| restart(){
| stop
| # give stuff some time to stop before we restart
| sleep 60
| # protect against any services that can't stop before we restart (warning this kills all Java instances running as 'jboss' user)
| su -l jboss -c 'killall java'
| # if the 'su -l ...' command fails try:
| # sudo -u jboss killall java
| start
| }
|
|
|
|
| case "$1" in
| start)
| start
| ;;
| stop)
| stop
| ;;
| restart)
| restart
| ;;
| *)
| echo "Usage: jboss {start|stop|restart}"
| exit 1
| esac
|
| exit 0
Thanks so much for your help!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257966#4257966
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257966
14 years, 7 months
[Installation, Configuration & Deployment] - Re: JBOSS runs as a service, but will not autostart
by PeterJ
Yes, I understand all that, but "weird" things happen when services start automatically at startup. What I am suspecting is that the OS does attempt to start the service, but it is crashing for some reason. I imagine there is an OS log file somewhere that might give some clues on the issue, but I would not know offhand. And even if I knew where that log was on Ubuntu , such knowledge might not help you on CentOS. So the best alternative is to have the script "echo" so info.
If you are using one of the jboss_init_*.sh scripts, then you will see this:
| JBOSS_CONSOLE=${JBOSS_CONSOLE:-"/dev/null"}
| . . .
| eval $JBOSS_CMD_START >${JBOSS_CONSOLE} 2>&1 &
in which case all you have to do is change the /dev/null to something a little more permanent ;-) Or set JBOSS_CONSOLE earlier script - there are some 'if' statements earlier in the script that ensure the files is accessible, so set it before those statements. And of course test manually first.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257964#4257964
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257964
14 years, 7 months