5:08 p.m.
[disconnected /] patch apply
../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
{
"outcome" : "success",
"result" : {}
}
[disconnected /]
[disconnected /]
[disconnected /]
[disconnected /] exit
logging.configuration already set in JAVA_OPTS
./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
./bin/jboss-cli.sh: line 81: `fi'
Known issue ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
5:09 p.m.
I think this is a known issue that occurs if you apply the patch when
you are in a [disconnected] state.
Stuart
Arun Gupta wrote:
[disconnected /] patch apply
../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
{
"outcome" : "success",
"result" : {}
}
[disconnected /]
[disconnected /]
[disconnected /]
[disconnected /] exit
logging.configuration already set in JAVA_OPTS
./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
./bin/jboss-cli.sh: line 81: `fi'
Known issue ?
Arun
5:14 p.m.
On Jun 4, 2014, at 4:08 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
[disconnected /] patch apply
../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
{
"outcome" : "success",
"result" : {}
}
[disconnected /]
[disconnected /]
[disconnected /]
[disconnected /] exit
logging.configuration already set in JAVA_OPTS
./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
./bin/jboss-cli.sh: line 81: `fi'
Known issue ?
Yes, it’s IMO a design mistake with offline patching. The big issue is that the
patch tool patches itself live instead of isolating itself or staging. So like this issue
is caused by the cli shell script getting updated before its fully parsed. The good is
that its harmless, as long as you quit before running any non-patch commands (as mentioned
in the instructions).
We need to fix this in 9.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
5:14 p.m.
On Jun 4, 2014, at 4:08 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
[disconnected /] patch apply
../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
{
"outcome" : "success",
"result" : {}
}
[disconnected /]
[disconnected /]
[disconnected /]
[disconnected /] exit
logging.configuration already set in JAVA_OPTS
./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
./bin/jboss-cli.sh: line 81: `fi'
Known issue ?
Yes, it’s IMO a design mistake with offline patching. The big issue is that the
patch tool patches itself live instead of isolating itself or staging. So like this issue
is caused by the cli shell script getting updated before its fully parsed. The good is
that its harmless, as long as you quit before running any non-patch commands (as mentioned
in the instructions).
We need to fix this in 9.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
5:18 p.m.
An issue filed ?
On Wed, Jun 4, 2014 at 5:14 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
On Jun 4, 2014, at 4:08 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
> [disconnected /] patch apply
> ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
> {
> "outcome" : "success",
> "result" : {}
> }
> [disconnected /]
> [disconnected /]
> [disconnected /]
> [disconnected /] exit
>
>
> logging.configuration already set in JAVA_OPTS
> ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
> ./bin/jboss-cli.sh: line 81: `fi'
>
> Known issue ?
>
Yes, it’s IMO a design mistake with offline patching. The big issue is that the patch
tool patches itself live instead of isolating itself or staging. So like this issue is
caused by the cli shell script getting updated before its fully parsed. The good is that
its harmless, as long as you quit before running any non-patch commands (as mentioned in
the instructions).
We need to fix this in 9.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
--
http://blog.arungupta.me
http://twitter.com/arungupta
4:15 a.m.
No, there is no issues filed for this particular one yet, i am going to
create one.
Thanks,
Emanuel
On 04/06/14 23:18, Arun Gupta wrote:
An issue filed ?
On Wed, Jun 4, 2014 at 5:14 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
>
> On Jun 4, 2014, at 4:08 PM, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>
>> [disconnected /] patch apply
>> ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch
>> {
>> "outcome" : "success",
>> "result" : {}
>> }
>> [disconnected /]
>> [disconnected /]
>> [disconnected /]
>> [disconnected /] exit
>>
>>
>> logging.configuration already set in JAVA_OPTS
>> ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi'
>> ./bin/jboss-cli.sh: line 81: `fi'
>>
>> Known issue ?
>>
> Yes, it’s IMO a design mistake with offline patching. The big issue is that the patch
tool patches itself live instead of isolating itself or staging. So like this issue is
caused by the cli shell script getting updated before its fully parsed. The good is that
its harmless, as long as you quit before running any non-patch commands (as mentioned in
the instructions).
>
> We need to fix this in 9.
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
3611
days inactive
3612
days old
5 comments
4 participants
participants (4)
-
Arun Gupta -
Emanuel Muckenhuber -
Jason Greene -
Stuart Douglas