I don't see any issues when I run the server and client on the local worksapce(via eclipse). However there are issues if the client is executed from a different machine than on server or executed from exported client product(i.e. Eclipse rcp).
I also read article on JNDI and various online blogs. Please let me know if I am missing anything obvious. Trying to get the remote client working for couple of days now. :(
Object returnValue = context.lookup("ejb:GeoEE/GeoEJB/UserRegistrationService!com.geo.request.ejb.IUserRegistrationService");
above line returns Object in local environment and null in case of remote or exported client.
Replace "ejb:" to "/"
If not set, use this properties to init context(replace server and port):
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.provider.url=http-remoting://127.0.0.1:8080
jboss.naming.client.ejb.context=true
Related
I am trying to create a new lagom scala project on windows 7 machine (behind proxy) but I get error message "org.eclipse.jgit.api.errors.TransportException: git://github.com/lagom/lagom-scala.g8.git: Connection time out"
Here is the command : sbt new lagom/lagom-scala.g8
I have the proxy environment variable http_proxy set but still I get this error. Any thoughts idea..to make this work ?
There's a discussion about this at https://github.com/lagom/lagom/issues/683
The conclusion is that this is a limitation of sbt 0.13.13, which uses the git protocol to clone templates and cannot be made to use an alternate protocol.
You can work around this by both forcing a newer version of sbt and specifying the complete https URL of the repository, like this:
sbt new -Dsbt.version=0.13.15 https://github.com/lagom/lagom-scala.g8
After successfully running subversion for years on a Windows 2008 server, I recently moved to Windows 8.1, mainly because the machine does also serve videos to my home network (works fine) and because Windows 8 provides better energy saving on my platform than Windows 2008 server did. So far, so good.
Then I tried to re-install Subversion. I intend to use the built-in server application svnserve.exe. I downloaded the latest windows package, installed it (success), and configured a service (svnserve --service ...) which I can successfully start using the Windows Service Management Console. Port 80 is already taken by a different application, so I let subversion pick 3690, which is fine for me. I used netstat to confirm that svnserve.exe is bound to port TCP:3690, which is listed OK. Just to clear one potential roadblock I also disabled the Windows firewall.
Then I created a sample repository named "test" using svnadmin locally, success as well, a subversion file structure appeared on the harddisk.
Problems arise when I try to access the repository using my local browser (Firefox), an attempt to connect to URLs
http://127.0.0.1:3690[/svn|/svn/test]
all three give me the same cryptical response:
( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries commit-revprops depth log-revprops atomic-revprops partial-replay inherited-props ephemeral-txnprops file-revs-reverse ) ) )
Somehow I have expected a subversion GUI instead.
Connecting from a remote machine via browser reveals the same useless line of text.
Connecting from a remote machine using my usual Tortoise client gives the message:
Unable to connect to a repository at URL 'http://xxx.xxx.xxx.xxx:3690/svn/test
Error running context: The server unexpectedly closed the connection
I tried to add the --log-file option to svnserve, and indeed a log file appears once I start the service, but it is empty and it remains empty.
Trying to use svnserve -X instead of running it as a service reveals the exact same behavior.
Seems I am stuck. Anyone who has an idea what I can do to get that thing working?
Just to help out another beginner running into the same problem ... I finally found the problem: I simply used the wrong client, svnserve does not support web browsers. Using the Tortoise client, and providing the correct prefix (svn:127.0.0.1/...) was all I had to do.
The long version:
If one wants to work with the simple, reliable, fast, but plain-text and proprietary protocol based) svnserve service, he needs to use a proprietary client, like Tortoise, and the svn: prefix instead of http/https:, and no port, like
svn://mysvnserver/testrepo
If needed, one may even reconfigure svnservice to use authentication and encryption later. svnserve isn't supporting web browsers, if one tries to access svnserve using a web browser like I did he gehts the internals of the svn protocol dumped to the screen.
If one wants to use his web browser, http/https protocol, and niceties, like a user friendly browser based interface and some remote administration capabilities, he must not use svnserve, but install a web server service (like apache) and configure if for use with subversion.
So in the end my problem had nothing to do with Windows 8. It just has slipped from my mind that years ago I went the apache path, while now I decided that the built-in svnserve service was good enough for my needs.
Armin.
I am working with database project for that I installed postgresSql, jboss and apache 2.4 in windows 7. I am able to get data from postgresql to jboss server then using apache(localhost:80) able to get data in browser within LAN. Now I want to connect this server to external world. Other people could access my server from browser. How to make my server to available for external server.
Thanks
You may edit the pg_hba.conf file
we are doing worklight app on a android and a desktopenvironment(for facebook) that works fine on the liberty profile server (developer worklight environment).
Know we need to post this app on Facebook but to do this we need to use the https protocol on our WAS server, to do this we set the ip, port, protocol: to our external server, and deploy our app with build for remote server, but when the app tried to call an adapter on the server, the Firefox console returns us this:
[09:58:50.675] "response [https://[publicIP]:[port]/WorklightPocProj/apps/services/../../invoke] success: /*-secure-
{"challenges":{"wl_antiXSRFRealm":{"WL-Instance-Id":"ih80d8pjg6la8ubccb7503b936"}}}*/"
and
[09:58:50.675] "defaultOptions:onFailure Procedure invocation error."
The application security on our WAS server is disabled and the ip/port are reachable too.
if i add to the XML adapter on the procedures securityTest="wl_unprotected" the app runs correctly, but i don't to do this workaround
Is there any configuration that we are missing on the app or in our WAS server?
A lot of time since this question but just for trying to help people that hit this question because of the search "defaultOptions:onFailure Procedure invocation error".
Also facing this issue in Worklight 6.1
In my case I faced this issue because I had the following configuration in the adapter .xml:
<procedure name="anyMethod"></procedure>
This works in the development server, but in a stand alone server (at least in WAS) you have to change it for:
<procedure name="submitAuthentication" securityTest="wl_unprotected"></procedure>
In both cases it is unprotected.
So I have a couple MQs set up in WASv8.5. I have tested these and they work fine, now I need to test some functionality. In order to do this I downloaded the "New" MQJExplorer and I noticed the ability to load JNDI from a context. Now since the Websphere instance is running locally can I just hook directly into the Websphere Context? I tried selecting Websphere Application Server and it gives me an address box starting with
iiop://
I tried using...
iiop://localhost
but that didn't work and neither did
iiop://localhost:9064
I tried looking about iiop and I couldn't really find how to enable it on WebSphere. How can I make this work?
Make sure the port is Bootstrap Port and also you may try adding providerURL under WAS console: Environment > Naming > Name Space Binding.