[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas updated AS7-6143:
--------------------------------
Assignee: (was: Stuart Douglas)
Fix Version/s: Open To Community
Component/s: EJB
> HiloKeygenerator not registered in JNDI
> ---------------------------------------
>
> Key: AS7-6143
> URL: https://issues.jboss.org/browse/AS7-6143
> Project: Application Server 7
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 7.1.1.Final
> Reporter: Manuel Fehlhammer
> Labels: cmp
> Fix For: Open To Community
>
>
> The HiLoKeygenerator from subsystem cmp is not registered in JNDI.
> Therefore it is not really usable.
> I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:cmp:1.0">
> <key-generators>
> <hilo name="itemidgenerator">
> <block-size>
> 10
> </block-size>
> <data-source>
> java:jboss/datasources/MySqlDS
> </data-source>
> <id-column>
> highvalue
> </id-column>
> <sequence-column>
> sequencename
> </sequence-column>
> <sequence-name>
> itemid
> </sequence-name>
> <table-name>
> HiLoSequences
> </table-name>
> </hilo>
> </key-generators>
> </subsystem>
> {code}
>
> But I do not find any JNDI registration related to this HiLoKeygenerator.
> From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas updated AS7-6143:
--------------------------------
Issue Type: Feature Request (was: Bug)
Assignee: Stuart Douglas
> HiloKeygenerator not registered in JNDI
> ---------------------------------------
>
> Key: AS7-6143
> URL: https://issues.jboss.org/browse/AS7-6143
> Project: Application Server 7
> Issue Type: Feature Request
> Affects Versions: 7.1.1.Final
> Reporter: Manuel Fehlhammer
> Assignee: Stuart Douglas
> Labels: cmp
>
> The HiLoKeygenerator from subsystem cmp is not registered in JNDI.
> Therefore it is not really usable.
> I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:cmp:1.0">
> <key-generators>
> <hilo name="itemidgenerator">
> <block-size>
> 10
> </block-size>
> <data-source>
> java:jboss/datasources/MySqlDS
> </data-source>
> <id-column>
> highvalue
> </id-column>
> <sequence-column>
> sequencename
> </sequence-column>
> <sequence-name>
> itemid
> </sequence-name>
> <table-name>
> HiLoSequences
> </table-name>
> </hilo>
> </key-generators>
> </subsystem>
> {code}
>
> But I do not find any JNDI registration related to this HiLoKeygenerator.
> From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas reopened AS7-6143:
---------------------------------
Re-opening as a feature request
> HiloKeygenerator not registered in JNDI
> ---------------------------------------
>
> Key: AS7-6143
> URL: https://issues.jboss.org/browse/AS7-6143
> Project: Application Server 7
> Issue Type: Feature Request
> Affects Versions: 7.1.1.Final
> Reporter: Manuel Fehlhammer
> Assignee: Stuart Douglas
> Labels: cmp
>
> The HiLoKeygenerator from subsystem cmp is not registered in JNDI.
> Therefore it is not really usable.
> I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:cmp:1.0">
> <key-generators>
> <hilo name="itemidgenerator">
> <block-size>
> 10
> </block-size>
> <data-source>
> java:jboss/datasources/MySqlDS
> </data-source>
> <id-column>
> highvalue
> </id-column>
> <sequence-column>
> sequencename
> </sequence-column>
> <sequence-name>
> itemid
> </sequence-name>
> <table-name>
> HiLoSequences
> </table-name>
> </hilo>
> </key-generators>
> </subsystem>
> {code}
>
> But I do not find any JNDI registration related to this HiLoKeygenerator.
> From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI
by Manuel Fehlhammer (JIRA)
[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ]
Manuel Fehlhammer commented on AS7-6143:
----------------------------------------
Thank you for your superfast reaction!
OK. Wasn't aware, that in JBOSS-AS 7 there is no intention providing the key generator as a public service.
Since I am using JPA and was using the keygenerator in JBOSS 5 for other key functionality (not entity PKs) it seems, that I have to develop my own HiLoKey-generator component.
> HiloKeygenerator not registered in JNDI
> ---------------------------------------
>
> Key: AS7-6143
> URL: https://issues.jboss.org/browse/AS7-6143
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.1.Final
> Reporter: Manuel Fehlhammer
> Labels: cmp
>
> The HiLoKeygenerator from subsystem cmp is not registered in JNDI.
> Therefore it is not really usable.
> I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:cmp:1.0">
> <key-generators>
> <hilo name="itemidgenerator">
> <block-size>
> 10
> </block-size>
> <data-source>
> java:jboss/datasources/MySqlDS
> </data-source>
> <id-column>
> highvalue
> </id-column>
> <sequence-column>
> sequencename
> </sequence-column>
> <sequence-name>
> itemid
> </sequence-name>
> <table-name>
> HiLoSequences
> </table-name>
> </hilo>
> </key-generators>
> </subsystem>
> {code}
>
> But I do not find any JNDI registration related to this HiLoKeygenerator.
> From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6137) Correct overlap in clustering logging id ranges
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-6137?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-6137:
--------------------------------
Affects Version/s: No Release
(was: 7.1.3.Final (EAP))
> Correct overlap in clustering logging id ranges
> -----------------------------------------------
>
> Key: AS7-6137
> URL: https://issues.jboss.org/browse/AS7-6137
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: No Release
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 7.2.0.Alpha1
>
>
> The following ranges are used for logging ids in the clustering subsystem:
> {noformat}
> clustering range: 10200 - 10399 (199 message ids)
> ClusteringApiLogger: 10200 range = 10, used = 2
> ClusteringApiMessages: 10210 range = 10, used = 10 (full range)
> ClusteringImplLogger: 10220 range = 20, used = 19 (almost full range)
> ClusteringImplMessages: 10240 range = 20, used = 9
> JGroupsLogger: 10260 range = 10, used = 6
> JGroupsMessages: 10270 range = 10, used = 8
> InfinispanLogger: 10280 range = 10, used = 7
> InfinispanMessages: 10290 range = 10, used = 15 (over full)
> ClusteringWebLogger: 10300 range = 10, used = 1
> ClusteringWebMessages: 10310 range = 10, used = 5
> InfinispanWebLogger: 10320 range = 10, used = 6
> InfinispanWebMessages: 10330 range = 10, used = 7
> SingletonLogger: 10340 range = 10, used = 4
> SingletonMessages: 10350 range = 10, used = 2
> EJBLogger: not assigned range = ?, used = 0
> EJBMessages: 10360 range = 10, used = 4
> -- free 10370 - 10399 --
> {noformat}
> The overlapping range between InfinispanMessages and ClusteringWebLogger needs to be rectified, as GSS uses message ids for distinct topics in knowledge databases.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6143) HiloKeygenerator not registered in JNDI
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/AS7-6143?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas resolved AS7-6143.
---------------------------------
Resolution: Rejected
Add the following into the <entity> section of your jbosscmp-jdbc.xml:
<entity-command name="key-generator">
<attribute name="key-generator-factory">itemidgenerator</attribute>
</entity-command>
This is not a public API, there are no plans to bind it to JNDI at this point.
> HiloKeygenerator not registered in JNDI
> ---------------------------------------
>
> Key: AS7-6143
> URL: https://issues.jboss.org/browse/AS7-6143
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.1.Final
> Reporter: Manuel Fehlhammer
> Labels: cmp
>
> The HiLoKeygenerator from subsystem cmp is not registered in JNDI.
> Therefore it is not really usable.
> I managed to get the service successfully started up with the following subsystem confiuration in standalone.xml:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:cmp:1.0">
> <key-generators>
> <hilo name="itemidgenerator">
> <block-size>
> 10
> </block-size>
> <data-source>
> java:jboss/datasources/MySqlDS
> </data-source>
> <id-column>
> highvalue
> </id-column>
> <sequence-column>
> sequencename
> </sequence-column>
> <sequence-name>
> itemid
> </sequence-name>
> <table-name>
> HiLoSequences
> </table-name>
> </hilo>
> </key-generators>
> </subsystem>
> {code}
>
> But I do not find any JNDI registration related to this HiLoKeygenerator.
> From JBOSS 5.x times I know that the generator was bound as "KeyGeneratorFactory" or something.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6103) ServiceModuleLoader can't properly unload module if it failed to load module due to wrong dependency
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/AS7-6103?page=com.atlassian.jira.plugin.s... ]
Chao Wang updated AS7-6103:
---------------------------
Fix Version/s: 7.2.0.CR1
> ServiceModuleLoader can't properly unload module if it failed to load module due to wrong dependency
> ----------------------------------------------------------------------------------------------------
>
> Key: AS7-6103
> URL: https://issues.jboss.org/browse/AS7-6103
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.2.0.Alpha1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Critical
> Labels: dependency, modules
> Fix For: 7.2.0.CR1
>
> Attachments: AS7-6103.patch
>
>
> ServiceModuleLoader can't properly unload module if it failed to load module due to wrong dependency.
> The codes below take care of unload operation.
> {code:title=org.jboss.as.server.moduleservice.ServiceModuleLoader.java|borderStyle=solid}
> case STOP_REQUESTED_to_STOPPING: {
> log.tracef("serviceStopping: %s", controller);
> ModuleSpec moduleSpec = this.moduleSpec;
> try {
> *Module module = loadModule(moduleSpec.getModuleIdentifier());*
> *unloadModuleLocal(module);*
> } catch (ModuleLoadException e) {
> // ignore, the module should always be already loaded by this point,
> // and if not we will only mask the true problem
> }
> // TODO: what if the service is restarted?
> controller.removeListener(this);
> break;
> }
> {code}
> The line *unloadModuleLocal(module)* can not be reached because the previous loadModule(moduleSpec.getModuleIdentifier() will throw ModuleLoadException if module has dependency problem.
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6144) Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6144?page=com.atlassian.jira.plugin.s... ]
Scott Marlow moved HIBERNATE-137 to AS7-6144:
---------------------------------------------
Project: Application Server 7 (was: Hibernate Integration)
Key: AS7-6144 (was: HIBERNATE-137)
Workflow: GIT Pull Request workflow (was: jira)
> Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6144
> URL: https://issues.jboss.org/browse/AS7-6144
> Project: Application Server 7
> Issue Type: Enhancement
> Environment: JBoss AS 7.1.2.Final, Hibernate 4.1.2.Final
> Reporter: Marek Posolda
> Assignee: Scott Marlow
>
> Normally UserTransaction is available in JBoss via JNDI lookup to "java:comp/UserTransaction" . But sometimes this approach does not work (For example if we have custom worker threads in our application or we are starting our AS7 deployment with custom MSC thread before "java:comp" context is available to JNDI)
> So it may be good to fallback to "java:jboss/UserTransaction", which is available in JBoss AS7 even from custom threads.
> Is it possible to change "org.jboss.as.jpa.hibernate4.JBossAppServerJtaPlatform" or "org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform" to have method locateUserTransaction() similar to this?:
> {code}
> public static final String AS7_NEW_UT_NAME = "java:jboss/UserTransaction";
> @Override
> protected UserTransaction locateUserTransaction() {
> try {
> return (UserTransaction) jndiService().locate(UT_NAME);
> }
> catch(JndiException jndiException) {
> return (UserTransaction) jndiService().locate(AS7_NEW_UT_NAME);
> }
> }
> {code}
--
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
13 years, 7 months
[JBoss JIRA] (AS7-6144) Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6144?page=com.atlassian.jira.plugin.s... ]
Scott Marlow updated AS7-6144:
------------------------------
Component/s: JPA / Hibernate
> Fallback for JBossAppServerJtaPlatform.locateUserTransaction() to look at "java:jboss" if "java:comp" not available
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6144
> URL: https://issues.jboss.org/browse/AS7-6144
> Project: Application Server 7
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Environment: JBoss AS 7.1.2.Final, Hibernate 4.1.2.Final
> Reporter: Marek Posolda
> Assignee: Scott Marlow
>
> Normally UserTransaction is available in JBoss via JNDI lookup to "java:comp/UserTransaction" . But sometimes this approach does not work (For example if we have custom worker threads in our application or we are starting our AS7 deployment with custom MSC thread before "java:comp" context is available to JNDI)
> So it may be good to fallback to "java:jboss/UserTransaction", which is available in JBoss AS7 even from custom threads.
> Is it possible to change "org.jboss.as.jpa.hibernate4.JBossAppServerJtaPlatform" or "org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform" to have method locateUserTransaction() similar to this?:
> {code}
> public static final String AS7_NEW_UT_NAME = "java:jboss/UserTransaction";
> @Override
> protected UserTransaction locateUserTransaction() {
> try {
> return (UserTransaction) jndiService().locate(UT_NAME);
> }
> catch(JndiException jndiException) {
> return (UserTransaction) jndiService().locate(AS7_NEW_UT_NAME);
> }
> }
> {code}
--
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
13 years, 7 months