[Design of JBoss Build System] - Re: Getting the release process working with javaee
by pgier
"scott.stark(a)jboss.org" wrote : "wolfc" wrote : I modeled the versions in the javaee subprojects to be the same as the spec version. So we should never bump these. Maybe we need a build number in there as well, like in RPMs (jboss-javaee-5.0-1)?
| Yes, that sounds like a good approach. So while the aggregate may be at Beta3, the subprojects are at the spec version with a build number qualifier. A version like 5.0-a does not match the osgi version conventions we outlined though. It would need to be something like 5.0.0.X-buildnumber as the qualifer portion is free-form and should not impact compatibility comparisons.
|
Instead of a build number (1, 2, 3, etc..) would it make sense to just append the aggregate release number? So for example jboss-ejb-api 3.0.0.X-5.0.0.Beta3?
We should be able to do something like this in each of the modules.
| <version>3.0.0.X-${project.parent.version}</version>
|
This way we wouldn't have to worry about continually updating the build number.
Or we could just keep the build number as a property in the aggregate. So the modules would have:
| <version>3.0.0.X-${buildNumber}</version>
|
And ${buildNumber} would be a property set in the parent pom.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082652#4082652
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082652
17 years, 1 month
[Design of JBoss ESB] - Re: Failover MessageRedelivery
by mark.little＠jboss.com
"beve" wrote : anonymous wrote : Why don't you use transacted JMS sessions
| Well, we also have the use case when it does not make sense to redeliver the message, like when a transformation or validation fails. The redelivery service can be configured with a retry count which we could then take advantage of. This is not an optimal solution as we will still be trying to redeliver/re-execute a message that we know will fail.
|
OK. I'm not sure if that feature request will get into the 4.2.1 release though.
anonymous wrote :
| While we are on the subject of transacted JMS Sessions, we are using the JMSGatewayListener and as far as I can see these JMSSessions are created without transactions and AUTO_ACKNOWLEDGE. But there is a JIRA (http://jira.jboss.com/jira/browse/JBESB-439), which I'm sure you know:)
| Lets say we make this configurable so that the JMSGatewayListener's sessions are transacted, and also make the ack mode be configurable.
| How do we commit the transaction upon sucessfully completing the action pipeline?
|
Yes, this is all related to the recent re-assignment ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082621#4082621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082621
17 years, 1 month
[Design of JBoss ESB] - Re: Failover MessageRedelivery
by beve
Ok, now I get it. The current redelivery service deals with redelivery between ESB calls.
Our concern is scheduling redelivery/re-executing of a service upon an error in the action pipleline. An example of this would be a call to a web service that is temporarily unavailable.
Our current solution is to save the incoming Message object to the MessageStore, as the first action in the action pipeline. Upon sucessful completion of the pipeline the message will be removed.
If an exception occurs in the pipeline an exception handler will retrieve the message from the message store, re-add the retrieved message, with a different classification, to the MessageStore. The classification will match the classification that the redelivery service is configured to look for.
To get this to work I need to make a few minor changes.
I added a method to RedeliverStore that takes a classification as a parameter:
| public interface RedeliverStore extends MessageStore {
| ...
| public boolean redeliver(URI uid,String classification) throws MessageStoreException;
|
I'd also like to make the classification on RedeliverEventMessageComposer a configuratble property which would save us from having to create our own composer.
Does this look alright? Does anyone have a better way on doing this?
We do plan to build an error handling process that will take care of automatic redelivery and where we will also be able to manually trigger redelivery from tasks in jbpm, but our time schedule will not allow this at the moment. This is really just an effort to get automatic redelivery to work with the least amout of effort and buy us some time.
Thanks,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082498#4082498
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082498
17 years, 1 month
[Design of the JBoss EJB Container] - shutdown.sh
by suneelchetty
I have developed an application and in that when we are trying to shutdown the jbosss using "./shutdown.sh -S" is working fine in NT and it is giving and error in Unix and Solaris as
log4j: ERROR Failed to create directory structure: /log
log4j: ERROR setFile(null, false) call failed.
I don't know why? Could any one help me in this regard.
this is wht my shutdown.sh contains
. \dnbusr1\im01/jboss/jboss/bin/setenv.sh
#!/bin/sh
### ====================================================================== ###
## ##
## JBoss Shutdown Script ##
## ##
### ====================================================================== ###
### $Id: shutdown.sh,v 1.6.2.1 2003/12/03 16:31:08 pilhuhn Exp $ ###
DIRNAME=`dirname $0`
PROGNAME=`basename $0`
GREP="grep"
#
# Helper to complain.
#
die() {
echo "${PROGNAME}: $*"
exit 1
}
# Read an optional running configuration file
if [ "x$RUN_CONF" = "x" ]; then
RUN_CONF="$DIRNAME/run.conf"
fi
if [ -r $RUN_CONF ]; then
. $RUN_CONF
fi
# OS specific support (must be 'true' or 'false').
cygwin=false;
case "`uname`" in
CYGWIN*)
cygwin=true
;;
esac
# For Cygwin, ensure paths are in UNIX format before anything is touched
if $cygwin ; then
[ -n "$JBOSS_HOME" ] &&
JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
[ -n "$JAVA_HOME" ] &&
JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
fi
# Setup JBOSS_HOME
if [ "x$JBOSS_HOME" = "x" ]; then
JBOSS_HOME=`cd $DIRNAME/..; pwd`
fi
export JBOSS_HOME
# Setup the JVM
if [ "x$JAVA_HOME" != "x" ]; then
JAVA=$JAVA_HOME/bin/java
else
JAVA="java"
fi
# Setup the classpath
JBOSS_BOOT_CLASSPATH="$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jnet.jar"
if [ "x$JBOSS_CLASSPATH" = "x" ]; then
JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH"
else
JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH"
fi
# For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
fi
# Execute the JVM
exec $JAVA \
$JAVA_OPTS \
-classpath $JBOSS_CLASSPATH \
org.jboss.Shutdown "$@"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082482#4082482
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082482
17 years, 1 month
[Design of JBoss Build System] - Guidance on svn:ignore required
by anil.saldhana＠jboss.com
https://svn.jboss.org/repos/jbossas/projects/security/security-jboss-sx/t...
I have a test case that uses Sun's open source OpenDS, ldap server. This creates some files like locks, logs etc, as shown below:
| asaldhana~/security/security-jboss-sx/trunk>svn stat
| ? src\tests\resources\opends\logs\access
| ? src\tests\resources\opends\logs\replication
| ? src\tests\resources\opends\logs\errors
| ? src\tests\resources\opends\config\archived-configs\config-20070910013727Z
| .gz
| ? src\tests\resources\opends\db\je.info.0
| ? src\tests\resources\opends\db\je.lck
| ? src\tests\resources\opends\db\00000000.jdb
| ? src\tests\resources\opends\locks\backend-backup.lock
| ? src\tests\resources\opends\locks\backend-tasks.lock
| ? src\tests\resources\opends\locks\backend-monitor.lock
| ? src\tests\resources\opends\locks\backend-schema.lock
| ? src\tests\resources\opends\locks\server.lock
| ? src\tests\resources\opends\locks\backend-userRoot.lock
|
OpenDS is not very flexible yet with directories to use etc.
I tried to create svn:ignores for these by my usual method as shown:
| /opends/logs>svn propset svn:ignore -F replication .
| /opends/logs>svn propset svn:ignore -F errors .
| etc
|
That command has not been working here.
Any guidance?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082444#4082444
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082444
17 years, 1 month