[JBoss JIRA] (ISPN-4148) ispn-cli --help containes arguments related only to jboss-cli
by Vitalii Chepeliuk (JIRA)
Vitalii Chepeliuk created ISPN-4148:
---------------------------------------
Summary: ispn-cli --help containes arguments related only to jboss-cli
Key: ISPN-4148
URL: https://issues.jboss.org/browse/ISPN-4148
Project: Infinispan
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.0.Alpha1
Reporter: Vitalii Chepeliuk
Assignee: Mircea Markus
Usage:
jboss-cli.sh/jboss-cli.bat [--help] [--version] [--controller=host:port]
[--connect] [--file=file_path]
[--commands=command_or_operation1,command_or_operation2...]
[--command=command_or_operation]
[--user=username --password=password]
[--no-local-auth]
[--timeout=timeout]
--help (-h) - prints (this) basic description of the command line utility.
--version - prints the version info of the JBoss AS release, JVM and
system environment.
--controller - the default controller host and port to connect to when
--connect option (described below) is specified or when the
connect command is issued w/o the arguments. The default
controller host is localhost and the port is 9999.
--connect (-c) - instructs the CLI to connect to the controller on start-up
(to avoid issuing a separate connect command later).
--gui - GUI built on top of the CLI, the only difference is that it
brings up a GUI instead of a command line. In this mode, the
CLI will automatically connect during start-up. You can
optionally specify --controller, if necessary.
--file - specifies a path to a file which contains commands and
operations (one per line) that should be executed (in a
non-interactive mode). The CLI will terminate the session
immediately after the last command has been executed or if
some command or operation failed.
--command - specifies a single command or an operation that should be
executed in the CLI session. The CLI will terminate the
session immediately after the command or the operation has
been executed. Note: --command argument is optional in a
sense that any word (or phrase without whitespaces in it)
will be assumed to be a command (or an operation).
--commands - specifies a comma-separated list (the list must not contain
whitespaces) of commands and operations that should be
executed in the CLI session. The CLI session will be
automatically terminated as soon as the last command or
operation has been executed or after the first error. Note:
--commands argument is optional in a sense that any
comma-separated list at the end of the argument list will be
assumed to be the list of commands and operations.
--user - if the controller requires user authentication, this argument
can be used to specify the user name as a command line
argument. If the argument isn't specified and the
authentication is required the user will be prompted to enter
the user name when the connect command is issued. Local
authentication is automatically disabled if a user is specified.
--password - specifies the password for authentication while connecting to
the controller as a command line argument. If the argument
isn't specified and the authentication is required the user
will be prompted to enter the password when the connect
command is issued.
--no-local-auth - disable the local authentication mechanism which allows the CLI
to demonstrate that it is being executed locally to the server
being managed through an exchange of tokens using the filesystem.
--timeout - specifies home many milliseconds to wait for a given command
to return. The value provided must be a positive integer.
Defaults to 5000 milliseconds when not provided.
For a list of available commands execute
help --commands
The resulting listing may depend on the current context. E.g. some of the
commands require an established connection to the controller (standalone or
domain). These commands won't appear in the listing unless the connection has
been established. Other commands may depend on the availability of specific
subsystems. E.g. if the messaging subsystem is not available, messaging-related
commands will not be listed.
Here are some of the most basic supported commands:
cn (or cd) - change the current node path to the argument;
connect - connect to the server or domain controller;
deploy - deploy an application;
help (or h) - print this message;
history - print or disable/enable/clear the history expansion;
ls - list the contents of the node path;
pwn (or pwd) - prints the current working node;
quit (or q) - quit the command line interface;
undeploy - undeploy an application;
version - prints the version and environment information.
For a more detailed description of a specific command, execute the command with
'--help' as the argument.
Tab-completion is supported for the commands, just press the tab key to start.
Operation requests start with './' or '/' and follow the format:
[node-type=node-name (/node-type=node-name)*] : operation-name ['('[name=value [, name=value]*]')'] [{header (;header)*}]
e.g. /subsystem=web/connector=http:read-attribute(name=protocol)
If the operation request doesn't require a node path then the request can start
with ':' followed by an operation name and the property list if necessary ('/:'
and './:' are also possible).
Whitespaces between the separators are insignificant.
If the operation doesn't require arguments then the brackets '()' are optional.
Tab-completion for operation requests supports node types and names, operation
names, property names and, in some cases, values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4148) ispn-cli --help containes arguments related only to jboss-cli
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-4148?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-4148:
------------------------------------
Assignee: Tristan Tarrant (was: Mircea Markus)
> ispn-cli --help containes arguments related only to jboss-cli
> -------------------------------------------------------------
>
> Key: ISPN-4148
> URL: https://issues.jboss.org/browse/ISPN-4148
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha1
> Reporter: Vitalii Chepeliuk
> Assignee: Tristan Tarrant
>
> Usage:
> jboss-cli.sh/jboss-cli.bat [--help] [--version] [--controller=host:port]
> [--connect] [--file=file_path]
> [--commands=command_or_operation1,command_or_operation2...]
> [--command=command_or_operation]
> [--user=username --password=password]
> [--no-local-auth]
> [--timeout=timeout]
> --help (-h) - prints (this) basic description of the command line utility.
> --version - prints the version info of the JBoss AS release, JVM and
> system environment.
> --controller - the default controller host and port to connect to when
> --connect option (described below) is specified or when the
> connect command is issued w/o the arguments. The default
> controller host is localhost and the port is 9999.
> --connect (-c) - instructs the CLI to connect to the controller on start-up
> (to avoid issuing a separate connect command later).
> --gui - GUI built on top of the CLI, the only difference is that it
> brings up a GUI instead of a command line. In this mode, the
> CLI will automatically connect during start-up. You can
> optionally specify --controller, if necessary.
> --file - specifies a path to a file which contains commands and
> operations (one per line) that should be executed (in a
> non-interactive mode). The CLI will terminate the session
> immediately after the last command has been executed or if
> some command or operation failed.
> --command - specifies a single command or an operation that should be
> executed in the CLI session. The CLI will terminate the
> session immediately after the command or the operation has
> been executed. Note: --command argument is optional in a
> sense that any word (or phrase without whitespaces in it)
> will be assumed to be a command (or an operation).
> --commands - specifies a comma-separated list (the list must not contain
> whitespaces) of commands and operations that should be
> executed in the CLI session. The CLI session will be
> automatically terminated as soon as the last command or
> operation has been executed or after the first error. Note:
> --commands argument is optional in a sense that any
> comma-separated list at the end of the argument list will be
> assumed to be the list of commands and operations.
> --user - if the controller requires user authentication, this argument
> can be used to specify the user name as a command line
> argument. If the argument isn't specified and the
> authentication is required the user will be prompted to enter
> the user name when the connect command is issued. Local
> authentication is automatically disabled if a user is specified.
>
> --password - specifies the password for authentication while connecting to
> the controller as a command line argument. If the argument
> isn't specified and the authentication is required the user
> will be prompted to enter the password when the connect
> command is issued.
>
> --no-local-auth - disable the local authentication mechanism which allows the CLI
> to demonstrate that it is being executed locally to the server
> being managed through an exchange of tokens using the filesystem.
> --timeout - specifies home many milliseconds to wait for a given command
> to return. The value provided must be a positive integer.
> Defaults to 5000 milliseconds when not provided.
> For a list of available commands execute
> help --commands
> The resulting listing may depend on the current context. E.g. some of the
> commands require an established connection to the controller (standalone or
> domain). These commands won't appear in the listing unless the connection has
> been established. Other commands may depend on the availability of specific
> subsystems. E.g. if the messaging subsystem is not available, messaging-related
> commands will not be listed.
> Here are some of the most basic supported commands:
> cn (or cd) - change the current node path to the argument;
> connect - connect to the server or domain controller;
> deploy - deploy an application;
> help (or h) - print this message;
> history - print or disable/enable/clear the history expansion;
> ls - list the contents of the node path;
> pwn (or pwd) - prints the current working node;
> quit (or q) - quit the command line interface;
> undeploy - undeploy an application;
> version - prints the version and environment information.
> For a more detailed description of a specific command, execute the command with
> '--help' as the argument.
> Tab-completion is supported for the commands, just press the tab key to start.
> Operation requests start with './' or '/' and follow the format:
> [node-type=node-name (/node-type=node-name)*] : operation-name ['('[name=value [, name=value]*]')'] [{header (;header)*}]
> e.g. /subsystem=web/connector=http:read-attribute(name=protocol)
> If the operation request doesn't require a node path then the request can start
> with ':' followed by an operation name and the property list if necessary ('/:'
> and './:' are also possible).
> Whitespaces between the separators are insignificant.
> If the operation doesn't require arguments then the brackets '()' are optional.
> Tab-completion for operation requests supports node types and names, operation
> names, property names and, in some cases, values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4147) Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4147?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4147:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1079883
> Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
> ---------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4147
> URL: https://issues.jboss.org/browse/ISPN-4147
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha1
> Reporter: Vitalii Chepeliuk
> Assignee: Tristan Tarrant
>
> Fcli/standalone_caches_test.rb:84: warning: Insecure world writable dir /qa/tools in PATH, mode 040777
> Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/cli/CommandLineMain : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
> at org.jboss.modules.Module.loadModuleClass(Module.java:548)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:249)
> at org.jboss.modules.Module.run(Module.java:280)
> at org.jboss.modules.Main.main(Main.java:455)
> Jobs are here
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4147) Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-4147?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-4147:
------------------------------------
Assignee: Tristan Tarrant (was: Mircea Markus)
> Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
> ---------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4147
> URL: https://issues.jboss.org/browse/ISPN-4147
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha1
> Reporter: Vitalii Chepeliuk
> Assignee: Tristan Tarrant
>
> Fcli/standalone_caches_test.rb:84: warning: Insecure world writable dir /qa/tools in PATH, mode 040777
> Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/cli/CommandLineMain : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
> at org.jboss.modules.Module.loadModuleClass(Module.java:548)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:249)
> at org.jboss.modules.Module.run(Module.java:280)
> at org.jboss.modules.Main.main(Main.java:455)
> Jobs are here
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4147) Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-4147?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-4147:
------------------------------------
Summary: Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError (was: Running CLI CLI command from file, ispn-cli.sh --file <path/to/file> fails with UnsupportedClassVersionError)
> Running CLI commands from file(ispn-cli.sh --file <path/to/file>) fails with UnsupportedClassVersionError
> ---------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4147
> URL: https://issues.jboss.org/browse/ISPN-4147
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha1
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
>
> Fcli/standalone_caches_test.rb:84: warning: Insecure world writable dir /qa/tools in PATH, mode 040777
> Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/cli/CommandLineMain : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
> at org.jboss.modules.Module.loadModuleClass(Module.java:548)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:249)
> at org.jboss.modules.Module.run(Module.java:280)
> at org.jboss.modules.Main.main(Main.java:455)
> Jobs are here
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4147) Running CLI CLI command from file, ispn-cli.sh --file <path/to/file> fails with UnsupportedClassVersionError
by Vitalii Chepeliuk (JIRA)
Vitalii Chepeliuk created ISPN-4147:
---------------------------------------
Summary: Running CLI CLI command from file, ispn-cli.sh --file <path/to/file> fails with UnsupportedClassVersionError
Key: ISPN-4147
URL: https://issues.jboss.org/browse/ISPN-4147
Project: Infinispan
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.0.Alpha1
Reporter: Vitalii Chepeliuk
Assignee: Mircea Markus
Fcli/standalone_caches_test.rb:84: warning: Insecure world writable dir /qa/tools in PATH, mode 040777
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/cli/CommandLineMain : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
at org.jboss.modules.Module.loadModuleClass(Module.java:548)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at org.jboss.modules.Module.run(Module.java:280)
at org.jboss.modules.Main.main(Main.java:455)
Jobs are here
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4146) Javadoc for useEagerLocking attribute is wrong
by Martin Gencur (JIRA)
Martin Gencur created ISPN-4146:
-----------------------------------
Summary: Javadoc for useEagerLocking attribute is wrong
Key: ISPN-4146
URL: https://issues.jboss.org/browse/ISPN-4146
Project: Infinispan
Issue Type: Bug
Components: Documentation-Core
Affects Versions: 7.0.0.Alpha1
Reporter: Martin Gencur
Assignee: Martin Gencur
Priority: Minor
Fix For: 7.0.0.Alpha2
The Javadocs says the same for useEagerLocking and eagerLockingSingleNode. The description for useEagerLocking is wrong though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4145) Infinispan cluster configuration with distribution mode
by Vijay Chandra (JIRA)
[ https://issues.jboss.org/browse/ISPN-4145?page=com.atlassian.jira.plugin.... ]
Vijay Chandra updated ISPN-4145:
--------------------------------
Description:
We have two web applications running on different machines on the same network. We have cache configuration file namely.ie. ecp-cluster-infinispan.xml on each of the instance. we tried of configure the infinispan cluster in distributed mode using jgroups in order to to retrieve/access the cache values two applications(each other). We used groups-udp.xml file for Jgroups configuration which is bundled with infinispan core. We are not able to retrieve the cache entries of one web application(one machine) on another web application (other machine).
Note : No clustering of web applications.
Distributed cache which allows Infinispan to scale linearly by defining a number of cluster-wide replicas for each cache entry.
I am attaching the configuration files which are used to configure the infinispan in distributed mode. Is this a configuration issue or use case.
I am ready to give more information if required. We are performing Proof of concept on Infinispan to use in our organization.
was:
We have two web applications running on different machines on the same network. We have cache configuration file namely.ie. ecp-cluster-infinispan.xml on each of the instance. we tried of configure the infinispan cluster in distributed mode using jgroups in order to to retrieve/access the cache values two applications(each other). We used groups-udp.xml file for Jgroups configuration which is bundled with infinispan core. We are not able to retrieve the cache entries of one web application(one machine) on another web application (other machine).
Note : No clustering of web applications.
Distributed cache which allows Infinispan to scale linearly by defining a number of cluster-wide replicas for each cache entry.
I am attaching the configuration files which are used to configure the infinispan in distributed mode. Is this a configuration issue or use case.
> Infinispan cluster configuration with distribution mode
> -------------------------------------------------------
>
> Key: ISPN-4145
> URL: https://issues.jboss.org/browse/ISPN-4145
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.3.0.Final
> Environment: OS: Linux,
> App server :JBoss EAP - Version 6.2.0.GA
> Infinispan version :5.3.0.Final
> Jgroups version :jgroups-3.3.1.Final
> Reporter: Vijay Chandra
> Assignee: Dan Berindei
> Attachments: config_files.zip
>
>
> We have two web applications running on different machines on the same network. We have cache configuration file namely.ie. ecp-cluster-infinispan.xml on each of the instance. we tried of configure the infinispan cluster in distributed mode using jgroups in order to to retrieve/access the cache values two applications(each other). We used groups-udp.xml file for Jgroups configuration which is bundled with infinispan core. We are not able to retrieve the cache entries of one web application(one machine) on another web application (other machine).
> Note : No clustering of web applications.
> Distributed cache which allows Infinispan to scale linearly by defining a number of cluster-wide replicas for each cache entry.
> I am attaching the configuration files which are used to configure the infinispan in distributed mode. Is this a configuration issue or use case.
> I am ready to give more information if required. We are performing Proof of concept on Infinispan to use in our organization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4145) Infinispan cluster configuration with distribution mode
by Vijay Chandra (JIRA)
[ https://issues.jboss.org/browse/ISPN-4145?page=com.atlassian.jira.plugin.... ]
Vijay Chandra updated ISPN-4145:
--------------------------------
Attachment: config_files.zip
Configuration files
> Infinispan cluster configuration with distribution mode
> -------------------------------------------------------
>
> Key: ISPN-4145
> URL: https://issues.jboss.org/browse/ISPN-4145
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.3.0.Final
> Environment: OS: Linux,
> App server :JBoss EAP - Version 6.2.0.GA
> Infinispan version :5.3.0.Final
> Jgroups version :jgroups-3.3.1.Final
> Reporter: Vijay Chandra
> Assignee: Dan Berindei
> Attachments: config_files.zip
>
>
> We have two web applications running on different machines on the same network. We have cache configuration file namely.ie. ecp-cluster-infinispan.xml on each of the instance. we tried of configure the infinispan cluster in distributed mode using jgroups in order to to retrieve/access the cache values two applications(each other). We used groups-udp.xml file for Jgroups configuration which is bundled with infinispan core. We are not able to retrieve the cache entries of one web application(one machine) on another web application (other machine).
> Note : No clustering of web applications.
> Distributed cache which allows Infinispan to scale linearly by defining a number of cluster-wide replicas for each cache entry.
> I am attaching the configuration files which are used to configure the infinispan in distributed mode. Is this a configuration issue or use case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years