[JBoss JIRA] Closed: (JBMESSAGING-207) HTTP invoker configuration and testing
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-207?page=all ]
Ovidiu Feodorov closed JBMESSAGING-207.
---------------------------------------
Resolution: Done
> HTTP invoker configuration and testing
> --------------------------------------
>
> Key: JBMESSAGING-207
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-207
> Project: JBoss Messaging
> Issue Type: Task
> Components: Configuration and Management
> Reporter: Ovidiu Feodorov
> Assigned To: Ron Sigal
> Priority: Blocker
> Fix For: 1.2.0.Beta1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Provide a HTTP invoker initial configuration and a working example.
> Add the example to docs/examples so it can be used as an integration test.
> Reviewed requirements:
> 1. The messaging client needs to connect to the server over HTTP
> 2. We need it implemented in such a way that there's no socket listening on the client, but the client can still receive messages asynchronously.
> 3. When the change is completed, all current Messaging functional tests, stress tests and smoke test must pass.
--
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
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3878) Attempt to deploy CMP Entity Bean without any CMP fields results in NullPointerException
by Patrick Kobly (JIRA)
Attempt to deploy CMP Entity Bean without any CMP fields results in NullPointerException
----------------------------------------------------------------------------------------
Key: JBAS-3878
URL: http://jira.jboss.com/jira/browse/JBAS-3878
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Environment: Win XP, JBoss IDE, JVM is Sun's Java_EE_sdk-5_01, MySQL 5.0.27, JBoss AS running from within Eclipse
Reporter: Patrick Kobly
Example JAR at:
http://www.kobly.com/exampleEJB.jar
Source at
http://www.kobly.com/src.zip
CMP 2.x Entity bean with no CMP fields. When an attempt to deploy is made, deploy fails with:
12:49:51,242 INFO [EjbModule] Deploying NPEEntity
12:49:51,820 WARN [ServiceController] Problem starting service jboss.j2ee:service=EjbModule,module=exampleEJB.jar
java.lang.NullPointerException
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.loadLoadGroups(JDBCEntityBridge.java:1056)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.resolveRelationships(JDBCEntityBridge.java:300)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.resolveRelationships(JDBCStoreManager.java:460)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:387)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:414)
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.GeneratedMethodAccessor5.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 $Proxy42.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662)
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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy43.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor15.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$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
12:49:51,836 INFO [EJBDeployer] Deployed: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/exampleEJB.jar
12:49:51,992 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:service=EjbModule,module=exampleEJB.jar
State: FAILED
Reason: java.lang.NullPointerException
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:service=EjbModule,module=exampleEJB.jar
State: FAILED
Reason: java.lang.NullPointerException
Same bean, with a CMP field (PK) called 'fix' added deploys successfully:
jar at
http://www.kobly.com/exampleEJB-fixed.jar
source at
http://www.kobly.com/src-fixed.zip
--
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
19 years, 8 months
[JBoss JIRA] Closed: (JBAS-1953) Installer's "all" profile missing HA classes
by Norman Richards (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1953?page=all ]
Norman Richards closed JBAS-1953.
---------------------------------
Resolution: Out of Date
> Installer's "all" profile missing HA classes
> --------------------------------------------
>
> Key: JBAS-1953
> URL: http://jira.jboss.com/jira/browse/JBAS-1953
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Ryan Campbell
> Assigned To: Norman Richards
>
> When running the ejb3 clustering tutorial against the installer's 'all" profile, I am receiving a TypeNotPresentException in my server.log
> 1. run the installer, select the "all" profile
> 2. build the ejb3 cluster tutorial "$ ant"
> 3 run the ejb3 cluster tutorial "$ ant run.stateless"
> Ant exits with the following:
> run.stateless:
> [java] Exception in thread "main" javax.naming.NameNotFoundException: org.jboss.tutorial.clustering.bean.Session not bound
> [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:491)
> [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:499)
> [java] at org.jnp.server.NamingServer.getObject(NamingServer.java:505)
> I see this in my server.log
> --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
> ObjectName: jboss.j2ee:service=EJB3,name=org.jboss.tutorial.clustering.bean.SessionBean
> State: FAILED
> Reason: java.lang.RuntimeException: java.lang.TypeNotPresentException: Type org.jboss.ha.framework.interfaces.LoadBalancePolicy not present
> ObjectName: jboss.j2ee:service=EJB3,name=org.jboss.tutorial.clustering.bean.StatefulBean
> State: FAILED
> Reason: java.lang.RuntimeException: java.lang.TypeNotPresentException: Type org.jboss.ha.framework.interfaces.LoadBalancePolicy not present
--
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
19 years, 8 months
[JBoss JIRA] Commented: (JBMESSAGING-264) Provide a mechanism to forward messages from one destination to another automatically
by Colin Stefani (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-264?page=comments#action_12... ]
Colin Stefani commented on JBMESSAGING-264:
-------------------------------------------
This is a feature that is crucial to my operations as a JMS user and it one thing keeping me off of many JMS implementations. As a result we use Tibco EMS which has a feature called "bridging" (aka message bridge as noted by Tim Fox). This is a VERY high performance internal replicator of messages between topics and/or queues or vice versa. One important element of this is to be able to apply a selector or filter on the bridge (much like one might do on a client connection to filter messages). This would allow the admin or developer creating the bridge to narrowly select the messages with the matching filter properties to deliver messages to a destination w/o having to write an elaborate external bridge piece of software. Speed is critical in this as it should be considered almost like the producer of the message is delivering the message to both locations. Tibco EMS seems to be able to produce an "OnMessage" event to clients in both the original target queue or topic and the bridged queue or topic in nearly the same timeframe.
Don't know if this will help when you get to this feature, but I've been keeping my eye on it from afar and if had my $0.02, I'd say worry less about the bridges to external destinations but instead focus on a feature for internal bridges first. For external or remote destination message delivery, I would treat those as a clients and create a routing mechanism that's not as "real-time" as a bridge would be.
> Provide a mechanism to forward messages from one destination to another automatically
> -------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-264
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-264
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Chris DeLashmutt
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.0.Beta1
>
>
> I have had requests for this feature many times. Basically, people seem to want to be able to have a component in messaging that will automatically forward messages to another destination. This destination could be in the same messaging server or some remote destination. I'm thinking that the process must either be a daemon or an MDB, and since JBossMsg will also be available standalone I'm thinking we make it an MBean. Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet (to make the pop and the push transactional).
--
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
19 years, 8 months
[JBoss JIRA] Closed: (JBAS-2598) [PerTxEntityInstanceCache] Unable to passivate due to ctx lock
by Alexey Loubyansky (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2598?page=all ]
Alexey Loubyansky closed JBAS-2598.
-----------------------------------
Resolution: Out of Date
Assignee: Alexey Loubyansky
This was fixed as part of
http://jira.jboss.com/jira/browse/JBAS-979
> [PerTxEntityInstanceCache] Unable to passivate due to ctx lock
> --------------------------------------------------------------
>
> Key: JBAS-2598
> URL: http://jira.jboss.com/jira/browse/JBAS-2598
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: Linux kos 2.6.14-archck5 #3 SMP PREEMPT Wed Dec 21 03:25:49 MSK 2005 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
> java version "1.5.0_05"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)
> Java HotSpot(TM) Server VM (build 1.5.0_05-b05, mixed mode)
> Reporter: Konstantin Sobolev
> Assigned To: Alexey Loubyansky
> Priority: Minor
>
> I'm getting lots of
> [PerTxEntityInstanceCache] Unable to passivate due to ctx lock
> warnings. I'm calling instance per transaction BMP entity bean without a transaction context, by default it has a commit option C (there's no warnings if using B). Right after bean method invocation JBoss tries to passivate the instance, but fails because enterprise context is still locked, thus a perfectly valid(?) code generates lots of warnings.
> My code looks like this (schematically):
> MyInstancePerTransactionBean bean = home.findByPrimaryKey(...);
> bean.method1(); //here we get passivation failure warning
> bean.method2(); //and another one here
> Call trace to the point where passivation fails:
> at org.jboss.ejb.plugins.PerTxEntityInstanceCache.canPassivate(PerTxEntityInstanceCache.java:181) <-- returns false
> at org.jboss.ejb.plugins.PerTxEntityInstanceCache.tryToPassivate(PerTxEntityInstanceCache.java:152)
> at org.jboss.ejb.plugins.PerTxEntityInstanceCache.release(PerTxEntityInstanceCache.java:94)
> at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:364)
> at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:149)
> at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:111)
> at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:261)
> at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:89)
> at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:53)
> at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
> at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
> at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:363)
> at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
> at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:153)
> at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
> at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
> at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:514)
> at org.jboss.ejb.Container.invoke(Container.java:873)
> at sun.reflect.GeneratedMethodAccessor104.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:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:155)
> at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104)
> at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165)
> at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
> at org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:97)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
> at $Proxy1264.getHierarchyName(Unknown Source)
> at com.supportwizard.swgroups.SWGroupsBean.ejbFindByName(SWGroupsBean.java:915)me(SWGroupsBean.java:915)
>
> Here SWGroupsBean is an ordinary BMP bean, it's ejbFindByName method contains the code snippet shown above (method1 being getHierarchyName). As I said ctx is locked, so PerTxEntityInstanceCache.canPassivate returns false and we get a warning.
--
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
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3876) Undeploying EJB application leaves trace of EJB - Mbeans
by Amit Bhayani (JIRA)
Undeploying EJB application leaves trace of EJB - Mbeans
--------------------------------------------------------
Key: JBAS-3876
URL: http://jira.jboss.com/jira/browse/JBAS-3876
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Console
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.5.CR1, JBossAS-4.0.4.GA
Reporter: Amit Bhayani
Assigned To: Darran Lofthouse
1) Copy sample.ear attached with this JIRA to jboss-4.0.x\server\default\deploy
2) Start the server
3) After completing the startup un-deploy the sample.ear (delete the .ear from deploy directory)
4) Access web-console and you will see that web-console is still trying to search the application that is already un-deployed
09:59:35,947 ERROR [STDERR] javax.management.InstanceNotFoundException: jboss.management.local:J2EEApplication=sample.ea
r,J2EEServer=Local,j2eeType=EJBModule,name=securitysample.jar is not registered.
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:666)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDeployedObjects(JSR77Lister.java:188)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createServer(JSR77Lister.java:215)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createServers(JSR77Lister.java:239)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDomain(JSR77Lister.java:254)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.createDomains(JSR77Lister.java:286)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.JSR77Lister.getTreeForResource(JSR77Lister.java:312)
09:59:35,947 ERROR [STDERR] at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(Abstrac
tPluginWrapper.java:215)
09:59:35,947 ERROR [STDERR] at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:406)
09:59:35,947 ERROR [STDERR] at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:206)
09:59:35,947 ERROR [STDERR] at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Objec
t;)Ljava.lang.Object;(Unknown Source)
09:59:35,947 ERROR [STDERR] at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Obj
ect;(Unknown Source)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
09:59:35,947 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
09:59:35,947 ERROR [STDERR] at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:105)
09:59:35,947 ERROR [STDERR] at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:148)
09:59:35,947 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
09:59:35,947 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCha
in.java:252)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
173)
09:59:35,947 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCha
in.java:202)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
173)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
09:59:35,947 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
--
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
19 years, 8 months
[JBoss JIRA] Created: (JBFORUMS-143) jboss-security.xml is not properly parsed when using JDK 1.4.2
by Ryszard Kozmik (JIRA)
jboss-security.xml is not properly parsed when using JDK 1.4.2
--------------------------------------------------------------
Key: JBFORUMS-143
URL: http://jira.jboss.com/jira/browse/JBFORUMS-143
Project: JBoss Forums
Issue Type: Bug
Environment: JBoss AS 4.0.4 GA
JBoss Portal 2.4 GA
jboss-forums-1.0.0Alpha-P2.4
JRE 1.4
Oracle 9i DB
Windows
Reporter: Ryszard Kozmik
Assigned To: Ryszard Kozmik
Fix For: 1.0.0 Beta
It seems that when someone uses JDK 1.4.2 then jboss-service.xml of JBoss Forums is not parsed properly.
org.jboss.deployment.DeploymentException: Error parsing the XML file: ; - nested throwable: (org.jboss.mx.util.JBossNotCompliantMBeanException: Error parsing the XML file: )
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
--
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
19 years, 8 months
