date:20120214

[jira] [Updated] (GERONIMO-6273) Remote EJB-JNDI lookup fails

2012-02-14 Thread Daniel Cavalcanti (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cavalcanti updated GERONIMO-6273:


Attachment: multiple-ejbs.zip

Sample maven project that demonstrates the problem.

> Remote EJB-JNDI lookup fails
> 
>
> Key: GERONIMO-6273
> URL: https://issues.apache.org/jira/browse/GERONIMO-6273
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.2.1
> Environment: Windows 7
>Reporter: Daniel Cavalcanti
>Priority: Critical
> Attachments: multiple-ejbs.zip
>
>
> I have created a simple project that defines a Remote Stateless EJB:
> @Remote
> public interface BeanService {
> public String hello(String name);
> }
> @Stateless
> public class BeanImpl implements BeanService {
> @Resource(name="who")
> private String who;
> public String hello(String name) {
> return MessageFormat.format("Hello {0} from {1}.", name, who);
> }
> }
> I also created the deployment descriptor and plan files:
> ejb-jar.xml:
> 
>  version="3.0" 
> xmlns="http://java.sun.com/xml/ns/javaee"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xsi:schemaLocation="
> http://java.sun.com/xml/ns/javaee 
> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd";>
> 
> 
> 
> 
> BeanImplA
> BeanImplA
> sample.BeanService
> sample.BeanImpl
> 
> who
> java.lang.String
> BeanImplA
> 
> 
> 
> 
> BeanImplB
> BeanImplBB
> sample.BeanService
> sample.BeanImpl
> 
> who
> java.lang.String
> BeanImplBB
> 
> 
> 
> 
> 
> 
> openejb-jar.xml:
> 
>  xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2";
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2";
> xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2";
> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
> http://openejb.apache.org/xml/ns/openejb-jar-2.2 
> http://geronimo.apache.org/schemas-2.2/openejb-jar-2.2.xsd";>
> 
> 
> sample
> multiple-ejbs
> 1.0.0
> jar
> 
> 
> 
> 
> 
> MyBeanA
> MyBeanA
> 
> 
> MyBeanB
> MyBeanBB
> 
> 
> 
> And a simple web service class to test the deployed EJB:
> @WebService(
> name="SampleWS",
> portName="SampleWS",
> serviceName="SampleWS")
> @Stateless()
> public class SampleWS {
> 
> private InitialContext ic;
> 
> @PostConstruct
> protected void postConstruct() {
> try {
> ic = new InitialContext();
> } catch (NamingException ex) {
> ex.printStackTrace();
> }
> }
> 
> @WebMethod
> public void lookup(@WebParam String name) {
> try {
> System.out.println("Looking up " + name);
> BeanService bean = (BeanService) ic.lookup(name);
> System.out.println(bean.hello(name));
> } catch (Exception ex) {
> System.err.println("Error: " + ex.getMessage());
> }
> }
> 
> }
> I start geronimo with debug level logging and deploy the application:
> 2012-02-14 18:12:39,855 INFO  [startup] Undeploying app: 
> C:\Users\204071044\AppData\Local\Temp\geronimo-deployer983143051956019168.tmpdir\multiple-ejbs-1.0.0.jar
> 2012-02-14 18:12:39,903 INFO  [DirectoryMonitor] Hot deployer notified that 
> an artifact was removed: sample/multiple-ejbs/1.0.0/jar
> 2012-02-14 18:12:40,683 INFO  [config] Configuring 
> Service(id=DefaultStatelessContainer, type=Container, provider-id=Default 
> Stateless Container)
> 2012-02-14 18:12:40,683 INFO  [config] Configuring 
> Service(id=DefaultStatefulContainer, type=Container, provider-id=Default 
> Stateful Container)
> 2012-02-14 18:12:40,683 INFO  [config] Configuring 
> Service(id=DefaultSingletonContainer, type=Container, provider-id=Default 
> Singleton Container)
> 2012-02-14 18:12:40,683 INFO  [config] Configuring 
> Service(id=DefaultBMPContainer, type=Container, provider-id=Default BMP 
> Container)
> 2012-02-14 18:12:40,683 INFO  [config] Configuring 
> Service(id=DefaultCMPContainer, type=Container, provider-id=Default CMP 
> Container)
> 2012-02-14 18:12:40,683 INFO  [config] Configuring enterprise application: 
> sample/multiple-ejbs/1.0.0/jar
> 2012-02-14 18:12:40,761

[jira] [Created] (GERONIMO-6273) Remote EJB-JNDI lookup fails

2012-02-14 Thread Daniel Cavalcanti (Created) (JIRA)

Remote EJB-JNDI lookup fails


 Key: GERONIMO-6273
 URL: https://issues.apache.org/jira/browse/GERONIMO-6273
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: OpenEJB
Affects Versions: 2.2.1
 Environment: Windows 7
Reporter: Daniel Cavalcanti
Priority: Critical
 Attachments: multiple-ejbs.zip


I have created a simple project that defines a Remote Stateless EJB:

@Remote
public interface BeanService {
public String hello(String name);
}


@Stateless
public class BeanImpl implements BeanService {
@Resource(name="who")
private String who;
public String hello(String name) {
return MessageFormat.format("Hello {0} from {1}.", name, who);
}
}

I also created the deployment descriptor and plan files:

ejb-jar.xml:


http://java.sun.com/xml/ns/javaee"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="
http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd";>




BeanImplA
BeanImplA
sample.BeanService
sample.BeanImpl

who
java.lang.String
BeanImplA




BeanImplB
BeanImplBB
sample.BeanService
sample.BeanImpl

who
java.lang.String
BeanImplBB







openejb-jar.xml:


http://openejb.apache.org/xml/ns/openejb-jar-2.2";
xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2";
xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2";
xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://openejb.apache.org/xml/ns/openejb-jar-2.2 
http://geronimo.apache.org/schemas-2.2/openejb-jar-2.2.xsd";>




sample
multiple-ejbs
1.0.0
jar






MyBeanA
MyBeanA


MyBeanB
MyBeanBB





And a simple web service class to test the deployed EJB:


@WebService(
name="SampleWS",
portName="SampleWS",
serviceName="SampleWS")
@Stateless()
public class SampleWS {

private InitialContext ic;

@PostConstruct
protected void postConstruct() {
try {
ic = new InitialContext();
} catch (NamingException ex) {
ex.printStackTrace();
}
}

@WebMethod
public void lookup(@WebParam String name) {
try {
System.out.println("Looking up " + name);
BeanService bean = (BeanService) ic.lookup(name);
System.out.println(bean.hello(name));
} catch (Exception ex) {
System.err.println("Error: " + ex.getMessage());
}
}

}

I start geronimo with debug level logging and deploy the application:

2012-02-14 18:12:39,855 INFO  [startup] Undeploying app: 
C:\Users\204071044\AppData\Local\Temp\geronimo-deployer983143051956019168.tmpdir\multiple-ejbs-1.0.0.jar
2012-02-14 18:12:39,903 INFO  [DirectoryMonitor] Hot deployer notified that an 
artifact was removed: sample/multiple-ejbs/1.0.0/jar
2012-02-14 18:12:40,683 INFO  [config] Configuring 
Service(id=DefaultStatelessContainer, type=Container, provider-id=Default 
Stateless Container)
2012-02-14 18:12:40,683 INFO  [config] Configuring 
Service(id=DefaultStatefulContainer, type=Container, provider-id=Default 
Stateful Container)
2012-02-14 18:12:40,683 INFO  [config] Configuring 
Service(id=DefaultSingletonContainer, type=Container, provider-id=Default 
Singleton Container)
2012-02-14 18:12:40,683 INFO  [config] Configuring 
Service(id=DefaultBMPContainer, type=Container, provider-id=Default BMP 
Container)
2012-02-14 18:12:40,683 INFO  [config] Configuring 
Service(id=DefaultCMPContainer, type=Container, provider-id=Default CMP 
Container)
2012-02-14 18:12:40,683 INFO  [config] Configuring enterprise application: 
sample/multiple-ejbs/1.0.0/jar
2012-02-14 18:12:40,761 INFO  [OpenEJB] Auto-deploying ejb BeanImplA: 
EjbDeployment(deployment-id=multiple-ejbs/BeanImplA)
2012-02-14 18:12:40,761 INFO  [OpenEJB] Auto-deploying ejb BeanImplB: 
EjbDeployment(deployment-id=multiple-ejbs/BeanImplB)
2012-02-14 18:12:40,761 INFO  [OpenEJB] Auto-deploying ejb BeanImpl: 
EjbDeployment(deployment-id=multiple-ejbs/BeanImpl)
2012-02-14 18:12:40,761 INFO  [OpenEJB] Auto-deploying ejb SampleWS: 
EjbDeployment(deployment-id=multiple-ejbs/SampleWS)
2012-02-14 18:12:40,761 INFO  [config] Enterprise application 
"sample/multiple-ejbs/1.0.0/jar" loaded.
2012-02-14 18:12:41,416 INFO  [JAXWSServiceBuilder] Configuri

[jira] [Issue Comment Edited] (GERONIMO-6270) Re-enable multiple instances support in one installation

2012-02-14 Thread Russell E Glaue (Issue Comment Edited) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207877#comment-13207877
 ] 

Russell E Glaue edited comment on GERONIMO-6270 at 2/14/12 8:52 PM:


Here is a summary of the problems I am aware of in enabling multiple instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring 
to exist, and will complain if it does not, however, the geronimo instance will 
continue to start regardless. If it cannot create the directory, Geronimo will 
show the following error when "Loading agent-car-jmx": ERROR 
[SnapshotConfigXMLBuilder] Could not make the directory 
/opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is 
specified relative to the working directory the user starts up the geronimo 
instance. Also, if ActiveMQ cannot create var/activemq Geronimo will fail to 
start with the following error when "Loading activemq-broker-blueprint": ERROR 
[BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: 
java.io.IOException: Failed to create directory 'var/activemq'
# GERONIMO_TMPDIR: GERONIMO-6174 - The start script sets the temp directory 
relative to GERONIMO_HOME, but instead should be set relative to the Geronimo 
Instance directory
# Karaf: GERONIMO-6174 - Karaf expects to use 
{karaf.home}/etc/shell.init.script each time a shell session is started, but I 
think ideally that should be {karaf.base}/etc/shell.init.script
# Repository: GERONIMO-6175 - The repository will use one in 
{org.geronimo.server.dir}/repository if configured, but some Geronimo code 
still expects a writable repository to exist at GERONIMO_HOME/repository. If it 
does not exist, Geronimo will fail to start with the following errors when 
"Loading rmi-naming": (1) WARN  [RMIRegistryService] RMI Registry failed, (2) 
ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED 
state: 
abstractName="org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car,j2eeType=GBean,name=RMIRegistry"


To see some of the complaints, the var directory must be removed from 
GERONIMO_HOME, and in its place you must create a file named var. This will 
prevent Geronimo from creating GERONIMO_HOME/var when it discovers it does not 
exist.

Here is the procedure to create two geronimo instances:
# Follow steps in 
https://cwiki.apache.org/confluence/display/GMOxDOC30/Running+multiple+Geronimo+instances
# Use the below start script
# create an empty file GERONIMO_HOME/var
# To expose some issues, comment out the work-arounds and restart.


Here is a start script I use to workaround some, but not all, of the issues as 
we are able.

{noformat:borderStyle=solid}
#!/bin/bash
# Geronimo Named Instance start script
# instance: gserv1

# Uncomment this to explicitly set Geronimo's runtime Java
#JAVA_HOME=/usr/jdk1.6.0_25
#PATH=${JAVA_HOME}/bin:${PATH}

# Set the location of the Geronimo Installation, and Geronimo Instance
GHOME=/opt/geronimo3
GVIRT=gserv1
GSERV=${GHOME}/${GVIRT}

#
# The Next section works around some known issues
#

# GERONIMO-5987
# Must change to the server directory in order to work around ActiveMQ lock
# file conflict issue reported in GERONIMO-5987.
cd ${GSERV}

# GERONIMO-6174
# Uncomment for the Workaround of issues in GERONIMO-6174
GERONIMO_TMPDIR=${GSERV}/var/temp
GERONIMO_OPTS="${GERONIMO_OPTS} -Dkaraf.home=${GSERV}"

#
# This Section starts the Geronimo Instance
#
export GERONIMO_OPTS="${GERONIMO_OPTS} 
-Dorg.apache.geronimo.server.dir=${GSERV}"
export GERONIMO_TMPDIR
export GERONIMO_HOME=${GHOME}
export GERONIMO_SERVER=${GSERV}
#
# Uncomment for Normal startup, and comment out the "Interactive startup"
#${GHOME}/bin/startup
#
# Interactive startup
${GHOME}/bin/geronimo run
{noformat}



  was (Author: rglaue):
Here is a summary of the problems I am aware of in enabling multiple 
instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring 
to exist, and will complain if it does not, however, the geronimo instance will 
continue to start regardless. If it cannot create the directory, Geronimo will 
show the following error when "Loading agent-car-jmx": ERROR 
[SnapshotConfigXMLBuilder] Could not make the directory 
/opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is 
specified relative to the working directory the user starts up the geronimo 
instance. Also, if ActiveMQ cannot create var/activemq Geronimo will fail to 
start with the following error when "Loading activemq-broker-blueprint": ERROR 
[BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: 
java.io.IOException: Failed to create directory 'va

[jira] [Issue Comment Edited] (GERONIMO-6270) Re-enable multiple instances support in one installation

2012-02-14 Thread Russell E Glaue (Issue Comment Edited) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207877#comment-13207877
 ] 

Russell E Glaue edited comment on GERONIMO-6270 at 2/14/12 6:10 PM:


Here is a summary of the problems I am aware of in enabling multiple instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring 
to exist, and will complain if it does not, however, the geronimo instance will 
continue to start regardless. If it cannot create the directory, Geronimo will 
show the following error when "Loading agent-car-jmx": ERROR 
[SnapshotConfigXMLBuilder] Could not make the directory 
/opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is 
specified relative to the working directory the user starts up the geronimo 
instance. Also, if ActiveMQ cannot create var/activemq Geronimo will fail to 
start with the following error when "Loading activemq-broker-blueprint": ERROR 
[BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: 
java.io.IOException: Failed to create directory 'var/activemq'
# GERONIMO_TMPDIR: GERONIMO-5987 (reported in comment) - The start script sets 
the temp directory relative to GERONIMO_HOME, but instead should be set 
relative to the Geronimo Instance directory
# Karaf: GERONIMO-6174 - Karaf expects to use 
{karaf.home}/etc/shell.init.script each time a shell session is started, but I 
think ideally that should be {karaf.base}/etc/shell.init.script
# Repository: GERONIMO-6175 - The repository will use one in 
{org.geronimo.server.dir}/repository if configured, but some Geronimo code 
still expects a writable repository to exist at GERONIMO_HOME/repository. If it 
does not exist, Geronimo will fail to start with the following errors when 
"Loading rmi-naming": (1) WARN  [RMIRegistryService] RMI Registry failed, (2) 
ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED 
state: 
abstractName="org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car,j2eeType=GBean,name=RMIRegistry"


To see some of the complaints, the var directory must be removed from 
GERONIMO_HOME, and in its place you must create a file named var. This will 
prevent Geronimo from creating GERONIMO_HOME/var when it discovers it does not 
exist.

Here is the procedure to create two geronimo instances:
# Follow steps in 
https://cwiki.apache.org/confluence/display/GMOxDOC30/Running+multiple+Geronimo+instances
# Use the below start script
# create an empty file GERONIMO_HOME/var
# To expose some issues, comment out the work-arounds and restart.


Here is a start script I use to workaround some, but not all, of the issues as 
we are able.

{noformat:borderStyle=solid}
#!/bin/bash
# Geronimo Named Instance start script
# instance: gserv1

# Uncomment this to explicitly set Geronimo's runtime Java
#JAVA_HOME=/usr/jdk1.6.0_25
#PATH=${JAVA_HOME}/bin:${PATH}

# Set the location of the Geronimo Installation, and Geronimo Instance
GHOME=/opt/geronimo3
GVIRT=gserv1
GSERV=${GHOME}/${GVIRT}

#
# The Next section works around some known issues
#

# GERONIMO-5987
# Must change to the server directory in order to work around ActiveMQ lock
# file conflict issue reported in GERONIMO-5987.
cd ${GSERV}

# GERONIMO-6174
# Uncomment for the Workaround of issues in GERONIMO-6174
GERONIMO_TMPDIR=${GSERV}/var/temp
GERONIMO_OPTS="${GERONIMO_OPTS} -Dkaraf.home=${GSERV}"

#
# This Section starts the Geronimo Instance
#
export GERONIMO_OPTS="${GERONIMO_OPTS} 
-Dorg.apache.geronimo.server.dir=${GSERV}"
export GERONIMO_TMPDIR
export GERONIMO_HOME=${GHOME}
export GERONIMO_SERVER=${GSERV}
#
# Uncomment for Normal startup, and comment out the "Interactive startup"
#${GHOME}/bin/startup
#
# Interactive startup
${GHOME}/bin/geronimo run
{noformat}



  was (Author: rglaue):
Here is a summary of the problems I am aware of in enabling multiple 
instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring 
to exist, and will complain if it does not, however, the geronimo instance will 
continue to start regardless. If it cannot create the directory, Geronimo will 
fail to start with the following error when "Loading agent-car-jmx": ERROR 
[SnapshotConfigXMLBuilder] Could not make the directory 
/opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is 
specified relative to the working directory the user starts up the geronimo 
instance. Also, if ActiveMQ cannot create var/activemq Geronimo will fail to 
start with the following error when "Loading activemq-broker-blueprint": ERROR 
[BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: 
java.io.IOExcep

[jira] [Commented] (GERONIMO-6270) Re-enable multiple instances support in one installation

2012-02-14 Thread Russell E Glaue (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207877#comment-13207877
 ] 

Russell E Glaue commented on GERONIMO-6270:
---

Here is a summary of the problems I am aware of in enabling multiple instances:

# SnapshotConfigXMLBuilder: (not reported) - Wants GERONIMO_HOME/var/monitoring 
to exist, and will complain if it does not, however, the geronimo instance will 
continue to start regardless. If it cannot create the directory, Geronimo will 
fail to start with the following error when "Loading agent-car-jmx": ERROR 
[SnapshotConfigXMLBuilder] Could not make the directory 
/opt/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-20111220/var/monitoring/
# ActiveMQ: GERONIMO-5987 (reported in comment) - ActiveMQ lock directory is 
specified relative to the working directory the user starts up the geronimo 
instance. Also, if ActiveMQ cannot create var/activemq Geronimo will fail to 
start with the following error when "Loading activemq-broker-blueprint": ERROR 
[BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: 
java.io.IOException: Failed to create directory 'var/activemq'
# GERONIMO_TMPDIR: GERONIMO-5987 (reported in comment) - The start script sets 
the temp directory relative to GERONIMO_HOME, but instead should be set 
relative to the Geronimo Instance directory
# Karaf: GERONIMO-6174 - Karaf expects to use 
{karaf.home}/etc/shell.init.script each time a shell session is started, but I 
think ideally that should be {karaf.base}/etc/shell.init.script
# Repository: GERONIMO-6175 - The repository will use one in 
{org.geronimo.server.dir}/repository if configured, but some Geronimo code 
still expects a writable repository to exist at GERONIMO_HOME/repository. If it 
does not exist, Geronimo will fail to start with the following errors when 
"Loading rmi-naming": (1) WARN  [RMIRegistryService] RMI Registry failed, (2) 
ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED 
state: 
abstractName="org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/3.0-beta-1/car,j2eeType=GBean,name=RMIRegistry"


To see some of the complaints, the var directory must be removed from 
GERONIMO_HOME, and in its place you must create a file named var. This will 
prevent Geronimo from creating GERONIMO_HOME/var when it discovers it does not 
exist.

Here is the procedure to create two geronimo instances:
# Follow steps in 
https://cwiki.apache.org/confluence/display/GMOxDOC30/Running+multiple+Geronimo+instances
# Use the below start script
# create an empty file GERONIMO_HOME/var
# To expose some issues, comment out the work-arounds and restart.


Here is a start script I use to workaround some, but not all, of the issues as 
we are able.

{noformat:borderStyle=solid}
#!/bin/bash
# Geronimo Named Instance start script
# instance: gserv1

# Uncomment this to explicitly set Geronimo's runtime Java
#JAVA_HOME=/usr/jdk1.6.0_25
#PATH=${JAVA_HOME}/bin:${PATH}

# Set the location of the Geronimo Installation, and Geronimo Instance
GHOME=/opt/geronimo3
GVIRT=gserv1
GSERV=${GHOME}/${GVIRT}

#
# The Next section works around some known issues
#

# GERONIMO-5987
# Must change to the server directory in order to work around ActiveMQ lock
# file conflict issue reported in GERONIMO-5987.
cd ${GSERV}

# GERONIMO-6174
# Uncomment for the Workaround of issues in GERONIMO-6174
GERONIMO_TMPDIR=${GSERV}/var/temp
GERONIMO_OPTS="${GERONIMO_OPTS} -Dkaraf.home=${GSERV}"

#
# This Section starts the Geronimo Instance
#
export GERONIMO_OPTS="${GERONIMO_OPTS} 
-Dorg.apache.geronimo.server.dir=${GSERV}"
export GERONIMO_TMPDIR
export GERONIMO_HOME=${GHOME}
export GERONIMO_SERVER=${GSERV}
#
# Uncomment for Normal startup, and comment out the "Interactive startup"
#${GHOME}/bin/startup
#
# Interactive startup
${GHOME}/bin/geronimo run
{noformat}



> Re-enable multiple instances support in one installation
> 
>
> Key: GERONIMO-6270
> URL: https://issues.apache.org/jira/browse/GERONIMO-6270
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 3.0-beta-1
>Reporter: Forrest Xia
>Assignee: Yi Xiao
>
> We need to investigate how to re-enable the multiple instances support in one 
> installation.
> Refer to 
> https://issues.apache.org/jira/browse/GERONIMO-6175
> https://issues.apache.org/jira/browse/GERONIMO-6174
> https://issues.apache.org/jira/browse/GERONIMO-5987

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

2012-02-14 Thread Forrest Xia (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207586#comment-13207586
 ] 

Forrest Xia commented on GERONIMO-6162:
---

Sorry, not noticed the comment tab.

Anyway, any reason to disable it? do you know that? if possible, can you help 
re-enable it in the code?

> Enable Datasource Connection Pool Parameters Setting
> 
>
> Key: GERONIMO-6162
> URL: https://issues.apache.org/jira/browse/GERONIMO-6162
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector, console
>Affects Versions: 3.0
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 3.0.1
>
>
> Currently we can't set Datasource Connection Pool Parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMO-6256) SortUtils does not behavior correctly while both after/before others and before/after are configured

2012-02-14 Thread Ivan (Resolved) (JIRA)


 [ 
https://issues.apache.org/jira/browse/GERONIMO-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan resolved GERONIMO-6256.


Resolution: Invalid

I made a mistaken, seems that the codes work well on this scenario.

> SortUtils does not behavior correctly while both after/before others and 
> before/after are configured
> 
>
> Key: GERONIMO-6256
> URL: https://issues.apache.org/jira/browse/GERONIMO-6256
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: web
>Affects Versions: 3.0-beta-1
>Reporter: Ivan
>Assignee: Ivan
> Fix For: 3.0, 3.0-beta-2
>
>
> SortUtils does not behavior correctly while both after/before others and 
> before/after are configured

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

2012-02-14 Thread viola.lu (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207594#comment-13207594
 ] 

viola.lu commented on GERONIMO-6162:


Have no idea its history, but enablement of this code will be a long story.

> Enable Datasource Connection Pool Parameters Setting
> 
>
> Key: GERONIMO-6162
> URL: https://issues.apache.org/jira/browse/GERONIMO-6162
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector, console
>Affects Versions: 3.0
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 3.0.1
>
>
> Currently we can't set Datasource Connection Pool Parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

2012-02-14 Thread Forrest Xia (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMO-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207584#comment-13207584
 ] 

Forrest Xia commented on GERONIMO-6162:
---

Any more specific information about this jira? please document it here clearly. 
thanks!

> Enable Datasource Connection Pool Parameters Setting
> 
>
> Key: GERONIMO-6162
> URL: https://issues.apache.org/jira/browse/GERONIMO-6162
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: connector, console
>Affects Versions: 3.0
>Reporter: viola.lu
>Assignee: viola.lu
>Priority: Minor
> Fix For: 3.0.1
>
>
> Currently we can't set Datasource Connection Pool Parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-6273) Remote EJB-JNDI lookup fails

[jira] [Created] (GERONIMO-6273) Remote EJB-JNDI lookup fails

[jira] [Issue Comment Edited] (GERONIMO-6270) Re-enable multiple instances support in one installation

[jira] [Issue Comment Edited] (GERONIMO-6270) Re-enable multiple instances support in one installation

[jira] [Commented] (GERONIMO-6270) Re-enable multiple instances support in one installation

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

[jira] [Resolved] (GERONIMO-6256) SortUtils does not behavior correctly while both after/before others and before/after are configured

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

[jira] [Commented] (GERONIMO-6162) Enable Datasource Connection Pool Parameters Setting

9 matches

Site Navigation

Mail list logo

Footer information