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
Related
i have connected the Apache MQ broker service through java only by downloading active mq jars in dependency. but activemq web console not connecting. http://localhost/8161/admin . Please tell me is there any setting or configuration is need to connect ?
Verify activemq.xml file from /conf . It must contain your correct IP for transport connectors.
Check log4j.properties in /conf, update logging options to WARN at least, DEBUG if possible. Update File Logging Path.
Run ./activemq start
Let the system throw an exception.
Check logs from the path you specified.
Look for log exception in Stack Overlow or Google to get first analysis on error.
More details
I am using Apache Tomcat 8.5.12 with JOSSO single sign on .
After configuration I can not start the tomcat server and I get this error.
Everything is well configured.
Does anyone have an idea that can help me to start the server ?enter image description here
Apache Tomcat 8.5 doesn't play nice with the JOSSO Agent for Apache Tomcat 8 as the former has changed the approach for hooking into the event bus. Therefore, an ad-hoc SSO agent is needed, included in an early access release of JOSSO 1.8.12, available here for download : https://github.com/atricore/josso1/releases/tag/1.8.12-rc1-release
A binary distribution is included, hence there's no need to build from the source.
In order to install it, make sure to manually replace the "old" agent artifacts - namely the JOSSO Agent for Tomcat 8 JAR files - with the ones that ship with 1.8.12 RC1.
As far as configuration is concerned, the following changes in the $CATALINA_HOME/lib/josso-agent-config.xml descriptor need to be applied for the JOSSO Agent for Apache Tomcat 8.5 to be instantiated.
From:
<bean class="org.josso.tc80.agent.CatalinaSSOAgent" name="josso-tc80-agent">
To:
<bean class="org.josso.tc85.agent.CatalinaSSOAgent" name="josso-tc85-agent">
As of the JOSSO server component, there is no need to perform any upgrade nor configuration change.
Iam trying to run elasticsearch-mesos on mesos.My machine is running ubuntu 14.04. I have running mesos cluster installed with mesosphere packages by following these instructions. When I run test frameworks it gets lister under frameworks of mesosUI but for elasticsearch-mesos its not getting listed under mesos webUI. I want to run elasticsearch-mesos on top of mesos. I followed instructions given here. When I run ./elasticsearch-mesos I am getting a message in terminal
I0108 17:24:01.898540 23861 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
I tried running ./elasticsearch-mesos on both mesos masters and slaves.
The last few lines of terminal output is given below
2015-01-08 17:24:01,881:23844(0x7f175bfff700):ZOO_INFO#zookeeper_init#786: Initiating
client connection, host=localhost:2181 sessionTimeout=10000 watcher=0x7f1762a3e6a0
sessionId=0 sessionPasswd=<null> context=0x7f1710002530 flags=0
I0108 17:24:01.881392 23858 sched.cpp:137] Version: 0.21.1
2015-01-08 17:24:01,881:23844(0x7f172b7fe700):ZOO_INFO#check_events#1703: initiated
connection to server [127.0.0.1:2181]
2015-01-08 17:24:01,897:23844(0x7f172b7fe700):ZOO_INFO#check_events#1750: session
establishment complete on server [127.0.0.1:2181], sessionId=0x14ac7c469270006,
negotiated timeout=10000
I0108 17:24:01.898455 23861 group.cpp:313] Group process (group(1)#127.0.1.1:38668)
connected to ZooKeeper
I0108 17:24:01.898509 23861 group.cpp:790] Syncing group operations: queue size (joins,
cancels, datas) = (0, 0, 0)
I0108 17:24:01.898540 23861 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
According to the README at https://github.com/mesosphere/elasticsearch-mesos,
you may need to modify mesos.master.url to point to the same ZK url that the Mesos master is using (maybe not localhost). If you're using a single-master Mesos cluster, you can skip the ZK url and point this parameter directly to the Mesos master.
Please also note that the elasticsearch framework is a bit outdated, so use with caution
I m using eclipse indigo and i installed the Jboss Server earlier.i though that every thing is fine;
But when i make a right clik on a JSP page for exemple ,there is no "Deploy" ,and if i what to deploy the whole project..the same thing i can't do it because the is no "Deploy" option.
iand if i ighone all that and do a "Run As" --> "Run on a server" i get a http 404 error saying the requested ressource is not available.
i have Jboss in my eclipse ,is there any why to know that Jboss is well insatlled??
Thank you
The easiest way to check whether JBoss 7 is running is to access native management interface.
Usually it's bound to 9999 port.
In order to verify the port look for port attribute of management native interface socket binding in standalone.xml (standalone-full.xml or whatever configuration you are using)
For localhost it would be:
http://localhost:9999
Another way to check JBoss 7 status is to use management console.
Usually it's bound to 9990 port.
In order to verify the port look for port attribute of management HTTP interface socket binding in standalone.xml (standalone-full.xml or whatever configuration you are using).
For localhost it would be:
http://localhost:9999
Additionally, you can check the so called marker files.
Just go to deployments directory and look for .deployed file (if the file exists it means that your application is successfully deployed).
You can read more about deployment descriptors at:
https://docs.jboss.org/author/display/AS7/Application+deployment
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