[JBoss JIRA] (WFLY-1186) Create JPA service callback for invoking database migration
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-1186:
-------------------------------
Assignee: (was: Scott Marlow)
> Create JPA service callback for invoking database migration
> -----------------------------------------------------------
>
> Key: WFLY-1186
> URL: https://issues.jboss.org/browse/WFLY-1186
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JPA / Hibernate
> Reporter: Anil Arora
>
> Looking for a simple callback/listener mechanism so that we can invoke a database migration script before JPA persistent unit starts up and runs the Hibernate schema validation mechanism.
> Ideally, there would be a property within the persistence.xml that indicates which class to call. It would also pass in/inject the datasource that is being used for the persistence unit.
> Essentially, this would solve the lack of migration support in Hibernate itself.
--
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
12 years, 6 months
[JBoss JIRA] (WFLY-711) Detect/assume duplicate instances running
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-711?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky reassigned WFLY-711:
--------------------------------------
Assignee: (was: Alexey Loubyansky)
> Detect/assume duplicate instances running
> -----------------------------------------
>
> Key: WFLY-711
> URL: https://issues.jboss.org/browse/WFLY-711
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Jim Tyrrell
> Fix For: Awaiting Volunteers
>
>
> I do like the fact that address in use do not leave a running instance laying around, I would much rather see one error message rather then pages and pages. To our users this is very overwhelming, especially when they come from our competitors. Also how does this kind of error not have an error code associated with it.
> How many other exceptions do not have error codes?
> Jim-Tyrrells-MacBook-Pro-2:bin jimtyrrell$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1
> JAVA: java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
> =========================================================================
> 08:38:37,622 INFO [org.jboss.modules] JBoss Modules version 1.0.0.CR4
> 08:38:37,772 INFO [org.jboss.msc] JBoss MSC version 1.0.0.CR2
> 08:38:37,812 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" starting
> 08:38:38,328 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
> 08:38:38,333 INFO [org.jboss.as.logging] Removing bootstrap log handlers
> 08:38:38,343 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
> 08:38:38,413 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
> 08:38:38,420 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
> 08:38:38,425 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
> 08:38:38,436 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
> 08:38:38,442 INFO [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 3.2.0.Beta2
> 08:38:38,448 INFO [org.xnio] (MSC service thread 1-10) XNIO Version 3.0.0.Beta3
> 08:38:38,457 INFO [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.0.0.Beta3
> 08:38:38,606 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
> 08:38:38,616 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-10) Starting remote JMX connector
> 08:38:38,618 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
> 08:38:38,618 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC00001: Failed to start service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [:1.6.0_24]
> at org.xnio.nio.NioXnio.createTcpServer(NioXnio.java:162)
> at org.xnio.Xnio.createStreamServer(Xnio.java:230)
> at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:162)
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:93)
> ... 5 more
> 08:38:38,623 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the URLStreamHandlerFactory
> 08:38:38,624 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the ContentHandlerFactory
> 08:38:38,625 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
> at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:89)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
> at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112)
> at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:47)
> at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:37)
> at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:126)
> at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:99)
> at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:86)
> ... 5 more
> 08:38:38,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:106)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> Caused by: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393) [:1.6.0_24]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129) [:1.6.0_24]
> at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190) [:1.6.0_24]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) [:1.6.0_24]
> at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68) [:1.6.0_24]
> at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222) [:1.6.0_24]
> at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:97)
> ... 5 more
> Caused by: java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24]
> at org.jboss.as.network.ManagedServerSocketBinding.bind(ManagedServerSocketBinding.java:73)
> at org.jboss.as.network.SocketBinding.createServerSocket(SocketBinding.java:149)
> at org.jboss.as.jmx.JMXConnectorService$JMXServerSocketFactory.createServerSocket(JMXConnectorService.java:194)
> at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299) [:1.6.0_24]
> ... 13 more
> 08:38:38,634 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190)
> at org.apache.catalina.connector.Connector.init(Connector.java:976)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> 08:38:38,636 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.initialize: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.catalina.connector.Connector.init(Connector.java:978)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> 08:38:38,638 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error starting endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
> at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:1020)
> at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:218)
> at org.apache.catalina.connector.Connector.start(Connector.java:1051)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> 08:38:38,639 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.start: LifecycleException: service.getName(): "jboss.web"; Protocol handler start failed: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.catalina.connector.Connector.start(Connector.java:1058)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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:680) [:1.6.0_24]
> 08:38:38,675 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
> 08:38:38,700 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) Bound data source [java:jboss/datasources/ExampleDS]
> 08:38:38,920 INFO [org.jboss.as.deployment] (MSC service thread 1-10) Started FileSystemDeploymentService for directory /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1/standalone/deployments
> 08:38:39,130 INFO [org.jboss.as.controller] (Controller Boot Thread) Service status report
> Services which failed to start:
> service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
> service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
> service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> 08:38:39,134 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.CR1 "White Rabbit" started (with errors) in 1668ms - Started 87 of 146 services (4 services failed or missing dependencies, 55 services are passive or on-demand)
> ^C08:39:03,929 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
> 08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
> 08:39:03,934 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" stopped in 4ms
--
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
12 years, 6 months
[JBoss JIRA] (WFLY-2644) Java heap space exceeded looping connect/disconnect cycle
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-2644?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky resolved WFLY-2644.
-------------------------------------
Resolution: Done
The CLI fix has been merged into master. Should be fixed now.
> Java heap space exceeded looping connect/disconnect cycle
> ---------------------------------------------------------
>
> Key: WFLY-2644
> URL: https://issues.jboss.org/browse/WFLY-2644
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Beta1
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Final
>
>
> CLIModelControllerClient implementation is not cleaning up something related to connection handling which leads to OOME repeating a cycle of ensureConnected(...) and close(). On my laptop it happens after around 1400 iterations.
--
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
12 years, 6 months
[JBoss JIRA] (WFLY-2684) Security Domains not accessible through web console
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFLY-2684?page=com.atlassian.jira.plugin.... ]
Heiko Braun updated WFLY-2684:
------------------------------
Summary: Security Domains not accessible through web console (was: Security Domains not accessible throught web console)
> Security Domains not accessible through web console
> ---------------------------------------------------
>
> Key: WFLY-2684
> URL: https://issues.jboss.org/browse/WFLY-2684
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Console
> Affects Versions: 8.0.0.CR1
> Environment: Linux 2.6.32-358.23.2.el6.x86_64 (CentOS 6.4) with 1.7.0_45-mockbuild_2013_10_23_08_18-b00 (OpenJDK 7) or Windows 7 64bit with Oracle Java 7
> Reporter: Marko Mrvelj
> Assignee: Heiko Braun
>
> When trying to access Security Domains under Profile/Security tree, the call blocks. Tested on CentOS 6 and Windows 7 machine, and behaviour seems to be the same. Did not see problems with other parts of web console. Also security domains seem to be working when configured from CLI.
> Also once you click on "Security Domain" the whole console stops responding to the mouse, and web refresh is needed to get it back.
> On the same (Linux) machine this works in Beta1.
--
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
12 years, 6 months