Re: My appliance blues

3 messages

Re: My appliance blues

Reply Threaded

Andrei,
So I was able to reproduce this problem by starting the appliance and photon while I had a Zone Alarm software firewall running. I know that you mentioned to Toli that you tried turning off your firewall as well, but this really sounds like exactly the same problem I had. Just to be sure, you have tried turning off your firewall, starting Photon and starting the appliance? Which firewall software are you using? Is it possible to set up a rule to allow all traffic from the IP address that your appliance gets (remember that you can get the appliance IP address by typing ifconfig at the login prompt)? The short story is that I think Windows-based software firewalls become confused when dealing with the VMWare instance.

graham

On 1/24/07, Andrei Lissovski <[hidden email]> wrote:

Hey Toli,

The OMS log is attached. It is a result of deleting the OMS log file, starting up OMS, starting up Photon (both status lights go green) and issuing a single order.

The following message shows up in the FIX Messages view:
    18:44:29    D    1001            BUY    DREI    10            LIMIT    100

Nothing shows up in the Open Orders view nor any other views.

The following output in the OMS log looks suspicious:
01:55:18,922  INFO main  ApplicationBase$1:initApplicationEventMulticaster:497 -
Unable to locate ApplicationEventMulticaster with name 'applicationEventMultica
ster': using default [org.springframework.context.event.SimpleApplicationEventMu
lticaster@ae506e]

There are no abnormalities on the Photon console.

Just in case, I'm also attaching my oms.xml which is the original oms.xml from the appliance but with a proper sender comp id in the defaultSessionID bean config.

Perhaps of relevance, I had to do the following dance with the appliance IP:
        mac=`ifconfig -a | grep "HWaddr" | cut -d " " -f 11`
        echo "eth0 mac $mac arp 1" > /etc/iftab and do a reboot. This is despite choosing the Keep option when starting the appliance for the first time. Without that it was grabbing the 127.0.0.1 address.

-Andrei

--
Marketcetera Trading Platform
download.run.trade.
www.marketcetera.org
_______________________________________________
m-etc-users mailing list
[hidden email]
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-users

Andrei Lissovski

Re: My appliance blues

Reply Threaded

Some javascript/style in this post has been disabled (why?)

Now that I think of it, I may have been turning off the firewall while the appliance and Photon have already been running, then trying to reconnect Photon to OMS.

I am using Norton AntiVirus 2006 which has "Auto-Protect". I'll try turning it off beforehand and report back on the results.

-Andrei

----- Original Message ----
From: Graham Miller <[hidden email]>
To: Andrei Lissovski <[hidden email]>; [hidden email]
Sent: Thursday, January 25, 2007 4:13:43 AM
Subject: Re: My appliance blues

Andrei,
So I was able to reproduce this problem by starting the appliance and photon while I had a Zone Alarm software firewall running. I know that you mentioned to Toli that you tried turning off your firewall as well, but this really sounds like exactly the same problem I had. Just to be sure, you have tried turning off your firewall, starting Photon and starting the appliance? Which firewall software are you using? Is it possible to set up a rule to allow all traffic from the IP address that your appliance gets (remember that you can get the appliance IP address by typing ifconfig at the login prompt)? The short story is that I think Windows-based software firewalls become confused when dealing with the VMWare instance.

graham

On 1/24/07, Andrei Lissovski <[hidden email]> wrote:

Hey Toli,

The OMS log is attached. It is a result of deleting the OMS log file, starting up OMS, starting up Photon (both status lights go green) and issuing a single order.

The following message shows up in the FIX Messages view:
    18:44:29    D    1001            BUY    DREI    10            LIMIT    100

Nothing shows up in the Open Orders view nor any other views.

The following output in the OMS log looks suspicious:
01:55:18,922  INFO main  ApplicationBase$1:initApplicationEventMulticaster:497 -
Unable to locate ApplicationEventMulticaster with name 'applicationEventMultica
ster': using default [org.springframework.context.event.SimpleApplicationEventMu
lticaster@ae506e]

There are no abnormalities on the Photon console.

Just in case, I'm also attaching my oms.xml which is the original oms.xml from the appliance but with a proper sender comp id in the defaultSessionID bean config.

Perhaps of relevance, I had to do the following dance with the appliance IP:
        mac=`ifconfig -a | grep "HWaddr" | cut -d " " -f 11`
        echo "eth0 mac $mac arp 1" > /etc/iftab and do a reboot. This is despite choosing the Keep option when starting the appliance for the first time. Without that it was grabbing the 127.0.0.1 address.

-Andrei

--
Marketcetera Trading Platform
download.run.trade.
www.marketcetera.org

_______________________________________________
m-etc-users mailing list
[hidden email]
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-users

Andrei Lissovski

Re: My appliance blues

Reply Threaded

In reply to this post by gm-mrktc

Some javascript/style in this post has been disabled (why?)

The culprit in my case turned out to be my net connectivity. I was using a hotel-style connection where you have to log in through a web browser before you can access the net. I was doing that on the host machine but of course the same step had to be performed on the appliance as well since it has its own different IP address. Normally, a text-mode browser can be used on the appliance for that: links, lynx, elinks, etc.

-Andrei

----- Original Message ----
From: "[hidden email]" <[hidden email]>
To: Graham Miller <[hidden email]>; [hidden email]
Sent: Thursday, January 25, 2007 11:18:30 AM
Subject: Re: [m-etc-users] My appliance blues

On 1/24/07, Andrei Lissovski <[hidden email]> wrote:

Hey Toli,

The OMS log is attached. It is a result of deleting the OMS log file, starting up OMS, starting up Photon (both status lights go green) and issuing a single order.

The following message shows up in the FIX Messages view:
    18:44:29    D    1001            BUY    DREI    10            LIMIT    100

Nothing shows up in the Open Orders view nor any other views.

The following output in the OMS log looks suspicious:
01:55:18,922  INFO main  ApplicationBase$1:initApplicationEventMulticaster:497 -
Unable to locate ApplicationEventMulticaster with name 'applicationEventMultica
ster': using default [org.springframework.context.event.SimpleApplicationEventMu
lticaster@ae506e]

There are no abnormalities on the Photon console.

Just in case, I'm also attaching my oms.xml which is the original oms.xml from the appliance but with a proper sender comp id in the defaultSessionID bean config.

Perhaps of relevance, I had to do the following dance with the appliance IP:
        mac=`ifconfig -a | grep "HWaddr" | cut -d " " -f 11`
        echo "eth0 mac $mac arp 1" > /etc/iftab and do a reboot. This is despite choosing the Keep option when starting the appliance for the first time. Without that it was grabbing the 127.0.0.1 address.

-Andrei

--
Marketcetera Trading Platform
download.run.trade.
www.marketcetera.org

_______________________________________________
m-etc-users mailing list
[hidden email]
http://lists.marketcetera.org/cgi-bin/mailman/listinfo/m-etc-users