[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Infinispan as Remote server mode with HotRod



Hi Ben,

Thanks again for reply. I have tried values for the environment variables in hotrod-client.properties file as :

$OPENSHIFT_GEAR_DNS:$OPENSHIFT_INFINISPAN_TCP_PROXY_PORT

Here $OPENSHIFT_GEAR_DNS is the variable which I get after doing ssh into Infinispan gear.

In Logs I can see its not able to connect with the Infinispan server running in scaled application. Error logs are:


java.lang.RuntimeException: org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport
org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInstantiation(SecureReflectionAccess.java:186)
org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: 5302f1df1---a9a000037-test.rhcloud.com/50.17.194.185:38047
org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:90)


Thanks,
Priyanka Gupta

-----Original Message-----
From: Ben Parees [mailto:bparees redhat com]
Sent: Monday, February 17, 2014 8:17 PM
To: Gupta, Priyanka E.
Cc: wdecoste redhat com; dev lists openshift redhat com
Subject: Re: Infinispan as Remote server mode with HotRod

----- Original Message -----
> From: "priyanka e gupta" <priyanka e gupta accenture com>
> To: bparees redhat com
> Cc: wdecoste redhat com, dev lists openshift redhat com
> Sent: Monday, February 17, 2014 9:39:23 AM
> Subject: RE: Infinispan as Remote server mode with HotRod
>
> Hi,
>
> Have already tried with OPENSHIFT_GEAR_DNS value which is something
> like 5301f6----38f00001a-unit.rhcloud.com. Still there is a issue.
> Mentioned in my previous mail also:
>
>  I Have also tried  replacing value of OPENSHIFT_INFINISPAN_PORT  with
> OPENSHIFT_GEAR_DNS, but still a issue as:

1) as mentioned earlier, OPENSHIFT_INFINISPAN_PORT is the wrong value to use, it is never going to work from a remote gear.

2) You can't replace the port with the dns (hostname).  You need to be using the hostname and the port in conjunction.

$GEAR_DNS:$OPENSHIFT_INFINISPAN_TCP_PROXY_PORT

>
>  org.infinispan.client.hotrod.exceptions.TransportException::
>  java.net.SocketTimeoutException
> >
>
> Thanks,
> Priyanka
> -----Original Message-----
> From: Ben Parees [mailto:bparees redhat com]
> Sent: Monday, February 17, 2014 7:55 PM
> To: Gupta, Priyanka E.
> Cc: wdecoste redhat com; dev lists openshift redhat com
> Subject: Re: Infinispan as Remote server mode with HotRod
>
> OPENSHIFT_INFINISPAN_IP is not the right variable to use..that is
> going to be the local ip (127.x.x.x) for infinispan which is only
> valid within the infinispan gear.  you need to use the DNS entry for
> the infinispan gear, which you can find as GEAR_DNS on the infinispan
> gear (same as the hostname you use to ssh into the infinispan gear).
>
>
> Ben Parees | OpenShift
>
> ----- Original Message -----
> > From: "priyanka e gupta" <priyanka e gupta accenture com>
> > To: bparees redhat com
> > Cc: wdecoste redhat com, dev lists openshift redhat com
> > Sent: Monday, February 17, 2014 7:19:09 AM
> > Subject: RE: Infinispan as Remote server mode with HotRod
> >
> > Hi Ben,
> >
> > Thanks a lot for response. Now I am able to get proxy varibles after
> > ssh into Infinispan cartridge.
> >
> > But I have an application deployed in separate gear. It has
> > hotrod-client.properties file as:
> >
> > infinispan.client.hotrod.server_list = $OPENSHIFT_INFINISPAN_IP:$
> > OPENSHIFT_INFINISPAN_TCP_PROXY_PORT;
> > infinispan.client.hotrod.socket_timeout = 500
> > infinispan.client.hotrod.connect_timeout = 10
> >
> > Variable are replaced by the actual  value. But it still gives error
> > saying could not fetch the transport:
> >
> > org.infinispan.client.hotrod.exceptions.TransportException:: Could
> > not fetch transport
> >
> >
> > I Have also tried  replacing value of OPENSHIFT_INFINISPAN_PORT
> > with OPENSHIFT_GEAR_DNS, but still a issue as:
> >
> > org.infinispan.client.hotrod.exceptions.TransportException::
> > java.net.SocketTimeoutException
> >
> > Is it possible to achieve it with application deployed in separate
> > gear. If yes, how?
> >
> > Thanks a ton in advance..
> >
> >
> > Thanks,
> > Priyanka
> >
> >
> > -----Original Message-----
> > From: Ben Parees [mailto:bparees redhat com]
> > Sent: Monday, February 17, 2014 2:54 AM
> > To: Gupta, Priyanka E.
> > Cc: wdecoste redhat com; dev lists openshift redhat com
> > Subject: Re: Infinispan as Remote server mode with HotRod
> >
> > Are you looking in the infinispan gear or your web framework gear?   The
> > env
> > variables will only appear in the infinispan gear.
> >
> > Here is how I deployed the infinispan cartridge you referenced and
> > confirmed the presence of the environment variables:
> >
> > 1) create app
> > rhc app create inf jbossews-2
> > http://cartreflect-claytondev.rhcloud.com/reflect?github=lunafromthe
> > mo on/openshift-origin-cartridge-infinispan
> > -s
> >
> > 2) ssh into the infinispan gear (important, this is the infinispan
> > gear and not the main gear.  You can list all the gears via "rhc app
> > show appname
> > --gears)
> >
> > ssh  5-----------e 5-----------e-bparees rhcloud com
> >
> > 3) display environment variables
> > [5-----------e-bparees.rhcloud.com 5-----------e]\> env | grep INF |
> > grep PROXY
> > OPENSHIFT_INFINISPAN_TCP_PROXY_PORT=43197
> > OPENSHIFT_INFINISPAN_CLUSTER_PROXY_PORT=43196
> >
> > Note that if the infinispan cartridge in question published its
> > environment variables, they would also appears in the jbossews gear
> > (or whatever other cartridge you use for a web framework) since
> > those subscribe to environment publications (see the mysql cartridge
> > for an example of a cartridge that publishes environment variables
> > to other
> > cartridges)
> >
> >
> > Ben Parees | OpenShift
> >
> > ----- Original Message -----
> > > From: "priyanka e gupta" <priyanka e gupta accenture com>
> > > To: bparees redhat com, wdecoste redhat com,
> > > dev lists openshift redhat com
> > > Sent: Saturday, February 15, 2014 11:33:59 PM
> > > Subject: RE: Infinispan as Remote server mode with HotRod
> > >
> > > Hi,
> > >
> > >
> > > There is no such variable I could find for TCP even after adding
> > > cartridge in Scaled app as OPENSHIFT_INFINISPAN_TCP_PROXY_PORT.
> > >
> > >
> > > Thanks & Regards
> > >
> > > Priyanka Gupta
> > >
> > > ________________________________
> > > From: Ben Parees [bparees redhat com]
> > > Sent: 15 February 2014 21:27:47
> > > To: wdecoste redhat com; dev lists openshift redhat com; Gupta,
> > > Priyanka E.
> > > Subject: RE: Infinispan as Remote server mode with HotRod
> > >
> > > Resending my reply from a few days ago:
> > >
> > >
> > > Did you see the PROXY_PORT environment variables? That is the
> > > externally exposed port for the cartridge which is what you need
> > > to use when communicating to the gear from a different gear or application:
> > >
> > > OPENSHIFT_INFINISPAN_TCP_PROXY_PORT=38048
> > > OPENSHIFT_INFINISPAN_HTTP_PROXY_PORT=38046
> > > OPENSHIFT_INFINISPAN_CLUSTER_PROXY_PORT=38047
> > >
> > > you also need to be using the external IP/DNS for the gear, which
> > > you can find in OPENSHIFT_GEAR_DNS
> > >
> > > You will only get those PROXY ports exposed if you deploy the
> > > infinispan cartridge in a scaled application.
> > >
> > >
> > >
> > > Sent from my Android phone using TouchDown
> > > (www.nitrodesk.com<UrlBlockedError.aspx>)
> > >
> > >
> > > -----Original Message-----
> > > From: [priyanka e gupta accenture com]
> > > Received: Saturday, 15 Feb 2014, 0:13
> > > To: wdecoste redhat com, dev lists openshift redhat com
> > > Subject: RE: Infinispan as Remote server mode with HotRod
> > >
> > >
> > > Hi,
> > >
> > > Please reply how this can be achieved? waiting for the response.
> > >
> > >
> > > Thanks & Regards
> > >
> > > Priyanka Gupta
> > >
> > > ________________________________
> > > From: Gupta, Priyanka E.
> > > Sent: 12 February 2014 16:08:36
> > > To: wdecoste redhat com; dev lists openshift redhat com
> > > Cc: Ganesh, Rupa; Madathilthattantav, S.
> > > Subject: Infinispan as Remote server mode with HotRod
> > >
> > > Hi,
> > >
> > > I have a Use case where I am using Infinispan as a remote Server
> > > mode with HotRod , where The Infinsiapn will be hosted in one
> > > application gear and should be accessible to application hosted in
> > > other gears.
> > > For testing this use case ,I created a scaled application and
> > > added infinispan as downloadable cartridge from
> > > https://raw.github.com/bdecoste/openshift-origin-cartridge-infinis
> > > pa
> > > n/
> > > master/metadata/manifest.yml
> > > .
> > >
> > > When I ssh and check for the variables required to configure in my
> > > test application hosted in a separate gear to connect to the
> > > hosted remote Infinispan server, these are the variables I came across:
> > >
> > > OPENSHIFT_INFINISPAN_HOST="52fb3fdc----5000021-xyz.rhcloud.com"
> > > OPENSHIFT_INFINISPAN_PORT="43--3"
> > >
> > > As I understand it requires INFINISPAN_TCP_PORT to connect with
> > > the Infinispan HotRod server present in separate gear. But
> > > according to my findings this is not provided as a variable in downloadable cartridge.
> > > Can you please provide the solution for that?
> > >
> > > Is this a  current limitation or an issue?
> > > Or is there any other way to achieve this use case ?
> > > Waiting for your response….
> > >
> > >
> > >
> > > Thanks & Regards,
> > > Priyanka Gupta
> > >
> > > ________________________________
> > >
> > > This message is for the designated recipient only and may contain
> > > privileged, proprietary, or otherwise confidential information. If
> > > you have received it in error, please notify the sender
> > > immediately and delete the original. Any other use of the e-mail
> > > by you is prohibited.
> > > Where allowed by local law, electronic communications with
> > > Accenture and its affiliates, including e-mail and instant
> > > messaging (including content), may be scanned by our systems for
> > > the purposes of information security and assessment of internal
> > > compliance with Accenture policy. .
> > > __________________________________________________________________
> > > __
> > > __
> > > ________________
> > >
> > > www.accenture.com
> > >
> >
> >
> > ________________________________
> >
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise confidential information. If
> > you have received it in error, please notify the sender immediately
> > and delete the original. Any other use of the e-mail by you is prohibited.
> > Where allowed by local law, electronic communications with Accenture
> > and its affiliates, including e-mail and instant messaging
> > (including content), may be scanned by our systems for the purposes
> > of information security and assessment of internal compliance with
> > Accenture policy. .
> > ____________________________________________________________________
> > __
> > ________________
> >
> > www.accenture.com
> >
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you
> have received it in error, please notify the sender immediately and
> delete the original. Any other use of the e-mail by you is prohibited.
> Where allowed by local law, electronic communications with Accenture
> and its affiliates, including e-mail and instant messaging (including
> content), may be scanned by our systems for the purposes of
> information security and assessment of internal compliance with Accenture policy. .
> ______________________________________________________________________
> ________________
>
> www.accenture.com
>


________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. .
______________________________________________________________________________________

www.accenture.com


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]