[JBoss JIRA] Created: (JBAS-4232) Start up error when installed in path with spaces
by Dimitris Andreadis (JIRA)
Start up error when installed in path with spaces
-------------------------------------------------
Key: JBAS-4232
URL: http://jira.jboss.com/jira/browse/JBAS-4232
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.0.CR1
Environment: Windows
Reporter: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA
08:53:57,191 INFO [Server] Starting JBoss (MX MicroKernel)...
08:53:57,191 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200703051212)
08:53:57,191 INFO [Server] Home Dir: C:\Program Files\jboss-4.2.0.CR1
08:53:57,191 INFO [Server] Home URL: file:/C:/Program Files/jboss-4.2.0.CR1/
08:53:57,191 INFO [Server] Patch URL: null
08:53:57,191 INFO [Server] Server Name: default
08:53:57,191 INFO [Server] Server Home Dir: C:\Program Files\jboss-4.2.0.CR1\server\default
08:53:57,191 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-4.2.0.CR1/server/default/
08:53:57,191 INFO [Server] Server Log Dir: C:\Program Files\jboss-4.2.0.CR1\server\default\log
08:53:57,191 INFO [Server] Server Temp Dir: C:\Program Files\jboss-4.2.0.CR1\server\default\tmp
08:53:57,191 INFO [Server] Root Deployment Filename: jboss-service.xml
08:53:57,426 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
08:53:57,426 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc.
08:53:57,426 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
08:53:57,754 INFO [Server] Core system initialized
08:53:59,441 INFO [WebService] Using RMI server codebase: http://localhost:8083/
08:53:59,441 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
08:53:59,785 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
08:53:59,785 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
08:53:59,925 INFO [TransactionManagerService] Starting recovery manager
08:53:59,988 INFO [TransactionManagerService] Recovery manager started
08:53:59,988 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
08:54:02,050 INFO [EJB3Deployer] Starting java:comp multiplexer
08:54:02,425 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.2.0.CR1/server/default
/deploy/jbossws.sar/
org.jboss.deployment.DeploymentException: exception in init of file:/C:/Program Files/jboss-4.2.0.CR1/server/default/dep
loy/jbossws.sar/jaxb-api.jar; - nested throwable: (java.lang.RuntimeException: Not a valid URL: file:/C:/Program Files/j
boss-4.2.0.CR1/server/default/deploy/jbossws.sar/jaxb-api.jar)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:901)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
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:597)
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:26
3)
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.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.GeneratedMethodAccessor9.invoke(Unknown Source)
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: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:597)
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:499)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Not a valid URL: file:/C:/Program Files/jboss-4.2.0.CR1/server/default/deploy/jbo
ssws.sar/jaxb-api.jar
at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48)
at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57)
at org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation(EJB3Deployer.java:203)
at org.jboss.ejb3.EJB3Deployer.accepts(EJB3Deployer.java:265)
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: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.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 $Proxy34.accepts(Unknown Source)
at org.jboss.deployment.MainDeployer.findDeployer(MainDeployer.java:1078)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:857)
... 68 more
Caused by: java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/jboss-4.2.0.CR1/se
rver/default/deploy/jbossws.sar/jaxb-api.jar
at java.net.URI$Parser.fail(URI.java:2809)
at java.net.URI$Parser.checkChars(URI.java:2982)
at java.net.URI$Parser.parseHierarchical(URI.java:3066)
at java.net.URI$Parser.parse(URI.java:3014)
at java.net.URI.(URI.java:578)
at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:44)
... 88 more
08:54:03,112 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0\bin;.;C:\WINDOWS\Sun\Java\bin;C:\W
INDOWS\system32;C:\WINDOWS;C:\oracle\product\10.2.0\client_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
;C:\Program Files\ATI Technologies\ATI.ACE\
08:54:03,190 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
08:54:03,190 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:54:03,190 INFO [Catalina] Initialization processed in 187 ms
08:54:03,190 INFO [StandardService] Starting service jboss.web
08:54:03,190 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.CR1
08:54:03,237 INFO [Catalina] Server startup in 47 ms
--
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, 3 months
[JBoss JIRA] Created: (EJBTHREE-881) IsLocalInterceptor not detecting local container after failover
by Brian Stansberry (JIRA)
IsLocalInterceptor not detecting local container after failover
---------------------------------------------------------------
Key: EJBTHREE-881
URL: http://jira.jboss.com/jira/browse/EJBTHREE-881
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: EJB 3.0 RC9 - Patch 1
Reporter: Brian Stansberry
Some unit tests I've written are showing a problem with nested SFSBs where the IsLocalInterceptor doesn't treat a call from a parent SFSB to a nested SFSB as local, but Remoting optimizes it locally. This leads to an exception in the transaction propagation handling.
What's strange is for the call that fails AFAICT IsLocalInterceptor and AOPRemotingInvocationHandler are both dealing with Dispatcher using the same Invocation and the same metadata. But when IsLocalInterceptor queries Dispatcher, it says the container isn't registered, while when AOPRemotingInvocationHandler asks Dispatcher to handle the invocation, it finds the container just fine.
See forum thread for details.
--
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, 3 months
[JBoss JIRA] Created: (EJBTHREE-925) SFSB proxy creation process incorrectly routed locally
by Brian Stansberry (JIRA)
SFSB proxy creation process incorrectly routed locally
------------------------------------------------------
Key: EJBTHREE-925
URL: http://jira.jboss.com/jira/browse/EJBTHREE-925
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.0 CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 4.2.0 CR2
Say you have two completely unrelated SFSBs, Bean0 and Bean1, deployed on two different servers, node0 and node1. The only common point between Bean0 and Bean1 is they both are SFSBs bound in JNDI under "StatefulBeanRemote". Otherwise they are completely unrelated.
Client on node0 then contacts the JNDI server on node1 and does a lookup of "StatefulBeanRemote" expecting to get a proxy for Bean1. The SFSB proxy-creation process will end up being routed locally to the proxy factory for Bean0. Wrong!
Problem is this:
1) When client does an SFSB lookup, they don't directly download the SFSB proxy. Instead they download a proxy to the bean's ProxyFactory. That proxy then makes a remoting RPC back to the remote server to get the SFSB proxy. See o.j.ejb3.JndiProxyFactory.
2) The proxy to the remote ProxyFactory includes o.j.aspects.remoting.IsLocalnterceptor. That interceptor will bypass the remote call and invoke locally if the aop Dispatcher has a target registered with the same id as the target id associated with the call.
3) For calls made by the proxy to the remote ProxyFactory, the target id is the jndiName of the bean (plus a constant). So, if an unrelated target is registered locally with the same JNDI name, the call will incorrectly be routed to the local bean's proxy factory.
--
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, 3 months
[JBoss JIRA] Created: (JGRP-445) Digest not set on FlushHeader on suspect member during a flush
by Michael Newcomb (JIRA)
Digest not set on FlushHeader on suspect member during a flush
--------------------------------------------------------------
Key: JGRP-445
URL: http://jira.jboss.com/jira/browse/JGRP-445
Project: JGroups
Issue Type: Bug
Affects Versions: 2.5
Reporter: Michael Newcomb
Assigned To: Bela Ban
NullPointerException can occur in findVirtualSynchronyGaps() because the Digest is not always set on the FlushHeader.
The below fix works, but not sure of it's implications.
private void onSuspect(Address address)
{
...
if (flushOkCompleted)
{
Digest digest = (Digest)down_prot.down(new Event(Event.GET_DIGEST));
// ************* Patch ************
FlushHeader fh = new FlushHeader(FlushHeader.FLUSH_COMPLETED, viewID);
fh.addDigest(digest);
m.putHeader(getName(),fh);
// ************* Patch ************
// original
// m.putHeader(getName(), new FlushHeader(FlushHeader.FLUSH_COMPLETED, viewID));
down_prot.down(new Event(Event.MSG, m));
if (log.isDebugEnabled())
log.debug(localAddress + " sent FLUSH_COMPLETED message to " + flushCoordinator);
}
...
}
--
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, 3 months
[JBoss JIRA] Created: (JBAS-4250) Bug In remote jdbc adapter
by Fr?d?ric Blaser (JIRA)
Bug In remote jdbc adapter
--------------------------
Key: JBAS-4250
URL: http://jira.jboss.com/jira/browse/JBAS-4250
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows XP, Oracle 9i
Reporter: Fr?d?ric Blaser
Priority: Minor
I have found some bugs inside jboss when I access datasource remotly.
1. The code bellow throws NullPointerException when the blob field is empty. failed on org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService:553
Code:
Blob blob = resultSet.getBlob(column.name());
bytes = blob.getBytes(1, (int)blob.length());
2. The same code above does not return the contents of the blob when the blob is filled.
3. There is a failue on org.jboss.resource.adapter.jdbc.remote.SerializableInputStream:266
Correction should be Code:
return read(b, 0, b.length);
--
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, 3 months
