[JBoss JIRA] Created: (JBPORTAL-2246) Portlet invoker exception during portlet window rendering
by Prabhat Jha (JIRA)
Portlet invoker exception during portlet window rendering
----------------------------------------------------------
Key: JBPORTAL-2246
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2246
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Portlet
Affects Versions: 2.7.0 Final
Reporter: Prabhat Jha
Assignee: Thomas Heute
Priority: Critical
Fix For: 2.7.1 Final
Please see related comment at https://jira.jboss.org/jira/browse/JBEPP-12.
JBoss] 13:09:48,658 ERROR [InternalPortletContentProvider] Portlet invoker exception during portlet window rendering
[JBoss] java.lang.IllegalStateException: No next invoker
[JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.safeGetNext(PortletInvokerInterceptor.java:123)
[JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82)
[JBoss] at org.jboss.portal.portlet.management.PortletContainerManagementInterceptorImpl.invoke(PortletContainerManagementInterceptorImpl.java:59)
[JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82)
[JBoss] at org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor.invoke(PortalSessionSynchronizationInterceptor.java:93)
[JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82)
--
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, 9 months
[JBoss JIRA] Created: (JBAS-6711) if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
by Ian Springer (JIRA)
if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6711
URL: https://jira.jboss.org/jira/browse/JBAS-6711
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
For example, I pass the following template, which has a non-null but valid value set for the "DLQ" prop:
Properties for DeploymentTemplateInfo [QueueTemplate]:
name=DLQ, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items=[name=
domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging.destination,keyP
ropertyList={service=Queue, name=DLQ }]
name=JNDIName, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:java.lang.String:rrr
name=clustered, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:boolean:true
name=downCacheSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=expiryQueue, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
name=fullSize, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:int:75000
name=maxDeliveryAttempts, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=maxSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=messageCounterHistoryDayLimit, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=pageSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=redeliveryDelay, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=securityConfig, viewUse=CONFIGURATION, mandatory=false, type=MutableCompositeMetaType, value= <<<null>>>
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
And here's the stack trace of the IAE that applyTemplate() throws:
11:04:25,156 ERROR [ApplicationServerComponent] Unable to apply template [QueueTemplate] to create ManagedComponent of type ComponentType{type=JMSDestination, s
ubtype=Queue}.
java.lang.IllegalArgumentException: Not handled value: CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items=[name=domai
n type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging.destination,keyProper
tyList={service=Queue, name=DLQ }]
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.writeTemplate(JmsDestinationTemplate.java:158)
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.applyTemplate(JmsDestinationTemplate.java:96)
at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:90)
at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1017)
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.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
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, 9 months
[JBoss JIRA] Created: (JBAS-6671) on Connection Factory components, jndi-name, rar-name, and connection-definition ManagedPropertys should all be mandatory, in both templates and properties on existing components
by Ian Springer (JIRA)
on Connection Factory components, jndi-name, rar-name, and connection-definition ManagedPropertys should all be mandatory, in both templates and properties on existing components
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6671
URL: https://jira.jboss.org/jira/browse/JBAS-6671
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
When creating or updating a ConnectionFactory component, when the jndi-name prop is not specified, I get:
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/notx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null text
when the rar-name prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null name
and when the connection-definition prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: ConnectionDefinition 'null' not found in rar 'null'
which tells me all three of these props are required, so prop.isMandatory() should return true, but it currently returns false. It should return true for both CF templates and existing CF components.
Not directly related to management, but all three of the above error messages could also be significantly improved, e.g.:
The "jndi-name" property was not specified for connection factory "FooBar" - this property is required.
The "rar-name" property was not specified for connection factory "FooBar" - this property is required.
The "connection-definition" property was not specified for connection factory "FooBar" - this property is required.
--
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, 9 months
[JBoss JIRA] Created: (JGRP-911) STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
by Bela Ban (JIRA)
STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
--------------------------------------------------------------------------------
Key: JGRP-911
URL: https://jira.jboss.org/jira/browse/JGRP-911
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
We currently use TCP server and client sockets to transfer state with STREAMING_STATE_TRANSFER. Add an option to use the default transport (could be TCP, could be UDP).
State provider:
- Write state into an output stream
- The output stream generates unicast messages of a fixed size and sends them to the state receiver
State receiver:
- Provides an input stream
- The app reads data off of that stream
- The received message chunks are placed into the input stream
Might be more firewall friendly and causes less config overhead (e.g. punching of holes for the TCP conn in the FW).
--
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, 9 months
[JBoss JIRA] Created: (JBAS-6682) StringIndexOutOfBoundsException in JvmRouteValve
by Brian Stansberry (JIRA)
StringIndexOutOfBoundsException in JvmRouteValve
------------------------------------------------
Key: JBAS-6682
URL: https://jira.jboss.org/jira/browse/JBAS-6682
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-5.1.0.Beta1
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.1.0.CR1
Saw this while testing mod_cluster:
2009-03-26 03:39:08,718 ERROR [org.apache.catalina.connector.CoyoteAdapter] (ajp-192.168.2.2-8009-5) An exception or error occurred in the container during the request processing
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1938)
at org.jboss.web.tomcat.service.session.JvmRouteValve.handleJvmRoute(JvmRouteValve.java:192)
at org.jboss.web.tomcat.service.session.JvmRouteValve.checkJvmRoute(JvmRouteValve.java:117)
at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:84)
at org.jboss.web.tomcat.service.session.LockingValve.invoke(LockingValve.java:62)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436)
at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
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, 9 months