[JBoss JIRA] Created: (EJBTHREE-1018) ClassCastException on concurrent EJB3 method invocation from different beans
by Michael Pfeiffer (JIRA)
ClassCastException on concurrent EJB3 method invocation from different beans
----------------------------------------------------------------------------
Key: EJBTHREE-1018
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1018
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA
Environment: Java: JDK 1.5.0_11
Eclipse: SDK 3.2.2
Reporter: Michael Pfeiffer
Two different EJB3 stateless session beans A and B packaged into separate EAR files deployed on the same JBoss instance
invoke a method of another stateless session bean C on another JBoss instance that returns an object of a user
defined class Value.
There seems to be a multi-threading issue.
Sometimes when both beans concurrently call the method of C an ClassCastException Value is thrown within the remote
interface proxy before the result object is returned to the calling bean.
The class Value and the remote interface for C are packaged into a JAR file within each EAR file inside a "lib" folder.
If this JAR file is deployed instead and not packaged into the EAR files of bean A and B everything works fine.
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-4621) error deploying admin-consoles in deploy is a link
by davide pasinato (JIRA)
error deploying admin-consoles in deploy is a link
--------------------------------------------------
Key: JBAS-4621
URL: http://jira.jboss.com/jira/browse/JBAS-4621
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Console
Affects Versions: JBossAS-4.2.1.GA
Environment: linux RH-4 Sun jdk 1.5 jboss 4.2.1 server: all with jbossws-2.0.1
Reporter: davide pasinato
Assigned To: Darran Lofthouse
Priority: Minor
I have a cluster of two jboss 4.2.1 servers. They run on the same machine. For this reason the server B links the directories deploy and lib of the server A when I start server A everything run smoothly. When I start server B I get an exception deploying the administration consoles. Looks like the directory management doesnt like symbolic links.
This is the exception I get on server B (the root directory of server B is /var/opt/jboss/stress1b):
org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@e5f0d2 on mbean jboss.admin:service=DeploymentFileRepository; - nested throwable: (java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b')
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
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.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
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 $Proxy9.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.GeneratedMethodAccessor4.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.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.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:508)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b'
at org.jboss.console.manager.DeploymentFileRepository.getFile(DeploymentFileRepository.java:151)
at org.jboss.console.manager.DeploymentFileRepository.setBaseDir(DeploymentFileRepository.java:124)
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.AttributeDispatcher.invoke(AttributeDispatcher.java:136)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103)
at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461)
at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608)
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:694)
... 84 more
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-4246) JBoss logo not displayed for web status when accessed from web console
by Stephen Burdeau (JIRA)
JBoss logo not displayed for web status when accessed from web console
----------------------------------------------------------------------
Key: JBAS-4246
URL: http://jira.jboss.com/jira/browse/JBAS-4246
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Console
Affects Versions: JBossAS-4.0.5.GA
Environment: Found on Windows XP; should exist everywhere.
Reporter: Stephen Burdeau
Assigned To: Darran Lofthouse
This is a minor issue to be sure.
Run web console and navigate to Monitoring - Web Status - Connector scoreboard in the left frame. The right frame displays the Tomcat status, but it does not include the JBoss logo on the top and it does not use the JBoss style sheet.
Navigating to Monitoring - Web Status - Full status also shows the same problem.
When accessing the same Tomcat status pages from the main page (e.g., http://localhost:8080), this problem does not occur.
It appears that logo.gif and jboss.css are located in the "root" directory for Tomcat. However, for the web console, logo.gif is located in the "images" subdirectory and jboss.css is located in the "css" subdirectory, so they are not found when using the web console.
An easy workaround is to copy the files logo.gif and jboss.css into the directory deploy/management/console-mgr.sar/web-console.war.
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBPORTAL-983) Upload of large files fails.
by Peter Johnson (JIRA)
Upload of large files fails.
----------------------------
Key: JBPORTAL-983
URL: http://jira.jboss.com/jira/browse/JBPORTAL-983
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Environment: Windows XP, JDK 1.5, JBoss AS 4.0.4GA
Reporter: Peter Johnson
Fix For: 2.4 Final
Using the CMS Admin portlet, I attempted to upload a zip file into a directory, as per section 3.2.9 of the User Guide. Initially I tried a zip ofabout 6MB containing many files, and eventually got down to a a zip file of about 500M with only a single Word document inside. The upload failed and an "SQLException: could not reset reader" error appeared (see forum post for stack trace).
I am, however, able to upload very small zip files.
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-4734) Flush failures on MuxChannel connection
by Brian Stansberry (JIRA)
Flush failures on MuxChannel connection
---------------------------------------
Key: JBAS-4734
URL: http://jira.jboss.com/jira/browse/JBAS-4734
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Vladimir Blagojevic
Fix For: JBossAS-5.0.0.CR1
Getting WARN messages about startFlush failures when multiplexed channels connect:
2007-09-18 03:04:02,936 WARN [org.jboss.ha.framework.server.JChannelFactory] Flush failed at 127.0.0.1:51382 DefaultPartition-SFSBCache
Adrian took a thread dump before one of those was logged and saw:
"main" prio=1 tid=0x80cbdfa0 nid=0x2847 in Object.wait() [0x804d2000..0x804d5130]
at java.lang.Object.wait(Native Method)
- waiting on <0xaf1e6838> (a org.jgroups.util.Promise)
at org.jgroups.util.Promise.doWait(Promise.java:104)
at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:60)
at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:28)
- locked <0xaf1e6838> (a org.jgroups.util.Promise)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:207)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229)
at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339)
at org.jgroups.JChannel.downcall(JChannel.java:1240)
at org.jgroups.JChannel.startFlush(JChannel.java:1504)
at org.jgroups.JChannelFactory.connect(JChannelFactory.java:364)
- locked <0xade09c70> (a org.jgroups.JChannelFactory$Entry)
I'll attach a server.log file from a hudson run that shows a bunch of these. Look at lines 4153-4193 for the first one, where the underlying JChannel connection happens.
I'm not seeing these on my local system.
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-4911) MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
by Luc Texier (JIRA)
MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
--------------------------------------------------------------------------------
Key: JBAS-4911
URL: http://jira.jboss.com/jira/browse/JBAS-4911
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA
Reporter: Luc Texier
Assigned To: Weston Price
After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource
<datasources>
<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<user-name>sa</user-name>
<password>jboss</password>
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
during start-up, the following exception is throwed
2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection@9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
--
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
16 years, 7 months
[JBoss JIRA] Created: (JBAS-4388) Place all management web applications, web invokers, etc under a common context root
by Jeff Schnitzer (JIRA)
Place all management web applications, web invokers, etc under a common context root
------------------------------------------------------------------------------------
Key: JBAS-4388
URL: http://jira.jboss.com/jira/browse/JBAS-4388
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web Console
Reporter: Jeff Schnitzer
Assigned To: Darran Lofthouse
In any enterprise environment, administrative interfaces are blocked from the public even if they require a password; administrative interfaces can only be accessed through the internal network or a SSL-secured VPN. This means the load balancer (or whatever) must block out all the possible management/invocation web apps:
/jmx-console
/web-console
/invoker
/jbossmq-httpil
These paths sometimes change between JBoss versions without any significant announcement, plus services are occasionally added. This could easily result in unsecured or poorly secured (basic auth) services exposed to the public.
Please put all JBoss-provided webapps under a base context that can easily be blocked to the public:
/jboss/jmx-console
/jboss/web-console
/jboss/invoker
/jboss/jbossmq-httpil
--
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
16 years, 7 months