Delivery Status Notification (Failure)
by postmaster@lists.jboss.org
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
avlyachekdd@localhost
17 years, 8 months
[JBoss jBPM] - Is there any way to turn off logging completely? (3.2 GA)
by joe_jboss@freemansoft.com
We have an application that runs jboss BPM without ever persisting the process states to a database. We recently realized that our VM sizes were increasing because of the logging records that are kept in transientinstances in our process instances. The online manual says you can turn off logging by removing the logging line copying the jbpm-context section from default.jboss.cfg.xml to jboss.cfg.xml and by removing the line that includes service name='logging' I'm not sure what that really does. It turns out that this does not actually terminate the logging. Logging Instances are still created and filled with data.
ProcessInstance constructor calls Token.addLog(ProcessLog)
Token.addLog(ProcessLog) calls processInstance.getInstance(LoggingInstance.class)
processInstance.getInstance() always creates a LoggingInstance as a fallback and attaches it to the token
This means that there is always a LoggingInstance() tied to the token so logging always gets captured and hangs around. I don't see any way to not end up with a LoggingInstance.
I couldn't find anywhere that the services as named in jbpm.cfg.xml were looked up and used in our application.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171933#4171933
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171933
17 years, 8 months
[JBoss Tools (users)] - Validate (Eclipse Seam Validator) problem
by Kragoth
I've noticed a small problem with the Seam Validator in the jboss Tools plugin.
The problem occurs if you have an attribute on a class where the second letter of the attribute is a capital letter.
eg.
| private GekkoMoney aRP;
|
Now according to java standards the getter for this property would be.
| public GekkoMoney getARP() {
| return aRP;
| }
|
Thus you would expect to reference the property in your xhtml EL expressions like this.
| #{item.debitControlChange.ARP}
|
The above el expression works but, the Seam Validator gives me this error when validating the expressions on the page.
"ARP" cannot be resolved.
It would seem that the EL resovler used when the page is running in the web app looks for the method getARP() which it finds. But the seam validator is looking for the property ARP which of course it doesn't find.
Shouldn't the validation use the same technique to test if an EL expression is valid or not? It is rather annoying for the validation to say the expression is wrong when it is not wrong.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171932#4171932
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171932
17 years, 8 months
[Installation, Configuration & DEPLOYMENT] - JBoss AS 4.2.3 start as service question
by wslyhbb
I have JBoss AS 4.2.3, if I start it as a service at boot, JBoss starts but Tomcat does not. However, I can start it manually by running run.sh and it all works correctly. What I mean is, if I boot the computer, then I can go to http://localhost:8080 and the JBoss page is displayed. If I click on any of the JBoss Management links (Tomcat, JMX Console, or JBoss Web Console) I get an "Unable to connect" error.
Please help.
Here is my /etc/rc.d/init.d/jboss:
#! /bin/sh
JBOSS_LOG_FILE=/var/log/jboss
JBOSS_HOME=${JBOSS_HOME:-"/usr/local/jboss-4.2.3.GA"}
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 '$JBOSS_HOME/bin/run.sh 2>&1 $JBOSS_LOG_FILE &'
}
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 '$JBOSS_HOME/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
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171922#4171922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171922
17 years, 8 months