July 2008 - jboss-user - Jboss List Archives

[JBoss Cache: Core Edition] - Re: How to evict know out of date objects (after SQL stateme

by bstansberry＠jboss.com

Yes, they are, and if you use them Hibernate will invalidate the relevant regions of the 2nd level cache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165392#4165392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165392

17 years, 9 months

1
0
0 / 0

[JBoss Portal] - Re: Url : how to define MyPortal as the default portal.

by thomas.heute＠jboss.com

On the admin GUI, just click on "Make default". In the XML i don't remember the syntax by heart, but that shouldn't be hard to find. (The Jira is closed as resolved, no need to vote for it) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165391#4165391 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165391

17 years, 9 months

1
0
0 / 0

[JBoss Portal] - Re: Url : how to define MyPortal as the default portal.

by Antoine_h

The JMX service description is : <mbean | code="org.jboss.portal.core.model.portal.DefaultPortalCommandFactory" | name="portal:commandFactory=DefaultPortal" | xmbean-dd="" | xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> | <xmbean/> | <depends | optional-attribute-name="NextFactory" | proxy-type="attribute">portal:commandFactory=Delegating</depends> | <depends | optional-attribute-name="Container" | proxy-type="attribute">portal:container=PortalObject</depends> | </mbean> | it is in : deploy\jboss-portal.sar\META-INF\jboss-service.xml you have to replace the JMX service, by one of your own, with the class overriden for your need. look at the Jira for an example of the code : http://jira.jboss.com/jira/browse/JBPORTAL-1324 and, please, vote for the jira task... so it shows that some people wish to have this feature in the future version.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165390#4165390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165390

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: MDB in seperate ejb-jar causes problem during deployment

by vdweij

That's exactly the issue... thanks for pointing that out. I'll try a higher JBoss version! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165389#4165389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165389

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Using quartz from EJB 3.0

by wolfc

There are two ways to use Quartz from EJB3: 1. the unsupported EJB3 Quartz timer service: https://jira.jboss.org/jira/browse/EJBTHREE-619 2. or the Quartz resource adapter: http://wiki.jboss.org/auth/wiki/QuartzSchedulerIntegration View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165383#4165383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165383

17 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Error in shutdown using jboss_init_redhat.sh

by PeterJ

Based on the posting timestamps, I'll assume you wrote your post before you saw my last post. Are you still trying to stop the out-of-memory app server, or are you asking about how to stop the app server in general? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165382#4165382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165382

17 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Error in shutdown using jboss_init_redhat.sh

by thalupula

Hi, Please find my jboss_init_redhat.sh file. Correct me if i'm wrong. Regards, Ravi Thalupula #!/bin/sh # # $Id: jboss_init_redhat.sh 60992 2007-02-28 11:33:27Z dimitris(a)jboss.org $ # # JBoss Control Script # # To use this script run it as root - it will switch to the specified user # # Here is a little (and extremely primitive) startup/shutdown script # for RedHat systems. It assumes that JBoss lives in /usr/local/jboss, # it's run by user 'jboss' and JDK binaries are in /usr/local/jdk/bin. # All this can be changed in the script itself. # # Either modify this script for your requirements or just ensure that # the following variables are set correctly before calling the script. #define where jboss is - this is the directory containing directories log, bin, conf etc JBOSS_HOME=${JBOSS_HOME:-"/opt/jboss-4.2.2.GA"} #define the user under which jboss will run, or use 'RUNASIS' to run as the current user JBOSS_USER=${JBOSS_USER:-"jboss"} #make sure java is in your path JAVAPTH=${JAVAPTH:-"/usr/java/jdk1.5.0_16"} #configuration to use, usually one of 'minimal', 'default', 'all' JBOSS_CONF=${JBOSS_CONF:-"default"} #define JBOSS_HOST JBOSS_HOST=${JBOSS_HOST:-"0.0.0.0"} #if JBOSS_HOST specified, use -b to bind jboss services to that address JBOSS_BIND_ADDR=${JBOSS_HOST:+"-b $JBOSS_HOST"} #define the classpath for the shutdown class JBOSSCP=${JBOSSCP:-"$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jnet.jar"} #define the script to use to start jboss JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF $JBOSS_BIND_ADDR"} if [ "$JBOSS_USER" = "RUNASIS" ]; then SUBIT="" else SUBIT="su - $JBOSS_USER -c " fi if [ -n "$JBOSS_CONSOLE" -a ! -d "$JBOSS_CONSOLE" ]; then # ensure the file exists touch $JBOSS_CONSOLE if [ ! -z "$SUBIT" ]; then chown $JBOSS_USER $JBOSS_CONSOLE fi fi if [ -n "$JBOSS_CONSOLE" -a ! -f "$JBOSS_CONSOLE" ]; then echo "WARNING: location for saving console log invalid: $JBOSS_CONSOLE" echo "WARNING: ignoring it and using /dev/null" JBOSS_CONSOLE="/dev/null" fi #define what will be done with the console log JBOSS_CONSOLE=${JBOSS_CONSOLE:-"/dev/null"} JBOSS_CMD_START="cd $JBOSS_HOME/bin; $JBOSSSH" JBOSS_CMD_STOP=${JBOSS_CMD_STOP:-"java -classpath $JBOSSCP org.jboss.Shutdown --shutdown"} if [ -z "`echo $PATH | grep $JAVAPTH`" ]; then export PATH=$PATH:$JAVAPTH fi if [ ! -d "$JBOSS_HOME" ]; then echo JBOSS_HOME does not exist as a valid directory : $JBOSS_HOME exit 1 fi echo JBOSS_CMD_START = $JBOSS_CMD_START case "$1" in start) cd $JBOSS_HOME/bin if [ -z "$SUBIT" ]; then eval $JBOSS_CMD_START >${JBOSS_CONSOLE} 2>&1 & else $SUBIT "$JBOSS_CMD_START >${JBOSS_CONSOLE} 2>&1 &" fi ;; stop) if [ -z "$SUBIT" ]; then $JBOSS_CMD_STOP else $SUBIT "$JBOSS_CMD_STOP" fi ;; restart) $0 stop $0 start ;; *) echo "usage: $0 (start|stop|restart|help)" esac View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165381#4165381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165381

17 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Error in shutdown using jboss_init_redhat.sh

by PeterJ

OK, so you want to shut down a local app server not a remote app server. "local" and "remote" does not refer to your physical location, but rather where the command line is being executed. Since you connected to the server using putty, any commands entered in are local. In that case you can use either the command you posted or the command I posted (use localhost for hostname) to shut down the app server. This assumes that the app server is using port 1099 for JNDI. Or are you still trying to shut down the hung app server that got an out-of-memory error? As Dimitri pointed out, if the app server ran out of memory, you will not be able to shut down the app server this way. You will have to kill it. To kill it, you will first have to find its process id: ps -ef | grep java Scan through the results of that command, looking for a java process that uses org.jboss.Main as its class. Use the kill command to end it: kill -9 xxx where xxx is the process id of the java process. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165379#4165379 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165379

17 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - jbossmq hung messages

by vadimos

We have noticed that under a load some messages are left sitting in the queue's persistent store. They don't get processed nor moved to DLQ. There is also no visible exception in our app or jboss (with tracing enabled). However, the messages do get successfully processed on jms restart. We are using jboss 4.0.4 with jbossmq, durable messages with mysql support. We have also installed the following patches but the issue is still there: https://jira.jboss.org/jira/browse/JBAS-3573 https://jira.jboss.org/jira/browse/JBAS-4090 thanks, vadim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165378#4165378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165378

17 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Using quartz from EJB 3.0

by jaikiran

Well, i actually thought that you had managed to bind Quartz scheduler to JNDI and that's why i suggested the @Resource approach. But based on your recent reply, it looks like that you are trying to find a way to use the quartz scheduler in your EJB3. So, is there any specific reason for injecting (or even try to lookup) the scheduler from JNDI? Why not just use the Quartz scheduler APIs to trigger the jobs? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165377#4165377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165377

17 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2008