[JBoss JIRA] Created: (JBAS-7910) jmx-console does not display CompositeData properly
by Thomas Diesler (JIRA)
jmx-console does not display CompositeData properly
---------------------------------------------------
Key: JBAS-7910
URL: https://jira.jboss.org/jira/browse/JBAS-7910
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
The JMX spec defines with Open MBean generic data transfer types that are self describing. The jmx-console should display these open types properly instead of just showing their string representation.
http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=os...
listBundles
javax.management.openmbean.TabularDataSupport(tabularType=javax.management.openmbean.TabularType(name=BUNDLES,rowType=javax.management.openmbean.CompositeType(name=BUNDLE,items=((itemName=ExportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=Fragment,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Fragments,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Headers,itemType=javax.management.openmbean.TabularType(name=HEADERS,rowType=javax.management.openmbean.CompositeType(name=HEADER,items=((itemName=Key,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=Value,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))),indexNames=(Key))),(itemName=Hosts,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Identifier,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=ImportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=LastModified,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=Location,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=PersistentlyStarted,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=RegisteredServices,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=RemovalPending,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Required,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),
...
--
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
15 years
[JBoss JIRA] Created: (EJBTHREE-1152) service-ref in ejb-jar.xml is ignored
by Thomas Diesler (JIRA)
service-ref in ejb-jar.xml is ignored
-------------------------------------
Key: EJBTHREE-1152
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1152
Project: EJB 3.0
Issue Type: Bug
Reporter: Thomas Diesler
Fix For: AS 5.0.0.Beta3
[tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
one-test:
[junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
[junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 8.761 sec
[junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
Caused by: javax.naming.NameNotFoundException: service1 not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.server.NamingServer.lookup(NamingServer.java:270)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:776)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.test.ws.jaxws.samples.serviceref.EJBClient.echo(EJBClient.java:52)
<ejb-jar version="3.0"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<enterprise-beans>
<session>
<ejb-name>EJBClient</ejb-name>
<remote>org.jboss.test.ws.jaxws.samples.serviceref.EJBRemote</remote>
<ejb-class>org.jboss.test.ws.jaxws.samples.serviceref.EJBClient</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<service-ref>
<service-ref-name>service1</service-ref-name>
<service-interface>javax.xml.ws.Service</service-interface>
<wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
<service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
</service-ref>
<service-ref>
<service-ref-name>service2</service-ref-name>
<service-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpointService</service-interface>
<wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
<service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname>
<port-component-ref>
<service-endpoint-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpoint</service-endpoint-interface>
<enable-mtom>true</enable-mtom>
</port-component-ref>
</service-ref>
</session>
</enterprise-beans>
</ejb-jar>
--
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
15 years
[JBoss JIRA] Created: (JBAS-7447) PersistentManager for sessions is broken
by Emilio Davis (JIRA)
PersistentManager for sessions is broken
----------------------------------------
Key: JBAS-7447
URL: https://jira.jboss.org/jira/browse/JBAS-7447
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-5.1.0.GA
Reporter: Emilio Davis
Assignee: Remy Maucherat
Using the following context.xml
<Context cookies="true" crossContext="true">
<Manager className="org.apache.catalina.session.PersistentManager" maxIdleSwap="1200" saveOnRestart="true">
<Store checkInterval="60" className="org.apache.catalina.session.JDBCStore" connectionURL="jdbc:mysql://localhost:3306/XXX?user=XXX&password=XXX" driverName="com.mysql.jdbc.Driver" sessionAppCol="app_name" sessionDataCol="session_data" sessionIdCol="session_id" sessionLastAccessedCol="last_access" sessionMaxInactiveCol="max_inactive" sessionTable="tomcat_sessions" sessionValidCol="valid_session"/>
</Manager>
<InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener>
</Context>
That used to work in jboss4.0.5GA and correct according to tomcat 6 documentation jboss 5.1.0GA fails to start tomcat with the following exception:
2009-11-02 23:11:54,292 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deplo
y, ctxPath=/
2009-11-02 23:11:55,619 ERROR [org.jboss.web.tomcat.service.deployers.JBossContextConfig] (main) XML
error parsing: context.xml
org.jboss.xb.binding.JBossXBException: Failed to parse source: Store not found as a child of Manager
in unordered_sequence: attributes?
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133)
at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextCo
nfig.java:573)
at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:536)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5436)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4148)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeploymen
t.java:310)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:1
42)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
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:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
at $Proxy38.start(Unknown Source)
I opened a thread in the tomcat integration forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=163337) but got no response.
--
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
15 years
[JBoss JIRA] Created: (JBRULES-2289) Support JPA Resource Local EntityTransaction based Transactions
by Michael Youngstrom (JIRA)
Support JPA Resource Local EntityTransaction based Transactions
---------------------------------------------------------------
Key: JBRULES-2289
URL: https://jira.jboss.org/jira/browse/JBRULES-2289
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.0.1.FINAL
Reporter: Michael Youngstrom
Assignee: Mark Proctor
It would be nice if wherever JPA is used in Drools (drools-flow in particular) there was support for RESOURCE_LOCAL transactions through JPA's EntityTransaction interface as an alternative to JTA.
Support for resource local transactions would reduce the base Drools Flow dependency footprint (no need for bitronix) as well as allow Drools to be used in a containerless or Tomcat like environment without a JTA implementation available. Although embeddable solutions are available they are often either buggy or complex. It would be nice to not have to deal with them if possible.
If the idea is acceptable I'd be willing to put together an initial patch.
--
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
15 years
[JBoss JIRA] Created: (JBMESSAGING-1791) ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally
by Tamas Cserveny (JIRA)
ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally
-----------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1791
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1791
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3
Environment: JBoss AS 4.2.3.GA Release (JBossESB 4.7)
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.4.0.SP3
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=4
jboss.messaging.providerIncrementingVersion=21
Reporter: Tamas Cserveny
Hi,
I found a CME in the JBoss-messageing.
Test scenario:
Vanilla JBossESB 4.7 with a simple flow. (file -> queue, bridge queue to another queue, queue -> file)
I kept this server running on a 2 core system with a load of 10 messages / sec. (ca 3kb messages).
I received many of these exception during the test. It caused some messages to stuck into the queue, but eventually they were redelivered. (Not after 5s, but after some other messages). They were counted in the 'DeliveringCount', and stayed like that.
Cheers,
Tamas
2010-02-26 00:00:50,083 ERROR [org.jboss.jms.client.container.ClientConsumer] Failed to deliver message
javax.jms.JMSException: There is no transaction with id LocalTx[m0r-676r546g-1-2tbmq36g-nq5p47-51zk6a]
at org.jboss.jms.tx.ResourceManager.addAck(ResourceManager.java:186)
at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:293)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect19.invoke(SessionAspect19.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java)
at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:152)
at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:976)
at org.jboss.messaging.util.JBMExecutor$TCLExecutor.run(JBMExecutor.java:78)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:619)
2010-02-26 00:03:22,084 ERROR [org.jboss.messaging.util.ExceptionUtil] ConnectionEndpoint[uip-txvw446g-1-2tbmq36g-nq5p47-51zk6a] sendTransaction [f6r-ghfu546g-1-2tbmq36g-nq5p47-5
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally(ServerSessionEndpoint.java:1474)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:810)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:473)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195)
--
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
15 years
[JBoss JIRA] Created: (JGRP-619) Change getState semantics
by Vladimir Blagojevic (JIRA)
Change getState semantics
-------------------------
Key: JGRP-619
URL: http://jira.jboss.com/jira/browse/JGRP-619
Project: JGroups
Issue Type: Task
Affects Versions: 2.5, 2.4, 2.3, 2.2.9
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Fix For: 3.0
Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer.
We have to simplify this process! State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener.
This issue is closely related to revamping of channel state transfer callbacks - JGRP-563
--
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
15 years