[JBoss JIRA] (AS7-3559) The SSLIdentityService needs to use hasDefined instead of has when obtaining the protocol.
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-3559:
-------------------------------------
Summary: The SSLIdentityService needs to use hasDefined instead of has when obtaining the protocol.
Key: AS7-3559
URL: https://issues.jboss.org/browse/AS7-3559
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Final
The following may be the result of has returning true when a protocol is not actually defined: -
17:57:33,898 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.server.controller.management.security_realm.ManagementRealm.ssl: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.ManagementRealm.ssl: JBAS015229: Unable to start service
at org.jboss.as.domain.management.security.SSLIdentityService.start(SSLIdentityService.java:96)
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]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]
Caused by: java.security.NoSuchAlgorithmException: undefined SSLContext not available
at sun.security.jca.GetInstance.getInstance(GetInstance.java:142) [:1.6.0_30]
at javax.net.ssl.SSLContext.getInstance(SSLContext.java:125) [:1.6]
at org.jboss.as.domain.management.security.SSLIdentityService.start(SSLIdentityService.java:91)
... 5 more
--
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, 10 months
[JBoss JIRA] (AS7-2045) JdbcSQLException: "Database is already closed" on server shutdown
by Jozef Hartinger (Created) (JIRA)
JdbcSQLException: "Database is already closed" on server shutdown
-----------------------------------------------------------------
Key: AS7-2045
URL: https://issues.jboss.org/browse/AS7-2045
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.2.Final
Reporter: Jozef Hartinger
Priority: Critical
Fix For: 7.1.0.Beta1
An application that uses the "create-drop" Hibernate ddl strategy fails do undeploy properly on shutdown when a persistent (non-in-memory) database is used. Shutdown log below.
This issue is critical for the demo applications on *openshift express* (which uses persistent setup for the built-in database) where redeploy is expected to get the application to the default state.
To reproduce:
# Use the attached standalone-persistent.xml profile (the only change is redefinition of the built-in datasource URL to jdbc:h2:${jboss.server.data.dir}/test;DB_CLOSE_DELAY=-1)
# Deploy the attached application
# Start the server with the persistent profile (./standalone.sh --server-config=../standalone/configuration/standalone-persistent.xml)
# Stop the server (Ctrl+C)
# You should see the exception below
{noformat}
16:42:43,982 INFO [org.jboss.as.logging] Restored bootstrap log handlers
16:42:44,003 INFO [org.jboss.jpa] stopping Persistence Unit Service 'test.war#booking'
16:42:44,005 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] HHH00227:Running hbm2ddl schema export
16:42:44,014 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH00231:Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-145]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.message.DbException.get(DbException.java:133)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1333)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1308)
at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:364)
at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:810)
at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1567)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:295)
at org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:54)
at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:354)
at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:305)
at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:301)
at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1288)
at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:126)
at org.jboss.as.jpa.service.PersistenceUnitService.stop(PersistenceUnitService.java:88) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
16:42:44,018 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] HHH00230:Schema export complete
16:42:44,022 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
16:42:44,028 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
16:42:44,030 INFO [org.jboss.as.server.deployment] Stopped deployment test.war in 68ms
16:42:44,032 INFO [org.jboss.as] JBoss AS 7.0.2.Final "Arc" stopped in 66ms
{noformat}
--
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, 10 months
[JBoss JIRA] (AS7-3280) Dependency attribute optional="true" is ignored for deployment modules
by Robert Reimann (JIRA)
Robert Reimann created AS7-3280:
-----------------------------------
Summary: Dependency attribute optional="true" is ignored for deployment modules
Key: AS7-3280
URL: https://issues.jboss.org/browse/AS7-3280
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.0.CR1b
Reporter: Robert Reimann
Assignee: David Lloyd
Setting optional="true" on a module dependency in jboss-deployment-structure.xml is ignored. Allthough the dependency is declared as optional the dependent WAR fails when the optional dependency isn't present.
The issue is not limited to subdeployment dependencyies (as described in AS7-2832) or additional dependencies (as described in https://community.jboss.org/message/646012). Even the simple form of optional dependency inclusion fails for deployment modules:
{code:xml}
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.apache.log4j" />
<module name="deployment.not-yet-existing.jar" optional="true" />
</dependencies>
</deployment>
</jboss-deployment-structure>
{code}
{code}
07:05:02,550 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.module.spec.service."deployment.not-yet-existing.jar".main (missing)
dependents: [service jboss.deployment.unit."jboss-as-log4jdemo.war".POST_MODULE, service jboss.module.service."deployment.jboss-as-log4jdemo.war".main]
{code}
--
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, 10 months