JBoss Outsystems install issues

JBoss Outsystems install issues

  
Hi Everyone,

I have tried to install the community edition v7 on a CentOS 5 system. Database and packages install ran fine but when I run the configurationtool.sh, the point where it executes SCInstall, I receive the following error. It seems that the Deployment Controller is not working and I am not sure where to look to resolve the problem. Any help would be appreciated.

===== Restarting OutSystems Services =====
 
Stopping RMI Registry Service                              [  OK  ]
Stopping OutSystems Deployment Controller Service          [  OK  ]
Stopping OutSystems Log Service                            [  OK  ]
Starting RMI Registry Service                              [  OK  ]
Starting OutSystems Deployment Controller Service[WARNING] 
Starting OutSystems Log Service                            [  OK  ]
Service Center Installer v7.0.1.5
 
Start installing Service Center v7.0.1.5...
This operation may take a few minutes to complete...
 
Publishing Extension(s)...
Message 1
  [Error] Unable to contact Outsystems Deployment Controller Service
 
Message 2
  [Error] Unable to contact Outsystems Deployment Controller Service
Hi Tyler,


Could you provide your Deployment Controller logs (available @ /opt/outsystems/platform/logs), so we can try to understand what happened?

Did your machine changed IP Address meanwhile (did your reboot / restarted the network service and got a different IP) ?
If so you need to run configuration tool again and:
   Check that your deployment controller server hostname is OK, if not, please fix it :)

Let me know if this solved your problem. If not, please send us the logs if possible, so we can look into it and help you out.

Cheers,

Pedro



Thanks for pointing me in the right direction Pedro. After inspection of the logs and some fiddling it turns out that the incorrect JCE for java was causing problems. IP addresses were correct. I downloaded the correct version and everything ran smoothly. However, now the installer fails with two error messages during deployment:

Message 1
  [Error] Error message from node tresblue (127.0.0.1): Internal Error
java.lang.reflect.UndeclaredThrowableException
java.lang.reflect.UndeclaredThrowableException:
   at $Proxy10.stop(Unknown Source)
   at outsystems.hubedition.util.applicationServer.jboss51.x.executeImpl(Unknown Source) ..........

Message 2
  [Error] Error message from node tresblue (127.0.0.1): Deployment failed
Deployment failed. Could not invoke ping. Exception: Connection to https://127.0.0.1 refused   at outsystems.hubedition.http.HttpWebRequest.getResponse(Unknown Source)
   at outsystems.hubedition.deployservice.Deploy.invokePing(Unknown Source) ...............

I supposed Message 2 is due to the fact that it cannot find ServiceCenter/_ping.js . I saved a log file here for viewing.
Tyler Sampson wrote:
Thanks for pointing me in the right direction Pedro. After inspection of the logs and some fiddling it turns out that the incorrect JCE for java was causing problems. IP addresses were correct. I downloaded the correct version and everything ran smoothly. However, now the installer fails with two error messages during deployment:

Message 1
  [Error] Error message from node tresblue (127.0.0.1): Internal Error
java.lang.reflect.UndeclaredThrowableException
java.lang.reflect.UndeclaredThrowableException:
   at $Proxy10.stop(Unknown Source)
   at outsystems.hubedition.util.applicationServer.jboss51.x.executeImpl(Unknown Source) ..........

Message 2
  [Error] Error message from node tresblue (127.0.0.1): Deployment failed
Deployment failed. Could not invoke ping. Exception: Connection to https://127.0.0.1 refused   at outsystems.hubedition.http.HttpWebRequest.getResponse(Unknown Source)
   at outsystems.hubedition.deployservice.Deploy.invokePing(Unknown Source) ...............

I supposed Message 2 is due to the fact that it cannot find ServiceCenter/_ping.js . I saved a log file here for viewing.
 
 Hi Tyler, can you inspect server.log.
the file is usually located @ /opt/jboss-5.1.0.GA/server/outsystems/log/server.log

My guess is that there are deploying errors or some loading errors that make deploys fail after.

If you want, you can attach the file here and I can look if I can see what the problem is.

Regards

Luís Lopes
Well, im down to the final stretch! Thanks for the help Luis. Yes, there were some errors relating to java. Did a fresh install and it seemed to have fixed the problems this far. I can get into Service Center now and everything seems to be configured. But when I try to publish the System Components OSP in Factory -> Solutions, it bombs out with "There was an error processing your request. Please try again later..." and nothing appears under the Error monitor. Ive checked the server and deploy service logs with nothing coming up. Is there somewhere else I must now look?

Edit: Ive tried with some other OSP files and they publish fine. Just seems to be the System Components one. Perhaps running out of memory (exceeding some set defined limit or such)
So I found a solution to my prior problem. I extracted the solutions file and uploaded each espace and extension individually. This worked but i guess was less ideal because now the ECT_Provider espace complains that a reference to System->Espace_Version entity does not exist. On top of this, when I publish my own espace that consumes a web service, it throws an error: "Invalid Web Reference. The Reports web reference could not be imported because it is not supported". However, i uploaded the very same espace to a Windows server and this works fine. Surely a web service is meant to be interoperable. Ive also tested with another independant web service. After looking at the below error messages it seems like its having an issue with "string" parameters? The JBoss version is proving difficult to handle.

Invalid Web Reference
The Reports web reference could not be imported because it is not supported.
Exception Details:
[1] Invalid Web Reference: The Reports web reference could not be imported because it is not supported.
   at outsystems.hubedition.compiler.WebReference.$mbi(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$xth(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$co(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.dumpWebReferencesSql(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.updateScript(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.updateScriptThread(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.$nxi(Unknown Source)
   at outsystems.hubedition.compiler.fv.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.compiler.fs.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.ThreadStart.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:722)
[2] java.lang.IllegalArgumentException:Invalid parameter 'string' in method 'getVehiclesVisibleOnlyUpdated': couldn't locate corresponding parameter in WebReferenceMethod + 'WebRefReports_getVehiclesVisibleOnlyUpdated'
   at outsystems.hubedition.compiler.webservices.WSDLMethod.$wsd(Unknown Source)
   at outsystems.hubedition.compiler.webservices.WSDLMethod.$iwd(Unknown Source)
   at outsystems.hubedition.compiler.webservices.WSDLMethod.<init>(Unknown Source)
   at outsystems.hubedition.compiler.webservices.WSDLService.<init>(Unknown Source)
   at outsystems.hubedition.compiler.webservices.WsConsume.introspectGeneratedClasses(Unknown Source)
   at outsystems.hubedition.compiler.webservices.WsConsume.run(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$rxh(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$mbi(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$xth(Unknown Source)
   at outsystems.hubedition.compiler.WebReference.$co(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.dumpWebReferencesSql(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.updateScript(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.updateScriptThread(Unknown Source)
   at outsystems.hubedition.compiler.ESpace.$nxi(Unknown Source)
   at outsystems.hubedition.compiler.fv.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.compiler.fs.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.ThreadStart.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:722)
Hi Tyler, if you send me the eSpace with the wsdl, or just the wsdl,  I can try to help you.
But it seems that it might be a bug in the consumption of the webreference and should be sent to outsystems support.

Regards
Luís Lopes wrote:
Hi Tyler, if you send me the eSpace with the wsdl, or just the wsdl,  I can try to help you.
But it seems that it might be a bug in the consumption of the webreference and should be sent to outsystems support.

Regards
 
 Hi Luís, ive attached a sample espace which replicates the problem I am having. It consumes a currency conversion web service but fails during publishing. Thanks
Hi Tyler, can you please refresh the webreference using this method.

1)copy the wsdl into a file.
2) remove from the wsdl these ports.
<wsdl:port name="CurrencyConvertorHttpGet" binding="tns:CurrencyConvertorHttpGet">
      <http:address location="http://www.webservicex.net/CurrencyConvertor.asmx" />
    </wsdl:port>
    <wsdl:port name="CurrencyConvertorHttpPost" binding="tns:CurrencyConvertorHttpPost">
      <http:address location="http://www.webservicex.net/CurrencyConvertor.asmx" />
    </wsdl:port>
3) refresh the webreference, but change adress to the location of the file you created.

the espace should compile now.

In servicecenter change effectiveurl of the webreference in order for the request work at runtime.
I'll attach the oml with the webref refreshed since I have it here
Does anyone know what causes this problem ?


Deployment failed. Could not invoke ping. Exception: Connection to https://127.0.0.1 refused at outsystems.hubedition.http.HttpWebRequest.getResponse(Unknown Source)

Why OutSystems tries to access the https port ?