Hi Asankha,
I think that is the problem I can't anything in my wso2-esb.log about JMX
Service URL.
Here is my configuration of the wrapper.conf:
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# set the working directory to the ESB_HOME
wrapper.working.dir=../..
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=%CLASSPATH%
wrapper.java.classpath.2=webapp/WEB-INF/lib/wrapper-3.2.3.jar
wrapper.java.classpath.3=webapp/WEB-INF/lib/patches
wrapper.java.classpath.4=webapp/WEB-INF/lib/patches/*.jar
wrapper.java.classpath.5=webapp/WEB-INF/lib
wrapper.java.classpath.6=webapp/WEB-INF/lib/synapse-*.jar
wrapper.java.classpath.7=webapp/WEB-INF/lib/*.jar
wrapper.java.classpath.8=tomcat/lib
wrapper.java.classpath.9=tomcat/lib/*.jar
wrapper.java.classpath.10=webapp/WEB-INF/classes/conf
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=webapp/WEB-INF/lib
wrapper.java.library.path.2=tomcat/lib
# Java Additional Parameters
wrapper.java.additional.1=-Dcom.sun.management.jmxremote.port=9999
wrapper.java.additional.2=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.3=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.4=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true
wrapper.java.additional.5=-Djava.endorsed.dirs=tomcat/lib/endorsed
wrapper.java.additional.6=-Desb.home=.
wrapper.java.additional.7=-Dserver-web.xml=webapp/WEB-INF/classes/conf/server-web.xml
wrapper.java.additional.8=-Dmime-mappings.xml=webapp/WEB-INF/classes/conf/mime-mappings.xml
wrapper.java.additional.9=-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XMLGrammarCachingConfiguration
wrapper.java.additional.10=-Dlog4j.configuration=file:webapp/WEB-INF/classes/conf/log4j.properties
wrapper.java.additional.11=-Desb.xml=webapp/WEB-INF/classes/conf/server.xml
wrapper.java.additional.12=-Dsynapse.xml=webapp/WEB-INF/classes/conf/synapse.xml
wrapper.java.additional.13=-Daxis2.xml=webapp/WEB-INF/classes/conf/axis2.xml
wrapper.java.additional.14=-Daxis2.repo=repository
# Initial Java Heap Size (in MB) - compute according to system
#wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB) - compute according to system
#wrapper.java.maxmemory=256
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.wso2.esb.Main
wrapper.app.parameter.2=START
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=logs/wso2-esb-process.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=5m
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=5
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=WSO2 Enterprise Service Bus (ESB)
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=WSO2ESB
# Display name of the service
wrapper.ntservice.displayname=WSO2 Enterprise Service Bus (ESB)
# Description of the service
wrapper.ntservice.description=WSO2 Enterprise Service Bus (ESB)
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
Hartmut Zimmermann
Phone: +49 621 60-49477, Fax: +49 621 60-78817, E-Mail:
[EMAIL PROTECTED]
Postal Address: BASF IT Services GmbH, HS-AA - J660, 67059 Ludwigshafen,
Germany
www.basf-it-services.com
BASF IT Services GmbH, Registered Office: 67059 Ludwigshafen, Germany
Companies' Register: Amtsgericht Ludwigshafen, HRB 3541
Managing Directors:
Dr. Kurt Ettmüller, Dr. Ralf Sonnberger
Chairman of the Supervisory Board: Andrew Pike
"Asankha C.
Perera"
<[EMAIL PROTECTED] An
> [email protected]
Gesendet von: Kopie
esb-java-user-bou
[EMAIL PROTECTED] Thema
Re: [esb-java-user]
Basicquestions!!!
12.02.2008 07:43
Bitte antworten
an
[EMAIL PROTECTED]
2.org
Hi Hartmut
I am sorry but just now realized that I have uploaded the full project from
my IDEA IDE and that one needs to deploy only whats in
"/ESBManager/ManagerConsole/exploded/" :-)
here is my full log from the console.
Sorry but were can I see the available rmi adresses on the ESB?
INFO: Server startup in 1403 ms
java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.33.46.78;
nested
exception is:
java.net.ConnectException: Connection timed out: connect]
Are you using Windows by any chance... if so has the firewall been
temporarily paused or the RMI port allowed through it? Also sharing your
web.xml file and the log file will help..
For example, once I start the ESB (with the wrapper.conf custom settings) I
will see the JMX URL on the logs/wso2-esb.log file
[EMAIL PROTECTED]:~/java/wso2esb-1.6/bin$ ./wso2-esb-daemon.sh start
Starting WSO2 Enterprise Service Bus (ESB)...
[EMAIL PROTECTED]:~/java/wso2esb-1.6/bin$ tail -f ../logs/
service.log trace.log wso2-esb.log
wso2-esb-process.log
[EMAIL PROTECTED]:~/java/wso2esb-1.6/bin$ tail -f ../logs/wso2-esb.log
2008-02-12 12:11:58,288 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
HttpCoreNIOListener HTTP Listener starting on port : 8080
2008-02-12 12:11:58,288 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServerManager Starting transport http on port 8080
2008-02-12 12:11:58,445 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServerManager Starting transport vfs
2008-02-12 12:11:58,446 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServerManager Starting transport mailto
2008-02-12 12:11:58,446 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServerManager Starting transport admin/https
2008-02-12 12:11:58,446 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServerManager Ready for processing
2008-02-12 12:12:01,016 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServiceBusManager Starting the JMX Connector
2008-02-12 12:12:01,170 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServiceBusManager JMX Service URL :
service:jmx:rmi:///jndi/rmi://10.100.1.69:1099/esb
2008-02-12 12:12:02,043 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
TomcatServer Tomcat Server Started at https://10.100.1.69:9443/esb
2008-02-12 12:12:02,043 [127.0.1.1-asankha] [WrapperSimpleAppMain] INFO
ServiceBus [ESB] WSO2 ESB started in 9125 ms
asankha_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
