[JBoss JIRA] Created: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
10:34 a.m.
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char
in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Piotr Piastucki commented on JBCACHE-1444:
------------------------------------------
This issue affect WebLogic server too, because threads are named like this in WL:
ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']
As a result I cannot deploy v3.0 under WL:
Caused by: javax.management.MalformedObjectNameException: Invalid character ':' in
value part of property
at javax.management.ObjectName.construct(ObjectName.java:602)
at javax.management.ObjectName.<init>(ObjectName.java:1394)
at
org.jboss.cache.jmx.JmxRegistrationManager.registerAllMBeans(JmxRegistrationManager.java:135)
... 56 more
Is there any way to instruct Jbosscache not to register MBeans by default?
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:50 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Peter Kovgan commented on JBCACHE-1444:
---------------------------------------
yes,
you put
<jmxStatistics
enabled="false"/>
in treecache.xml file
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:25 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani updated JBCACHE-1444:
-----------------------------------
Fix Version/s: 3.1.0
Affects Version/s: 3.0.0.GA
Priority: Critical (was: Major)
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.1.0
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani updated JBCACHE-1444:
-----------------------------------
Fix Version/s: 3.0.1.CR3
3.0.1.GA
(was: 3.1.0)
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.CR3, 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani commented on JBCACHE-1444:
----------------------------------------
Ok, I've added a JVM system property where you can specify the prefix. From the
(updated) Javadocs on JmxRegistrationManager:
* Note that by default object names used are prefixed with
<tt>jboss.cache:service=JBossCache</tt>. While this format
* works for and is consistent with JBoss AS and the JMX console, it has been known to
cause problems with other JMX
* servers such as Websphere. To work around this, you can provide the following VM
system property to override this
* prefix with a prefix of your choice:
* <tt><b>-Djbosscache.jmx.prefix=JBossCache</b></tt>
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.CR3, 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani resolved JBCACHE-1444.
------------------------------------
Resolution: Done
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.CR3, 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:20 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Piotr Piastucki commented on JBCACHE-1444:
------------------------------------------
From my point of view the issue has not been fixed - the deployment
still fails under WL when local mode is selected, because of
private void processBaseName(ObjectName baseName)
{
...
if
(cacheSpi.getConfiguration().getCacheMode().equals(Configuration.CacheMode.LOCAL))
{
// CurrentTimeMillis is not good enaugh as an unique id generator. I am
constantly
// getting conflicts in several parallel tests on my box. Maybe some more
sofisticated
// unique id generator should be provided?
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() +
"-" + System.currentTimeMillis();
}
...
}
Obviously, no matter what is selected as prefix, thread name IS still used.
I did not find any workaround for the issue as:
1) I can properly register cache as MBean as described in user guide (correct object name
is provided by me in this case):
JmxRegistrationManager jmxManager = new JmxRegistrationManager(server,
cache, on);
jmxManager.registerAllMBeans();
BUT
2) When jmxStatistics are disabled in the config file then CacheMgmtInterceptor is not
added to interceptor chain and I cannot get any statistics.
3) Whe jmxStatistics are enabled in the config file then Jboss cache tries to register the
MBean with the default name (the one with thread name) and it fails.
Question - why the same flag controls jmx registration and interceptor chain creation??
there should be a separate attribute in jmxStatistics tag to control whether the users
whats to register the MBean automatically or do it manually later (as I try to do).
Thanks,
Piotr
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani commented on JBCACHE-1444:
----------------------------------------
Agreed that the current time in millis is poor, as is the thread name (since a single
thread is likely to be responsible for creating and registering).
What could work is to use Integer.toHexString(System.identityHashCode(objectToRegister))
after the prefix, although this would trip up if the same instance were to be registered
more than once. But IMO I think this makes sense.
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:42 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Piotr Piastucki commented on JBCACHE-1444:
------------------------------------------
Ok, but please also address the second issue.
Users should be able to instruct jboss cache to add CacheMgmtInterceptor to interceptor
chain without registering it as MBean, because they may want to register all beans
themselves. There should be a separate flag to exclude the interceptor from the chain.
Currently, the only workaround I found is as follows:
Cache cache = factory.createCache(configFileName, true);
CacheMgmtInterceptor cmi = new CacheMgmtInterceptor();
cache.addInterceptor(cmi, 0);
CacheSPI cachespi = (CacheSPI) cache;
cachespi.getComponentRegistry().registerComponent(cmi, cmi.getClass());
But I do not think users should be forced to do such hacks :)
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.0.1.GA
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani reopened JBCACHE-1444:
------------------------------------
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Priority: Critical
Fix For: 3.1.0
Original Estimate: 5 hours
Remaining Estimate: 5 hours
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani updated JBCACHE-1444:
-----------------------------------
Original Estimate: (was: 5 hours)
Remaining Estimate: (was: 5 hours)
Fix Version/s: 3.1.0
(was: 3.0.1.GA)
Priority: Major (was: Critical)
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Fix For: 3.1.0
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani commented on JBCACHE-1444:
----------------------------------------
Piotr, please see JBCACHE-1462 for your suggestion above.
I'm leaving this JIRA to focus on JMX MBean naming only.
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Fix For: 3.1.0.GA
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:35 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1444) ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due to ":" char in name.
[
https://jira.jboss.org/jira/browse/JBCACHE-1444?page=com.atlassian.jira.p...
]
Manik Surtani resolved JBCACHE-1444.
------------------------------------
Fix Version/s: 3.0.1.GA
(was: 3.1.0.GA)
Resolution: Done
ObjectName's validation fails for Jbosscache 3.0 on WAS 6.1 due
to ":" char in name.
------------------------------------------------------------------------------------
Key: JBCACHE-1444
URL: https://jira.jboss.org/jira/browse/JBCACHE-1444
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: 3.0.0.CR3, 3.0.0.GA
Environment: WAS 6.1, IBM VM
Reporter: Peter Kovgan
Assignee: Manik Surtani
Fix For: 3.0.1.GA
I deploy jboss cache on WAS 6.1(base install), and the problem is:
new JmxRegistrationManager uses this function to create unique object name:
private void processBaseName(ObjectName baseName)
in LOCAL mode, name is
objectNameBase = LOCAL_CACHE_PREFIX + Thread.currentThread().getName() + "-" +
System.currentTimeMillis();
the problem WAS returns <ContainerName>:<some number> as a
Thread.currentThread().getName().
This means you have something like WebContainer : 1 in name, but the ":" char
fails during the validation in WAS's proprietary(!!!)
javax.management.ObjectName.class.
Probably needed some configurable option that excludes ":"
Thread.currentThread().getName() - problem part - should be changed for WAS to exclude
":"
below is WAS check for invalid characters:
while ((in_index < len) && ((c1 = name_chars[in_index++]) != '='))
switch (c1) {
// '=' considered to introduce value part
case '*' :
case '?' :
case ',' :
case ':' :
case '\n' :
final String ichar = ((c1=='\n')?"\\n":""+c1);
throw new MalformedObjectNameException(
"Invalid character '" + ichar +
"' in key part of property");
default: ;
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5827
days inactive
5885
days old
jbosscache-issues@lists.jboss.org
13 comments
3 participants
participants (3)
-
Manik Surtani (JIRA) -
Peter Kovgan (JIRA)
-
Piotr Piastucki (JIRA)