[Hibernate-JIRA] Created: (HSEARCH-1026) It's impossible to expose statistics via JMX from more than one application
by Jakub Białek (JIRA)
It's impossible to expose statistics via JMX from more than one application
---------------------------------------------------------------------------
Key: HSEARCH-1026
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1026
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.4.1.Final
Environment: Hibernate 3.6.9.Final
Reporter: Jakub Białek
Deploying more than one application using hibernate search with hibernate.search.jmx_enabled=true on the same application server leads to overwrite StatisticsInfoMBean (and probably other mbeans), so exposed statistics will come only from the last deployed application.
Currently it's impossible to define name of the StatisticsInfoMBean, all created instances are always bound to StatisticsInfoMBean.STATISTICS_MBEAN_OBJECT_NAME = org.hibernate.search.jmx:type=StatisticsInfoMBean.
>From ImmutableSearchFactory:
{code}
if ( isJMXEnabled() ) {
// since the SearchFactory is mutable we might have an already existing MBean which we have to unregister first
if ( JMXRegistrar.isNameRegistered( StatisticsInfoMBean.STATISTICS_MBEAN_OBJECT_NAME ) ) {
JMXRegistrar.unRegisterMBean( StatisticsInfoMBean.STATISTICS_MBEAN_OBJECT_NAME );
}
JMXRegistrar.registerMBean(
new StatisticsInfo( statistics ), StatisticsInfoMBean.STATISTICS_MBEAN_OBJECT_NAME
);
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[Hibernate-JIRA] Created: (HSEARCH-1130) Support @Spatial without depending on the Coordinates class
by Emmanuel Bernard (JIRA)
Support @Spatial without depending on the Coordinates class
-----------------------------------------------------------
Key: HSEARCH-1130
URL: https://hibernate.onjira.com/browse/HSEARCH-1130
Project: Hibernate Search
Issue Type: New Feature
Components: query
Reporter: Emmanuel Bernard
Assignee: Nicolas Helleringer
Today, entities must depend on Coordinates (implementing or via a property returning Coordinates).
We can imagine the following
{code}
@Spatial(name=home")
class User {
@Latitude(for="home")
Double homeLatitude;
@Longitude(for="home")
Double homeLongitude;
}
Note that we will need to support @Spatials as well in this case (check AbstractDocumentBuilder initializeMemberLevelAnnotations() and checkForFields() as we will need a checkForSpatials()
This feature can wait for after the main spatial pull request
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months