[JBoss JIRA] Created: (JBCACHE-1025) JBossCache mbean registration fails on WebSphere 6.1
by Jerry Gauthier (JIRA)
JBossCache mbean registration fails on WebSphere 6.1
----------------------------------------------------
Key: JBCACHE-1025
URL: http://jira.jboss.com/jira/browse/JBCACHE-1025
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1
Environment: WebSphere 6.1
Reporter: Jerry Gauthier
Assigned To: Jerry Gauthier
Fix For: 1.4.1.SP4
At least two customers have encountered the following problem when starting JBossCache on WebSphere 6.1.
When the cache is started and the cache's interceptor mbeans are registered, the registration fails with an InstanceAlreadyExistsException. This occurs even on initial startup and despite the fact that JBossCache only registers a name if it's not already registered.
A post to the ActiveMQ Forum at http://issues.apache.org/activemq/browse/SM-883 suggest that this problem occurs because WebSphere modifies the mbean's registration name during the registration process. Subsequent tests to determine if the mbean has been registered apparently fail unless the client uses the name generated by WebSphere. (This is unverified but seems plausible.)
Caused by: javax.management.InstanceAlreadyExistsException:jboss.cache:service=TreeCache-Group,cell=citgoNode01Cell,nod
e=citgoNode01,process=server1
at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
at com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469)
at org.jboss.cache.util.MBeanConfigurator.registerInterceptors(MBeanConfigurator.java:72)
at org.jboss.cache.TreeCache._createService(TreeCache.java:1428)
at org.jboss.cache.TreeCache.createService(TreeCache.java:1378)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
--
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] Closed: (JBAS-3325) Fix the handling of BindAddress and Host in org.jboss.web.WebService
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3325?page=all ]
Dimitris Andreadis closed JBAS-3325.
------------------------------------
Resolution: Done
Setting the Host was broken. Host and BindAddress were using the same backend InetAddress.
Now BindAddress and Host can be set independently.
They default to:
<attribute name="BindAddress">${jboss.bind.address}</attribute>
<!-- The address to use for the host portion of the RMI codebase URL -->
<attribute name="Host">${java.rmi.server.hostname}</attribute>
I've also removed all the dead code, added an extra Codebase attribute on the WebService mbean, and clarified/corrected the comments in conf/jboss-service.xml
> Fix the handling of BindAddress and Host in org.jboss.web.WebService
> --------------------------------------------------------------------
>
> Key: JBAS-3325
> URL: http://jira.jboss.com/jira/browse/JBAS-3325
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Other
> Affects Versions: JBossAS-4.0.4.GA
> Environment: JBoss 4.0.3.SP1
> $ java -version
> java version "1.4.2_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
> $ java -version
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
> Reporter: Robert Schroeder
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall mentions the parameter "java.rmi.server.hostname" to set if the external host name differs from the local host (e.g. server machine is behind a firewall)
> But org.jboss.web.WebService doesn'r recognize this parameter:
> String hostname = server.getBindAddress(); // this always returns something, at least "0.0.0.0"!
> // If not user specified hostname given, then try to determine what it should be
> if (hostname == null) //this branch is never executed!
> {
> // First look for the rmi server name
> try
> {
> hostname = System.getProperty("java.rmi.server.hostname"); // this parameter is not recognized as this branch is never executed
> }
> catch (SecurityException e)
> {
> // ignore, but don't be silent
> ThrowableHandler.addWarning(e);
> }
> // else use the localhost name
> if (hostname == null)
> {
> try
> {
> hostname = InetAddress.getLocalHost().getHostName();
> }
> catch (IOException e)
> {
> log.error("Failed to get localhost name; ignoring", e);
> }
> }
> if (hostname != null)
> {
> setHost(hostname);
> }
> }
> // Host must be set to continue (either by user or detection)
> String address = getHost();
> if (address == null)
> throw new MissingAttributeException("Host");
> // Set the rmi codebase if it is not already set
> String codebase = System.getProperty("java.rmi.server.codebase");
> if (codebase == null)
> {
> address = ServerConfigUtil.fixRemoteAddress(address);
> codebase = "http://" + address + ":" + getPort() + "/";
> System.setProperty("java.rmi.server.codebase", codebase);
> }
> log.info("Using RMI server codebase: " + codebase);
> So the resulting problem is that codebase contains an address which is not reachable from the other side of firewall because "java.rmi.server.hostname" is not recognized (same for "-Djava.rmi.server.useLocalHostname=false" )
> Example:
> JBoss started with parameter set "-Djava.rmi.server.hostname=as2.subdomain1.subdomain2.test.com"
> but (thanks to rmi logging) the proxy objects on client side have codebase set to "http://as2:<port>" and not to "http://as2.subdomain1.subdomain2.test.com:<port>" as expected.
> JBoss 4 runs on a linux machine
> hostname --> "as2"
> hostname -f --> "as2.subdomain1.subdomain2.test.com"
--
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] Updated: (JBAS-3325) Fix the handling of BindAddress and Host in org.jboss.web.WebService
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3325?page=all ]
Dimitris Andreadis updated JBAS-3325:
-------------------------------------
Summary: Fix the handling of BindAddress and Host in org.jboss.web.WebService (was: Remove old code)
Fix Version/s: JBossAS-4.2.0.GA
JBossAS-5.0.0.Beta3
(was: JBossAS-4.2.1.CR1)
> Fix the handling of BindAddress and Host in org.jboss.web.WebService
> --------------------------------------------------------------------
>
> Key: JBAS-3325
> URL: http://jira.jboss.com/jira/browse/JBAS-3325
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Other
> Affects Versions: JBossAS-4.0.4.GA
> Environment: JBoss 4.0.3.SP1
> $ java -version
> java version "1.4.2_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
> $ java -version
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
> Reporter: Robert Schroeder
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall mentions the parameter "java.rmi.server.hostname" to set if the external host name differs from the local host (e.g. server machine is behind a firewall)
> But org.jboss.web.WebService doesn'r recognize this parameter:
> String hostname = server.getBindAddress(); // this always returns something, at least "0.0.0.0"!
> // If not user specified hostname given, then try to determine what it should be
> if (hostname == null) //this branch is never executed!
> {
> // First look for the rmi server name
> try
> {
> hostname = System.getProperty("java.rmi.server.hostname"); // this parameter is not recognized as this branch is never executed
> }
> catch (SecurityException e)
> {
> // ignore, but don't be silent
> ThrowableHandler.addWarning(e);
> }
> // else use the localhost name
> if (hostname == null)
> {
> try
> {
> hostname = InetAddress.getLocalHost().getHostName();
> }
> catch (IOException e)
> {
> log.error("Failed to get localhost name; ignoring", e);
> }
> }
> if (hostname != null)
> {
> setHost(hostname);
> }
> }
> // Host must be set to continue (either by user or detection)
> String address = getHost();
> if (address == null)
> throw new MissingAttributeException("Host");
> // Set the rmi codebase if it is not already set
> String codebase = System.getProperty("java.rmi.server.codebase");
> if (codebase == null)
> {
> address = ServerConfigUtil.fixRemoteAddress(address);
> codebase = "http://" + address + ":" + getPort() + "/";
> System.setProperty("java.rmi.server.codebase", codebase);
> }
> log.info("Using RMI server codebase: " + codebase);
> So the resulting problem is that codebase contains an address which is not reachable from the other side of firewall because "java.rmi.server.hostname" is not recognized (same for "-Djava.rmi.server.useLocalHostname=false" )
> Example:
> JBoss started with parameter set "-Djava.rmi.server.hostname=as2.subdomain1.subdomain2.test.com"
> but (thanks to rmi logging) the proxy objects on client side have codebase set to "http://as2:<port>" and not to "http://as2.subdomain1.subdomain2.test.com:<port>" as expected.
> JBoss 4 runs on a linux machine
> hostname --> "as2"
> hostname -f --> "as2.subdomain1.subdomain2.test.com"
--
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-4351) url file:/opt/jboss/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist?
by Jon Stevens (JIRA)
url file:/opt/jboss/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist?
--------------------------------------------------------------------------------------------------------
Key: JBAS-4351
URL: http://jira.jboss.com/jira/browse/JBAS-4351
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-4.2.0.CR2
Reporter: Jon Stevens
Assigned To: Dimitris Andreadis
I'm getting this exception during startup... activation.jar is missing from that directory in the 4.2.0.CR2 release...
org.jboss.deployment.DeploymentException: url file:/opt/jboss/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)
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: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.GeneratedMethodAccessor3.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.GeneratedMethodAccessor9.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)
--
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: (JBPM-900) starting processes without start task
by Tom Baeyens (JIRA)
starting processes without start task
-------------------------------------
Key: JBPM-900
URL: http://jira.jboss.com/jira/browse/JBPM-900
Project: JBoss jBPM
Issue Type: Bug
Components: Web Interface
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
i created a process with a start state, two async nodes and an end state. after starting, the process should just run through until the end in 3 transactions.
when i clicked the 'Start Process' link in the processes page, I got following exception page:
"
HTTP Status 404 - /jbpm-console/main/process/started.jsf
type Status report
message /jbpm-console/main/process/started.jsf
description The requested resource (/jbpm-console/main/process/started.jsf) is not available.
Apache Tomcat/5.5.17
"
the server didn't report an exception.
--
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
