Deploy order in Mobicents JAIN SLEE - java

I`m trying to launch Mobicents USSD Gateway. Right now the problem is following:
Jboss is trying to deploy module before he deploys its dependencies hence returning the error:
SLEE DUs not deployed, due to missing dependencies:
file:/mobicents-jainslee-2.7.0.FINAL-jboss-5.1.0.GA/jboss-5.1.0.GA/server/default/deploy/mobicents-ussd-gateway/services-DU-1.0.0-SNAPSHOT.jar/
Missing Dependencies:
EventTypeID[name=ss7.map.DIALOG_REQUEST,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_DELIMITER,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.REJECT_COMPONENT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_PROVIDERABORT,vendor=org.mobicents,version=1.0]
ResourceAdaptorTypeID[name=MAPResourceAdaptorType,vendor=org.mobicents,version=2.0]
EventTypeID[name=ss7.map.service.suplementary.PROCESS_UNSTRUCTURED_SS_REQUEST,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_TIMEOUT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_REJECT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_CLOSE,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.service.suplementary.UNSTRUCTURED_SS_RESPONSE,vendor=org.mobicents,version=1.0]
LibraryID[name=library-map,vendor=library-map,version=2.0]
EventTypeID[name=ss7.map.DIALOG_NOTICE,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.ERROR_COMPONENT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_USERABORT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.INVOKE_TIMEOUT,vendor=org.mobicents,version=1.0]
EventTypeID[name=ss7.map.DIALOG_ACCEPT,vendor=org.mobicents,version=1.0]
MAPRA
I`ve tried to set up dependencies to deployment unit services-DU-1.0.0-SNAPSHOT.jar via jboss-deployement-structure.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="mobicents-slee-ra-jdbc-DU-1.0.0.FINAL.jar" />
<module name="mobicents-slee-ra-map-du-2.8.0-SNAPSHOT.jar" />
</dependencies>
</deployment>
</jboss-deployment-structure>
But this time he continues to try to install services-DU first, then reports missing dependencies, then succussfully installs dependencies, then tries to install services-DU again and throws exception:
2014-12-05 07:19:24,826 ERROR [org.mobicents.slee.container.deployment.jboss.DeploymentManager] (main) Failure invoking 'InstallDeployableUnitAction[file:/mobicents-jainslee-2.7.0.FINAL-jboss-5.1.0.GA/jboss-5.1.0.GA/server/default/deploy/mobicents-ussd-gateway/services-DU-1.0.0-SNAPSHOT.jar/]
javax.slee.management.DeploymentException: Failure encountered during deploy process.
at org.mobicents.slee.container.management.jmx.DeploymentMBeanImpl.install(DeploymentMBeanImpl.java:340)
at org.mobicents.slee.container.deployment.jboss.action.InstallDeployableUnitAction.invoke(InstallDeployableUnitAction.java:41)
at org.mobicents.slee.container.deployment.jboss.DeploymentManager.sciAction(DeploymentManager.java:316)
at org.mobicents.slee.container.deployment.jboss.DeploymentManager.installDeployableUnit(DeploymentManager.java:181)
at org.mobicents.slee.container.deployment.jboss.SLEESubDeployer.start(SLEESubDeployer.java:281)
I suppose it is a deploy order problem, but maybe I`m wrong and it is somethinf different. Can anyone help me with this?

This is not going to be a real answer... but someone may find it useful.
I'm having exactly the same problem with those jBoss deployment logs.
I don't know how to solve it, but at least in my case, jBoss continue logging messages and finally it starts the UssdGateway.
Here there are some logs after those errors:
11:21:26,288 INFO [UssdPropertiesManagement] (main) Loading USSD
Properties from
/home/ericsson/jboss-5.1.0.GA/server/default/data/UssdManagement_ussdproperties.xml
11:21:26,295 INFO [ShortCodeRoutingRuleManagement] (main) Loading
short code routig rule configuration from
/home/ericsson/jboss-5.1.0.GA/server/default/data/UssdManagement_scroutingrule.xml
11:21:26,295 WARN [ShortCodeRoutingRuleManagement] (main) Failed to
load the short code routig rule configuration file.
/home/ericsson/jboss-5.1.0.GA/server/default/data/UssdManagement_scroutingrule.xml
(No such file or directory) 11:21:26,302 INFO [UssdManagement] (main)
Started UssdManagement 11:21:26,332 INFO [ShellServer] (main)
Starting SS7 management shell environment 11:21:26,350 INFO
[ShellServer] (main) ShellExecutor listening at /127.0.0.1:3435
11:21:26,510 INFO [Http11Protocol] (main) Starting Coyote HTTP/1.1 on
http-127.0.0.1-8080 11:21:26,549 INFO [AjpProtocol] (main) Starting
Coyote AJP/1.3 on ajp-127.0.0.1-8009 11:21:26,566 INFO [ServerImpl]
(main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA
date=200905221634)] Started in 1m:7s:690ms
And the gateway is funtional, because I was able to test it with the SS7 simulator, and the TestServlet was instanciated. In fact, I was able to test it with a real HLR, so it kind of works.
Now we have to code some developments on top of it...
For that error, and what can imply... I still do not have an answer.
Anyway, if I finally guess how to fix it, I will update this text.
Just a final comment...
To build this mobicents solution, it was a real pain.
The original instructions in DeployUSSDGWFromTrunk fail.
I wasn't able to make it run, and it took us (a mate and me) about a week to make it compile and run, reading many google groups posts, and changing random stuff through the pom's.
Finally we got it running, but I still have that feeling that it is not a very good development base.

Related

wildfly-swarm launch from Eclipse "org.jboss.modules.ModuleLoadException"

For multiple projects, I use wildfly-swarm to avoid installing a webserver. The swarm jar file is generated and I can successfully launch it through "java -jar mypackage-swarm.jar".
However, to debug it easily, I would like to launch it via my IDE (eclipse). Either by directly launching my main class or using fakerplace, I have the following exception :
Fakereplace is running.
Dependencies not bundled, will resolve from local M2REPO
2017-01-17 08:31:41,806 org.wildfly.swarm.internal.SwarmMessages [main] DEBUG Logging Provider: org.jboss.logging.Log4jLoggerProvider
2017-01-17 08:31:41,811 org.wildfly.swarm.Swarm [main] DEBUG WFSWARM0020: Stage Config found in swarm.project.stage.file system property at location: null
2017-01-17 08:31:41,862 INFO [org.wildfly.swarm] (main) WFSWARM0018: Installed fraction: Logging - STABLE org.wildfly.swarm:logging:2016.12.1
2017-01-17 08:31:41,865 INFO [org.wildfly.swarm] (main) WFSWARM0018: Installed fraction: Undertow - STABLE org.wildfly.swarm:undertow:2016.12.1
2017-01-17 08:31:41,865 INFO [org.wildfly.swarm] (main) WFSWARM0018: Installed fraction: Spring WebMVC - STABLE org.wildfly.swarm:spring:2016.12.1
org.jboss.modules.ModuleLoadException: Error loading module from modules/org/apache/xerces/main/module.xml
...
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.11.0.SP5' (position: END_TAG seen ...<resources>\n <artifact name="xerces:xercesImpl:2.11.0.SP5"/>... #5:52)
I've found similar exceptions on internet, but I cannot find a solution.
Has anyone any idea on this ?
Why don't you just run it as jar application ?
I'm not sure how to do that in eclipse below is example in intellj but for eclipse you can find your solution here:
eclipse: how to debug a Java program as a .jar file?

JBoss is getting SHUTDOWN automatically in linux

I have deployed my application in jboss-4.0.2RC1. It is working fine. But after some time unexpectedly jboss is getting shutdown.
Please find the below logs
2015-09-21 21:09:28,995 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
2015-09-21 21:09:28,995 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown
2015-09-21 21:09:28,996 DEBUG [org.jboss.deployment.MainDeployer] Undeploying
I am not able to find the root cause?
Please suggest
What operating system is hosting your jboss? There are a number of reasons this could happen depending on your configuration. For instance, if you are running on Windows and running JBoss as a service, it will shutdown upon server logoff, unless you have added to your run.conf.bat something like:
set JAVA_OPTS=%JAVA_OPTS% -Xrs

Jetty JNDI Jumpstart NamingException unknown JNDI name prefix 'org.mortbay.jetty.webapp.WebAppContext test-jndi

Is there a way to solve this? I am also new to both tapestry, jetty, and openejb. I am having out of ideas =(
Configuration: Jetty 6.1.26 + OpenEJB 4.5.1 running Jumpstart for Tapestry 6.8
All compiles well, runs Ant collapser successfully, and deployed well. Jetty and OpenEJB are prestine from the binary zip. Just that OpenEjb have hsqldb-2.8 rather than hsqldb-2.9 which is instructed from the tapestry-jumpstart install manual.
But at some point when running in Eclipse Juno or IntelliJ IDEA (doesnt matter) I get this following log:
INFO - Deployed Application(path=E:\Workspace\IdeaProjects\tapestry\jumpstart-6.8.0\classpath.ear)
WARN [main] (Slf4jLog.java:76) - Config error at <New id="wiggle" class="org.mortbay.jetty.plus.naming.EnvEntry"><Arg><Ref id="wac"/></Arg><Arg>wiggle</Arg><Arg type="java.lang.Double">100</Arg><Arg type="boolean">true</Arg></New>
WARN [main] (Slf4jLog.java:89) - EXCEPTION
java.lang.reflect.InvocationTargetException
...
caused by: javax.naming.NamingException: Unknown JNDI name prefix 'org.mortbay.jetty.webapp.WebAppContext#40ad55ac{_test-jndi,c:'
at org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:130)
...
WARN [main] (Slf4jLog.java:76) - ContextDeployer$Scanner failed on 'C:\Server\jetty-6.1.26\contexts\test-jndi.xml
INFO [main] (Slf4jLog.java:67) - NO JSP Support for /jumpstart, did not find org.apache.jasper.servlet.JspServlet
INFO [main] (RegistryBuilder.java:129) - Adding module definition for class org.apache.tapestry5.ioc.services.TapestryIOCModule
Can someone tell me what went wrong with this? and what should I do?
Thanks much.

Unable to run struts program

I developed one web applications using struts. Now when i tried to run in another machine I am getting the following error. Following is taken from glassfish server log
SEVERE: INFO [http-thread-pool-8080-(1)] (CommonsLogger.java:31) - Parsing configuration file [struts-default.xml]
SEVERE: INFO [http-thread-pool-8080-(1)] (CommonsLogger.java:31) - Unable to locate configuration files of the name struts-plugin.xml, skipping
SEVERE: INFO [http-thread-pool-8080-(1)] (CommonsLogger.java:31) - Parsing configuration file [struts-plugin.xml]
SEVERE: INFO [http-thread-pool-8080-(1)] (CommonsLogger.java:31) - Parsing configuration file [struts.xml]
SEVERE: INFO [http-thread-pool-8080-(1)] (CommonsLogger.java:31) - Loading global messages from ApplicationResources
Also in the browser I am getting java.lang.reflect.InvocationTargetExceptionthis message. Please tell me where the problem lies.
This seems to be a similar problem to what is described in this article:
http://www.java.net/node/705006
It appears to be a GlassFish bug to incorrectly put "SEVERE:" before the log message that actually starts with "INFO".
FYI I came across this with SL4J and Glassfish 3.1. The exact same code logging via the JUL logger works perfectly, and then you get the "SEVERE:" when you swap it out with a proper logger.
Sadly I have not been able to find a resolution, and will post it when I find it. It is equally possible that they re-fix the bug in the next version of GlassFish.

Axis2 - always getting 404 errors

I'm trying to move some Web Service stubs from Metro to Axis2, however after generating my stubs using wsdl2java I'm constently getting 404 errors whenever I try and make a service call.
16/12/2010 11:14:57 AM org.apache.axis2.deployment.ModuleDeployer deploy
INFO: Deploying module: addressing-1.5.3-jar - file:/C:/Users/xxx/.m2/repository/org/apache/axis2/axis2/1.5.3/axis2-1.5.3-jar.jar
16/12/2010 11:14:57 AM org.apache.axis2.transport.http.HTTPSender sendViaPost
INFO: Unable to sendViaPost to url[xxxx]
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:307)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at au.com.jpaterso.betcalc.axis2.tab.LoginStub.getKey(LoginStub.java:184)
at au.com.jpaterso.betcalc.axis2.tab.Test.main(Test.java:13)
Exception in thread "main" org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:307)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at au.com.jpaterso.betcalc.axis2.tab.LoginStub.getKey(LoginStub.java:184)
at au.com.jpaterso.betcalc.axis2.tab.Test.main(Test.java:13)
The URL that it's trying to connect to is definitely correct as I can access it via my browser/SoapUI.
Any help would be greatly appreciated!
Thanks, Joseph.
You didn't provide much information about the environment in which you try to deploy your WS. E.g. is this a webapp running under Tomcat/JBoss or maybe the standalone server deployed with Axis2?
From the trace that you have posted I suppose that there is a connection with your server but your WS is not successfully deployed. I assume that you may use the standalone server for your tests and I suggest:
Go to your WS repository. On my test machine this would be something like ~/axis2-x.x.x/repository/services and make sure that your service is there (either the .aar file or the unpacked version).
Start the server and check if your service is really deployed. On my installation, for example the server will generate the following output (not complete):
me#melinuxpc:~/axis2-1.5.1/bin> ./axis2server.sh
Using AXIS2_HOME: xxx
Using JAVA_HOME: xxx
Using JAVA_OPTS: -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
Listening for transport dt_socket at address: 8000
[INFO] [SimpleAxisServer] Starting
[INFO] [SimpleAxisServer] Using the Axis2 Repository xxx
[SimpleAxisServer] Using the Axis2 Repository xxx
[SimpleAxisServer] Using the Axis2 Configuration File xxx
[INFO] Clustering has been disabled
[INFO] Deploying module: xxx
[INFO] Deploying Web service: MyTestService - file: ~/axis2-1.5.1/repository/services/MyTestService/
Check if your web service is deployed and there are no errors. You may check if the WSDL of the service is available "in the browser". On my test machine the URL will be:
http://localhost:8080/axis2/services/MyTestService?wsdl
While a list with all deployed services may be seen at:
http://localhost:8080/axis2/services/
And do not be too quick in abandoning Axis2 ;)
Good luck!
I also see this error when use "axis2-wsdl2code-maven-plugin" to generate stub for a .NET webservice (.asmx).
I fixed by disable "chunked" of _serviceClient. Only add below code in method Constructor of file stub.
_serviceClient.getOptions().setProperty(HTTPConstants.CHUNKED, "false");

Categories