[JBoss JIRA] Created: (JBCOMMON-114) Warning for non File URLs should also check for vfszip URLs
by Darran Lofthouse (JIRA)
Warning for non File URLs should also check for vfszip URLs
-----------------------------------------------------------
Key: JBCOMMON-114
URL: https://jira.jboss.org/browse/JBCOMMON-114
Project: JBoss Common
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Affects Versions: 2.2.17.GA
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 2.2.18.GA
Within the resolveSystemIDasURL method the following check is performed: -
if (warnOnNonFileURLs && url.getProtocol().equalsIgnoreCase("file") == false)
{
log.warn("Trying to resolve systemId as a non-file URL: " + systemId);
}
With the introduction of vfszip URLs from JBoss 5 these should also be checked and the warning skipped if it is a vfszip URL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (HIBERNATE-134) Infinispan custom cache command factory not installed error during app deployment
by Dmitry Chuiko (JIRA)
Dmitry Chuiko created HIBERNATE-134:
---------------------------------------
Summary: Infinispan custom cache command factory not installed error during app deployment
Key: HIBERNATE-134
URL: https://issues.jboss.org/browse/HIBERNATE-134
Project: Hibernate Integration
Issue Type: Bug
Environment: Ubuntu 12.04, JBoss AS 7.1.2, Hibernate 4.1.2, Infinispan 5.1.4
Reporter: Dmitry Chuiko
Assignee: Steve Ebersole
We use Infinispan as 2LC for Hibernate in a clustered configuration under JBoss 7. So {{persistence.xml}} contains the following line: {code:xml}<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.infinispan.InfinispanRegionFactory"/>{code}. The following error occurs during app deployment:
{noformat}12:04:52,859 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": org.jboss.msc.service.StartException in service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: MOYsklad] Unable to build EntityManagerFactory
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
at org.hibernate.ejb.HibernatePersistenceLognex.createContainerEntityManagerFactory(HibernatePersistenceLognex.java:16)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
Caused by: org.hibernate.cache.CacheException: Infinispan custom cache command factory not installed (possibly because the classloader where Infinispan lives couldn't find the Hibernate Infinispan cache provider)
at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCacheCommandFactory(InfinispanRegionFactory.java:500)
at org.hibernate.cache.infinispan.InfinispanRegionFactory.startRegion(InfinispanRegionFactory.java:379)
at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:212)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:347)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1741)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:93)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
... 10 more
{noformat}
This issue takes place because context {{ClassLoader}} is substituted in {{org.hibernate.ejb.Ejb3Configuration#configure}}. So Infinispan can not find {{org.infinispan.commands.module.ModuleCommandExtensions}} realization from {{hibernate-infinispan}} module in {{org.infinispan.util.ModuleProperties#loadModuleCommandHandlers}} method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-2436) clear screen doesn't work on windows 7
by Alexey Loubyansky (Created) (JIRA)
clear screen doesn't work on windows 7
--------------------------------------
Key: AS7-2436
URL: https://issues.jboss.org/browse/AS7-2436
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Following the discussion [jboss-as7-dev] AS 7.1.0 - jboss-admin : cls/clear command not working
I am using Windows 7 64 bit and it is not working.
On 31/10/2011 11:53 PM, Alexey Loubyansky wrote:
> > No, it is expected to work. It does work on linux and remember verifying
> > it on vista. CLI uses jline to manage the terminal. This is what its
> > clearScreen impl looks like
> >
> > /**
> > * Clear the screen by issuing the ANSI "clear screen" code.
> > */
> > public boolean clearScreen() throws IOException {
> > if (!terminal.isANSISupported()) {
> > return false;
> > }
> >
> > // send the ANSI code to clear the screen
> > printString(((char) 27) + "[2J");
> > flushConsole();
> >
> > // then send the ANSI code to go to position 1,1
> > printString(((char) 27) + "[1;1H");
> > flushConsole();
> >
> > redrawLine();
> >
> > return true;
> > }
> >
> > Maybe the terminal doesn't support ANSI?
> >
> > On 10/30/2011 07:35 AM, Vimal Kansal wrote:
>> >> I am using jboss-admin on windows 7 64 bit and both cls/clear are not
>> >> working : they just don't do anything. I wonder if the command is just a
>> >> place holder for now?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-5180) jaas tag for management interface does not work in domain mode
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created AS7-5180:
-----------------------------------
Summary: jaas tag for management interface does not work in domain mode
Key: AS7-5180
URL: https://issues.jboss.org/browse/AS7-5180
Project: Application Server 7
Issue Type: Bug
Components: Console, Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: Hisanobu Okuda
Assignee: Heiko Braun
I configured <jaas> for management interface in host.xml of domain mode as follow:-
{code:xml}
<security-realm name="ldap_security_realm">
<authentication>
<jaas name="managementLDAPDomain"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.native.port:9999}"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
</management>
...
(skip)
...
<subsystem xmlns="urn:jboss:domain:security:1.1">
<security-domains>
<security-domain name="managementLDAPDomain">
<authentication>
<login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required">
<module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/>
<module-option name="java.naming.provider.url" value="ldap://dhcp-107.winlab.fab.redhat.com:389"/>
<module-option name="java.naming.security.authentication" value="simple"/>
<module-option name="bindDN" value="cn=Administrator,cn=users,DC=domain1,DC=winlab,DC=fab,DC=redhat,DC=com"/>
...
{code}
But, an authentication failed and I got a message "The web console could not be loaded. Authentication required." in the console. It seems that host.xml need to have security-domain section similar to standalone.xml. "-jaas" of JVM option does not work as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months