I'm tweaking the wrapper.conf in ActiveMQ so that the service will add an extdir of our camel jars.
In the windows wrapper I was able to change the Application parameters so that it added the extdir to the startup
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.apache.activemq.console.Main
wrapper.app.parameter.2=--extdir "..\..\lib\companyname"
wrapper.app.parameter.3=start
This successfully loads the lib folder at startup on windows machines.
However when I change the linux wrapper.conf to match this it fails and the log shows:
INFO | jvm 1 | 2013/11/12 06:51:05 | INFO: Unrecognized option: --extdir "..\..\lib\companyname"
INFO | jvm 1 | 2013/11/12 06:51:05 | Usage: Main [--extdir <dir>] [task] [task-options] [task data]
These tweaks are planned to be chefinised so having the service working is a requirement.
This problem was caused by a difference in how the windows and linux JVM handle parameters.
Looking into the service wrapper helped me to figure this out.
http://wrapper.tanukisoftware.com/doc/english/prop-app-parameter-n.html
The solution was to split the --extdir and directory path into separate parameters like so:
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.apache.activemq.console.Main
wrapper.app.parameter.2=--extdir
wrapper.app.parameter.3=/opt/apache-activemq-5.8.0/lib/companyname
wrapper.app.parameter.4=start
Related
I created a simple project using ATG 10.2 .I want to know how to deploy it in weblogic. Please provide detailed procedure with screenshots,if possible.
To provide a 'detailed' procedure is beyond the scope of what StackOverflow is trying to provide. That said, if you have an understanding of the Weblogic Management Console you should be able to follow these steps to setup your initial deployment:
Create a Server
1.1 Specify a server name (eg. commerce) and the port number this server will run on (eg. 8180). Select it as a 'Stand-alone server'.
1.2 Once created go to Configuration > Server Start for the newly created server and modify the 'Arguments' block and include the following setings (assuming you are running windows, for Unix update your own paths)
-Datg.dynamo.data-dir=c:\ATG-Data -Datg.dynamo.server.name=commerce -d64 -XX:ParallelGCThreads=8 -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xms1152m -Xmx2048m -XX:NewSize=128m -XX:MaxNewSize=256m -XX:PermSize=128m -XX:MaxPermSize=256m
1.3 Save your Server
Create DataSources
2.1 In the Console click on 'Services > Data Sources'
2.2 Create 'New' datasources for each of your connections. As a minimum you will need connections for ATGSwitchingDS_A, ATGSwitchingDS_B (Assuming you are doing switching datasources) and ATGProductionDS. These names should match your JNDI names in your property files. Remember to specify the 'commerce' server as the target for each of the datasources.
Create Deployment
3.1 Assuming you've already built your EAR (eg. ATGProduction.ear) and it is available in c:\deployments you need to create a deployment in Weblogic. You need to create the deployment in the console and specify the target as 'commerce'. Once done you need to also 'start serving requests' on the deployment.
Start Server
You should now be able to see your server running on port 8180 with the log files being written to c:\ATG-Data\servers\commerce\logs.
If after this things aren't running, post specific questions about your issues and someone here might be able to help you.
I am new to restcomm two days ago i start following getting start guide and build restcomm from source. I am able to build successfully on my Mac machine but when i am trying to run JBoss server to run the application it is giving me some errors which i am not sure why. So my question is can i run restcomm application on MAC OS ?as mostly i see there are lot of answers are about linux OS.
MacBook-Pro:restcomm bilal$ ./start-restcomm.sh
BASEDIR: /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm
RESTCOMM_HOME: /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2
Looking for the appropriate interface
Looking for the IP Address, subnet, network and broadcast_address
Use of uninitialized value $ARGV[0] in concatenation (.) or string at /usr/local/bin/ipcalc line 136.
RestComm automatic configuration started:
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-dialogic-xms.sh...
Configuring Dialogic XMS...MS_MODE: mms
...activated Dialogic XMS...
...finished configuring Dialogic XMS!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-dialogic-xms.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-jboss-as.sh...
Configuring JBoss AS...
...disabled JBoss splash screen...
Finished configuring JBoss AS!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-jboss-as.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-load-balancer.sh...
Deactivated Load Balancer on SIP stack configuration file
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-load-balancer.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-mobicents-ms.sh...
TRUSTSTORE_FILE is not set
Configuring Mobicents Media Server... MS_ADDRESS BIND_ADDRESS NETWORK 192.168.1.0 SUBNET_MASK RTP_LOW_PORT 34534 RTP_HIGH_PORT 65535
Configured UDP Manager
Updated log configuration
Finished configuring Mobicents Media Server!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-mobicents-ms.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-restcomm.sh...
Configuring RestComm...
Updated mobicents-dar properties
Updated RestComm configuration
Configured Fax Service credentials
Configured Sms Aggregator using OUTBOUND PROXY
Configured the Speech Recognizer
Configured Acapela Speech Synthesizer
Configured VoiceRSS Speech Synthesizer
Disabled TeleStax Proxy
sed: 1: "/Users/muhammadbilal/Re ...": invalid command code m
Configured SMPP Account Details
Configured RestComm!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-restcomm.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-sip-connectors.sh...
Configuring Application Server...
Configured SIP Connectors and Bindings
sed: 1: "/Users/muhammadbilal/Re ...": invalid command code m
Configured gather-statistics
TRUSTSTORE_FILE is not set
Finished configuring Application Server!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-sip-connectors.sh!
RestComm automatic configuration finished!
./start-restcomm.sh: line 182: ${MS_EXTERNAL^^}: bad substitution
TelScale RestComm started running on standalone mode. Screen session: restcomm.
Using IP Address:
Yes you can run Restcomm on Mac OSX, the main difference is that you need to do some more configuration manually since the auto configuration scripts don't work there as well as they do for GNU/Linux.
Please check this guide:
https://github.com/RestComm/Restcomm-Connect/wiki/Restcomm-OSX-native-installation
If you still have issues after trying such configuration, please post back here.
Best regards,
Antonis Tsakiridis
I created two sepaerate directories in which I installed the Standalone Mule ESB server:
/ee/mmc-distribution-mule-console-bundle-3.5.2-HF1
/ee2/mmc-distribution-mule-console-bundle-3.5.2-HF1
I start up the first server, and below is the status:
[root#x240perf2 mmc-distribution-mule-console-bundle-3.5.2-HF1]# ./status.sh
MMC is running as PID=1998.
Mule Enterprise Edition is running as PID=2619.
Then I try to start the second instance:
[root#x240perf2 mmc-distribution-mule-console-bundle-3.5.2-HF1]# ./startup.sh
Port 8585 is in use, please make it available and try again.
So apparently the port 8585 is being used by the original instnace
So I stop the first instnace, and start the second istance, which comes up successfully, as follows:
./startup.sh
Please enter the desired port for Mule [Default 7777]:
Starting MMC, please wait...
class com.sun.jersey.multipart.impl.MultiPartConfigProvider
class com.sun.jersey.multipart.impl.MultiPartReader
class com.sun.jersey.multipart.impl.MultiPartWriter
[11-13 16:49:19] WARN HttpSessionSecurityContextRepository [http-bio-8585-exec-1]: Failed to create a session, as response has been committed. Unable to store SecurityContext.
[11-13 16:49:32] WARN HttpMethodBase [http-bio-8585-exec-12]: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
[11-13 16:49:38] WARN HttpSessionSecurityContextRepository [http-bio-8585-exec-12]: Failed to create a session, as response has been committed. Unable to store SecurityContext.
Nov 13, 2014 4:49:50 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
Nov 13, 2014 4:49:50 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8585"]
But notice it seems to be using 8585 for tomcat (of which I know little about, except it some sort of app server, never used it)
I examined this site:
http://www.mulesoft.org/documentation/display/33X/Running+Multiple+Mule+Instances
but it does nto discuss the issue., and the page it points do does not seem current. Did I misunderstand something
Is it possible to run two separate instances of Mule ESB at the same time
and if so, how ? (how would I change the port its using, what file should I modify)
Thanks
Edit: my second post in response to answer:
(BTW: I am using Mule ESB standalone Enterprise Edition 3.5.2)
To make sure I did not have any apps that were running
on port 8585, I shutdown my original instance, and created two new instances, and made sure no apps were deployed to either instance.
I brought up the first instance without issue, but the second instance I brought up still gives me the port 8585 in use error (from startup.sh)
This site says that the MMC default port is 7777, but the tomcat default port on which it runs is 8585
http://www.mulesoft.org/documentation/display/current/Setting+Up+MMC-Mule+ESB+Communications
I used the following command to find all files within my second instance of por t 8585
find . -type f |xargs grep "8585
Other than log files I got two hits
startup.sh
and
/mmc-3.5.2-HF1/apache-tomcat-7.0.52/conf/server.xml
I did NOT find in either instance the $MULE_HOME/apps/mmc/mule-config.xml (probably because I have no apps deployed)
In the server.xml, the MMC apparently uses tomcat to
handle the MMC applicaiton, and server.xml contains
the following:
<Connector port="8585" protocol="HTTP/1.1"
So I guess I could change 8585 to 8586 at this point, but ...
The startup.sh has serveral (about 9 or 10) hardcode dreferences to 8585 to check that the MMC is running and take action if it is or is not running
So do I actually have to change the entire startup.sh to replace 8585 with 8586 i the second instance as well as change the server.xml port 8585 reference ?
Thanks
You can run as many instances as you want, as long they don't use the same ports. Looks like you are deploying something in port 8585, so in the second instance you have to select a different port.
Is that port being used in any application that you developed and deployed in the Mule runtime?
Also, if you are using the Mule runtime with the MMC agent activated, you also have to change the port for the agent in the second instance. I think you can do that in the /conf/wrapper.conf or by passing to the startup script the following parameter:
-Dmule.mmc.bind.port=7778
(or any port that is free).
You can run as many as you want.
In MMC we can able to deploy and run many applications each applications has its own instance
I have gone through the mule doc.
https://www.mulesoft.org/documentation-3.2/display/MULE2INTRO/Installing+Mule
I am trying to understand how to make multiple instances from a single esb server.
I have to make a cluster of the instance.
But I havent get any clear idea about doing this.
I am using a ubuntu OS.
I want to know that.
1) Do I have to make 2 directory which containing to 2 server.
2 if no Do I have to configure 1 server So that I can make as many instance as I can.
3 if yes Then please can some one help me with step.
I often set up multiple mule instances on Ubuntu linux in parallel, and I use parallel directories that contain the Mule standalone installation.
Here is a template upstart script I have used to run it on startup under the mule user. You should copy this file to /etc/init/mule-instance-name.conf, and create an associated file /etc/default/mule-instance-name in which you set the MULE_HOME environment variable to the directory where you installed that instance.
description "Run Mule ESB instance 1"
author "Ryan Hoegg"
setuid mule
setgid nogroup
# we need real ethernet before starting:
start on (local-filesystems and net-device-up IFACE!=lo)
stop on runlevel [016]
kill timeout 30
script
. /etc/default/mule-instance1
exec $MULE_HOME/bin/mule
end script
I've been hacking and googling for a while now, and I've found several statck overflow threads that seemed like they were written for older versions of intellij, with various application servers. Usually they tell you to enter
java -Xdebug -Xrunjdwp:transport=dt_socket,address=51887,suspend=n,server=y
One answer suggests using something like
-agentlib:jdwp:transport=dt_socket,address=51887,suspend=n,server=y
But then I get this:
Error occurred during initialization of VM
Could not find agent library: libjdwp:transport.jnilib (searched /Library/Java/JavaVirtualMachines/1.6.0_37-b06-434.jdk/Contents/Libraries:/System/Library/Java/Extensions:/Library/Java/Extensions:.)
Then after one or the other of the above they tell you something like "Edit Configurations> jetty > remote and enter localhost, 51887" (the port number varies)
However in 12, the page you land on after you select remote has a plethora of options, and is asking for JNDI ports, not jdwp ports on another tab it actually suggests the jdwp parameters above.
Researching the JNDI port bit, generally yields instructions to add args like this to your command line...
-Dcom.sun.management.jmxremote= \
-Dcom.sun.management.jmxremote.port=1099 \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.authenticate=false\
I've done that too and I can see port 1099 held by java (using lsof) and I can telnet to 1099, so I know the JVM is listening. (We'll try not to worry about the fact that that appears to say, open up a port by which anyone install arbitrary java code over the network to your computer without a password)
However, in Intellij whenever I try to deploy and debug it gives me the following message:
I can see java RMI communications over 1099 when I snoop port 1099 with wireshark (but they are illegible). Evidently, the communications are not satisfactory for Intellij, so I'm wondering if there's something I need to do to Jetty to get it to play nice. Note that changing the Jetty version is not presently an option, so let's not go there :).
I've also tried removing the artifact, disabling make, and trying to just connect the debugger, but it still gives me the same red baloon and error message, so evidently the JNDI (port 1099) part is required.
Does anyone see something I'm doing wrong, or know of something else I should do to get this to work?
(I'm wondering if it is something similar to this: http://youtrack.jetbrains.com/issue/IDEA-65746 jboss issue)
Edit: Thanks to this google groups post I've discovered that it is possible to get the debugger connected if you don't specify Edit Configurations> + > jetty > remote, but instead choose Edit Configurations > + > remote, but debug and deploy is what I'm after so that's only a half solution.
Jetty remote configuration requires several manual steps which are performed automatically when you start Jetty directly from IDEA using the local configuration instead.
If you absolutely must use the remote configuration, try the following steps:
In the Remote staging section of the Server tab of the IDEA Jetty remote run configuration:
specify Same file system for Type and Host
specify path to the <Jetty home>/contexts folder in the Local path field of the contexts section
(settings will differ if you have Jetty running on another machine than IDEA, but I assume it's the same machine in your case)
Pass the following VM parameters to the Jetty process:
-Dcom.sun.management.jmxremote=
-Dcom.sun.management.jmxremote.port=<JNDI port>
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-DOPTIONS=jmx
<JNDI port> value should be the same as specified in the JNDI port field of the IDEA Jetty run configuration
Pass the following configuration files to the Jetty process (in the command line):
etc/jetty-jmx.xml
etc/jetty.xml
If you need to debug, you should also pass to Jetty process VM parameters taken from IDEA Jetty run configuration: Startup/Connection tab, select Debug list item under the To debug remote server JVM ...
Here is the sample command line to start Jetty process with all the required options:
java -Xdebug -Xrunjdwp:transport=dt_socket,address=60208,suspend=n,server=y -DSTOP.PORT=0 -Dcom.sun.management.jmxremote= -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -DOPTIONS=jmx -Dfile.encoding=UTF-8 -classpath start.jar etc/jetty-jmx.xml etc/jetty.xml