Running HornetQ 2.2.14 in standalone mode.
HornetQ is behind a firewall, thus requiring a static port.
How can one define this port?
This page shows how to define this port in JBoss, but has nothing about HornetQ standalone mode.
This page claims that the relevant configuration file (jboss-service.xml) is in a file called hornetq-service.sar, but it's not there...
So how is this done?
Related
I'm new to the Hyper-V and trying to setup a lab. Here is my setup:
Cisco switch with a SPAN port (configured to mirror in/out, replicate the encapsulation, source port for the span is a trunk). I verified that I see all packets on the SPAN port
Server with Hyper-V VM that has two NICs. One is for general connectivity, the other is configured as a mirror destination. Vlan identification is disabled. Mapped to a virtual switch
Virtual switch is mapped to a dedicated server port connected to the Cisco SPAN port. OS sharing is allowed. VLAN identification is disabled. NDIS capture is enabled but NDIF also lists an errors in the window: "The Selected Extension is not operating correctly. Check the event logs for further information. If this is a non-Microsoft Extention, contact the vendor for further troubleshooting steps."
Server NIC is configured as a Hyper-V source as explained here: https://cloudbase.it/hyper-v-promiscuous-mode/
I can only see traffic from the server on the VM port. Nothing from the SPAN.
Is it even possible to setup what I'm trying to achieve? If so, am I missing something?
Thank you very much
VM NIC:
VSwitch:
Create a new web application in VS2017
Right-click web application->Add->Container Orchestration support-> Service Fabric
Run (F5) locally (success), loads on http://machinename:<port in manifest>
Publish to Azure SF cluster + container registry
This URL should load http://<azurecluster>:<port in manifest>
But it is not loading.
The only thing that loads in the cluster is the Service Fabric Explorer, which shows the application running without error.
Am I doing anything wrong?
I think this has something to do with an incorrect port.
When adding a container ourselves through the template (as in the pic below), these are the options:
Host Port and container Port. Are these mapped correctly in
Container Orchestration support (step #2 above)?
In Host port help icon, it says the port might need to be opened on
load balancer. Do I need to do such things in my steps above?
Moreover, only the container port is provided in
config (applicationManifest.xml) in Step #2. So what about the host port?
How is the container port mapped to the application port?
Why didn't we have to do it locally (if this is the problem)?
The service specifies the container port in the manifest:
<Resources>
<Endpoints>
<Endpoint Name="Guest1TypeEndpoint" UriScheme="http" Port="8081" Protocol="http"/>
</Endpoints>
</Resources>
The application specifies the host port in the manifest:
<Policies>
<ContainerHostPolicies CodePackageRef="Code">
<PortBinding ContainerPort="80" EndpointRef="Guest1TypeEndpoint"/>
</ContainerHostPolicies>
</Policies>
In this example, container port 8081 is mapped to host port 80.
More info here.
You also need to configure an Azure Load Balancer rule and probe, to forward traffic (on port 80) into the cluster.
After that, you should see it work properly.
I have created instance on google cloud platform (allowed http traffic). Used Ubuntu 14.04 OS. Installed oracle java8 and apache-tomcat.Placed war file in tomcat webapps and started server. Server started successfully.
Question is how to access my application, tried accessing external ip of instance from web browser but no response.
Can anyone tell me the process or missing things I have not done.
Thanks in advance.
I had the same issue and eventually solved it
In my case the solution was simple.Check the firewall rule is really tcp:8080 and not tcp:80 as created by default.
Changed this and finally saw my tomcat welcome page.
1)Added http port (8080) in firewall rules in Networking section
2)Refreshing VM instance by click refresh option before accessing with external ip followed by http server port(8080)
I hope after following first step, need to refresh VM instance to access web serve with external IP
I am writing an action script 3.0 client that has to communicate with a remote server. In localhost environment everything works fine, but if I test the client in the real internet environment there is no connection.
My guess is that it has to do with the cross domain policy file, but calling
Security.loadPolicyFile("xmlsocket://"+targetIP);
does not send the <policy file request\> message to the server on the default 843 port, or any port for that matter. I think it might be because flash recognises that the address is local and omits the request. But I need to receive it to be able to implement the answer on the server. Otherwise I'd be coding blindly.
Is there a way to force the flash client to behave as if it was in a different domain while still being in localhost so I can troubleshoot this issue without involving a remote host? I don't have many resources in that regard.
Try running the client on 'localhost', and load the policy file from '127.0.0.1'.
They should be seen as different 'domains'.
I have a Kiosk that connects to a local socket server so it can access some hardware. If the kiosk code is stored locally, it can access the socket perfectly.
However, and I know for good reason, if the kiosk code is hosted on a remote server, it can not access the local socket server because of a sandbox violation.
The problem is that all of these kiosks are hosted on AppEngine, so when I am done making changes, it takes hours to render out to a single HTML file, and change all the css/js location links.
Is there anyway possible for the allow the SWF file to access the local socket server when it is hostel remotely?
Also,
The socket server is a Java app that I dont have the source to. I run it locally through the terminal
I've had the same problem.
The thing is that with Flash player 10 security with sockets has become much stricter. Just placing crossdomain.xml on the server won't do anything - you actually have to send the crossdomain policy file to any client who connects.
The simplest solution is provided by Adobe - they've provided a couple of scripts, one perl and one python, which will set up a policy file server. You can find them here:
Setting up a socket policy server