[JBoss JIRA] Created: (JBAS-7202) Runtime shutdown hook called, forceHalt: true
by devarshi pathak (JIRA)
Runtime shutdown hook called, forceHalt: true
---------------------------------------------
Key: JBAS-7202
URL: https://jira.jboss.org/jira/browse/JBAS-7202
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Hibernate service
Affects Versions: JBossAS-4.0.5.GA
Environment: Production
Reporter: devarshi pathak
Assignee: Steve Ebersole
Priority: Critical
2009-08-21 17:25:29,076 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
2009-08-21 17:25:29,076 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
2009-08-21 17:25:30,832 INFO [org.hibernate.impl.SessionFactoryImpl] closing
2009-08-21 17:25:30,852 INFO [org.hibernate.jmx.HibernateServiceMBean] stopping service
2009-08-21 17:25:30,852 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{}
2009-08-21 17:25:30,852 DEBUG [org.hibernate.impl.SessionFactoryObjectFactory] JNDI lookup: hibernate/EntityRankFactory
2009-08-21 17:25:30,852 DEBUG [org.hibernate.impl.SessionFactoryObjectFactory] lookup: uid=c4d7bb3f233e038d01233e038e730000
2009-08-21 17:25:30,852 INFO [org.hibernate.impl.SessionFactoryImpl] closing
2009-08-21 17:25:30,852 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Unbinding factory from JNDI name: java:hibernate/EntityRankFactory
2009-08-21 17:25:30,852 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{}
2009-08-21 17:25:30,853 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Unbound factory from JNDI name: java:hibernate/EntityRankFactory
2009-08-21 17:25:30,901 INFO [org.apache.coyote.http11.Http11BaseProtocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-8080
2009-08-21 17:25:31,909 INFO [org.apache.coyote.http11.Http11BaseProtocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8080
2009-08-21 17:25:33,332 INFO [org.jboss.system.server.Server] Shutdown complete
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-3405) Unable to secure JMX Invoker
by amdonov (JIRA)
Unable to secure JMX Invoker
----------------------------
Key: JBAS-3405
URL: http://jira.jboss.com/jira/browse/JBAS-3405
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.3 SP1
Environment: Windows Sun JDK 1.5
Reporter: amdonov
I am having the same problem securing the JMX invoker as the user in the referenced forum thread. However, I'm running 4.0.4.GA instead of 4.0.3 SP1. When, performing a clean installation using the installer. I selected the default configuration and elected to secure the invokers. The install completes without error. JBoss has the following error which is unfortunatly only written at the DEBUG level.
2006-07-20 10:40:47,541 DEBUG [org.jboss.mx.modelmbean.ModelMBeanInvoker] Failed to invoke ctor(MBeanInvoker) for: class org.jboss.jmx.connector.invoker.AuthenticationInterceptor
java.lang.NoSuchMethodException: org.jboss.jmx.connector.invoker.AuthenticationInterceptor.<init>(org.jboss.mx.server.MBeanInvoker)
at java.lang.Class.getConstructor0(Class.java:2647)
at java.lang.Class.getConstructor(Class.java:1629)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.getInterceptors(ModelMBeanInvoker.java:739)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.configureInterceptorStack(ModelMBeanInvoker.java:678)
at org.jboss.mx.modelmbean.XMBean.configureInterceptorStack(XMBean.java:400)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.init(ModelMBeanInvoker.java:504)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:486)
at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:211)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:181)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
2006-07-20 10:40:47,551 DEBUG [org.jboss.system.ServiceCreator] Created bean:
Access to the adaptors is not restricted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Assigned: (JBAS-1863) Add DSTOOL (Contributed Code) to help users prepare and test datasources
by Dimitris Andreadis (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-1863?page=com.atlassian.jira.plug... ]
Dimitris Andreadis reassigned JBAS-1863:
----------------------------------------
Assignee: Jesper Pedersen
Assign to Jesper to review, at some point.
> Add DSTOOL (Contributed Code) to help users prepare and test datasources
> ------------------------------------------------------------------------
>
> Key: JBAS-1863
> URL: https://jira.jboss.org/jira/browse/JBAS-1863
> Project: JBoss Application Server
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.2 Final
> Environment: All platforms (same contributed web app/war file works in all versions)
> Reporter: James Ross
> Assignee: Jesper Pedersen
> Priority: Minor
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The dstool.war (source included) file has been provided to Ivelin Ivanov via email - I don't know how to attach it here. You can contact me at jdross(a)co.pinellas.fl.us for a resubmittal of the code.
> Here's the details I provided Ivelin:
> All our application code at Pinellas County, Floriday is based on fast J2C connection-pooled datasource database interaction. One of the items we really had to overcome with the "vanilla" JBoss was the exposed passwords. In the JBoss training class, our people learned JBoss' technique for using the login-config.xml file to create encoded authentication entries, in conjunction with the datasource entry in the oracle-ds.xml file. But its really a pain to futz all that together. The other problem with datasources - on any ap server is figuring out if they work after you set them up -- if it doesn't work, is the problem the application code not calling the datasource correctly, or the oracle-ds.xml entry, or the login-config.xml entry, or a bad password -- the list is endless - and JBoss doesn't provide a nice way to test the configuration.
> So over the Memorial Day Holiday, we created the Datasource Tools Web App. Its all in the dstool.war file, attached (unfortunately not attached on this form, cause I don't know how - but available from jdross(a)co.pinellas.fl.us or from Ivelin). It creates the application-policy stanza for the login-config.xml file, and the local-tx-datasource stanza for the xxx-ds.xml file - all based on some simple entries on a web form. It doesn't modify the files - it just creates the entries for you to cut-and-paste into the files - that way its non-interfering, and requires no setup to find the files.
> Then, after you setup the the datasource, the Tools Web App provides a really simple means of testing the datasource - and timing its performance.
> Our interest is primarily in Oracle and MySQL, but to make the tool more general, I've expanded it to also include setup and testing for DB2, HSQL, Postgres, and MS SQL Server. JBoss provides information on 34 different databases (counting the XA variants) - if you find this tool of use, I can expand it to prep/test for the other 28 databases - expansion is just a matter of adding entries to the pcg.dstools.DsDefs.java file - but it would be helpful to have someone at JBoss check it.
> But first, let me know if there's any interest at all in including this tool with the JBoss distro. No doubt, you have bigger plans for the future in the way of a Datasource Console - but for now, a simple tool makes life a lot easier.
> To look at it, just drop the attached dstool.war file (provided to Ivelin) into JBOSS_HOME/server/default/deploy
> then go to:
> http://localhost:8080/dstool
> You can run through the tool whether or not you have any datasources defined on the system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBMETA-220) Support JAXB style programming for RAR module
by Jesper Pedersen (JIRA)
Support JAXB style programming for RAR module
---------------------------------------------
Key: JBMETA-220
URL: https://jira.jboss.org/jira/browse/JBMETA-220
Project: JBoss Metadata
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Jesper Pedersen
Assignee: Jeff Zhang
Fix For: 2.0.0.CR1
Currently we have standard get- and set- methods, like
@XmlElement(name="outbound-resourceadapter")
public void setOutboundRa(OutboundRaMetaData outboundRa) {
this.outboundRa = outboundRa;
}
public OutboundRaMetaData getOutboundRa() {
return outboundRa;
}
We should support a JAXB style programming in the RAR module, and thereby creating any objects or lists that doesn't exists in the get-method, like
@XmlElement(name="outbound-resourceadapter")
public void setOutboundRa(OutboundRaMetaData outboundRa) {
this.outboundRa = outboundRa;
}
public OutboundRaMetaData getOutboundRa() {
if (outboundRa == null)
outboundRa = new OutboundRa();
return outboundRa;
}
This will allow an easier merging between the annotation model and the XML model.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Assigned: (JBAS-1436) Improved management
by Dimitris Andreadis (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-1436?page=com.atlassian.jira.plug... ]
Dimitris Andreadis reassigned JBAS-1436:
----------------------------------------
Assignee: Jesper Pedersen (was: Vicky Kak)
Give back to JCA lead for review.
> Improved management
> -------------------
>
> Key: JBAS-1436
> URL: https://jira.jboss.org/jira/browse/JBAS-1436
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Adrian Brock
> Assignee: Jesper Pedersen
> Fix For: JBossAS-6.0.0.Alpha1
>
>
> Forum Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48682
> **This is a holder issue. Each section should be raised as a new issue as it is
> developed with a link from this issue.**
> There are a number of areas in JCA that need better management capabilities.
> Some of these stats may also reveal the need for new configuration/tuning parameters.
> In core JCA:
> 1) Better visibility on the ManagedConnectionFactory.
> This is currently a DynamicMBean that provides basic config parameters, but we could also
> provide a proxy/wrapper to provide statistics of operations on the factory and its
> ManagedConnections.
> a) createManagedConnections
> b) matchManagedConnections
> c) events on from the listeners
> 2) Better visibility of the Pool(s)
> Only top level statistics are provided (you cannot see the subpools).
> The statistics are also not synchronized with the pool (for performance reasons
> and also the fact that each stat is retrieved on individual MBean getAttribute requests)
> Additional statistics could include wait times when requests are waiting on an empty pool,
> idle time of unused connections, etc.
> 3) Better visibility of the ConnectionManager
> Currently this has no visibility for management.
> Its main responsibilties are transactions enlistment and security.
> e.g. This could show how long is wasted because <track-connection-by-tx/> does not
> return the connection the pool until transaction completion.
> 4) JDBC resource adapter
> PreparedStatementCache stats
> Query time stats
> etc.
> 5) JMS resource adapter
> Message send/receive stats
> 6) Inbound messaging
> Stats for message delivery
> 7) Transaction inflow
> Stats for transaction inflow and also display a list of current inbound transactions
> 8) Work management
> Stats for the work management pools and timers
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months