[JBoss JIRA] (AS7-1562) Ability to add custom java url protocol handler
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-1562?page=com.atlassian.jira.plugin.s... ]
David Lloyd closed AS7-1562.
----------------------------
Resolution: Rejected
This wasn't really a bug, more of a forum question.
> Ability to add custom java url protocol handler
> -----------------------------------------------
>
> Key: AS7-1562
> URL: https://issues.jboss.org/browse/AS7-1562
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Server
> Environment: JBoss EAP 5.1
> Reporter: Brad Maxwell
> Labels: URLStreamHandlerFactory, custom, handler, java, url
>
> Looking in the source code for org.jboss.system.server.ServerImpl [1]
> - this class is setting the URLStreamHandlerFactory and also calling preload and specifying the java.protocol.hanlder.pkgs.
> URL.setURLStreamHandlerFactory(new URLStreamHandlerFactory());
>
> // Preload JBoss URL handlers
> URLStreamHandlerFactory.preload()
> ...
> System.setProperty("java.protocol.handler.pkgs", handlerPkgs);
> So it looks like there isn't a way to change the URLStreamHandlerFactory that is used and the instance of URLStreamHandlerFactory created is not accessible to add new protocols.
> Is there anything I'm missing, it looks like this should be a feature, I've found a few posts on the net mentioning other app servers allow you to specify the Factory class to use.
> The exception is:
> java.net.MalformedURLException: unknown protocol: classpath
> [1] http://anonsvn.jboss.org/repos/jbossas/tags/JBPAPP_4_3_0_GA_CP08/system/s...
> [2] http://anonsvn.jboss.org/repos/common/common-core/tags/jboss-common-core-...
> [3] http://community.jboss.org/message/288238?tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3684) AS7.1 can't start on windows
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created AS7-3684:
----------------------------------------
Summary: AS7.1 can't start on windows
Key: AS7-3684
URL: https://issues.jboss.org/browse/AS7-3684
Project: Application Server 7
Issue Type: Bug
Components: Scripts
Affects Versions: 7.1.0.CR1b
Reporter: Max Rydahl Andersen
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 7.1.0.Final
>From Thomas Reinhardt on AS7-241:
Fails for 7.1.0 cr1b. OS is Windows 7 x64. Java 1.7.0_01_x64 and 1.6.0_26_x64 tested. Also tested in "C:\temp\JBoss 7", same result.
C:\Program Files (x86)\--bin--\jboss710-cr1b\bin>standalone.bat
Calling "C:\Program Files (x86)\--bin--\jboss710-cr1b\bin\standalone.conf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files (x86)\--bin--\jboss710-cr1b
JAVA: C:\java\jdk1.7.0_01_x64\bin\java
JAVA_OPTS: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterv
al=3600000 -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -server
===============================================================================
WARNING: No log manager service descriptor found in specified logmodule org.jboss.logmanager:main
WARNING: No mbeanserver service descriptor found in specified mbeanserverbuildermodule org.jboss.as.jmx:main
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:248)
at org.jboss.modules.Main.main(Main.java:313)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to
"org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more
Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3589) CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
by Serge Emmanuel Pagop (JIRA)
[ https://issues.jboss.org/browse/AS7-3589?page=com.atlassian.jira.plugin.s... ]
Serge Emmanuel Pagop commented on AS7-3589:
-------------------------------------------
Yes, for domain mode operation. But for standalone mode operation in a clustering env. the best strategy is to create a CLI script that deploys your application to all your server nodes
> CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3589
> URL: https://issues.jboss.org/browse/AS7-3589
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.0.CR1b
> Environment: RHEL 6, JBoss EAP 6 DR12
> Reporter: Serge Emmanuel Pagop
> Assignee: Paul Ferraro
> Fix For: 7.1.0.Final
>
>
> I create multiple IP Addresses on a single NIC for this use case.
> Use-Case: Clustering in Standalone mode with 2 nodes installed in different Datacenter
> Action: deployment of a distributable web application in the node 1 from datacenter 1
> Expectation: consequence should be also the deployment of the distributable application in the running node2 from datacenter 2
> Result: no deployment of application in the running node2 from datacenter2
> Info: find the web application example as attach
> All the steps:
> 1) from datacenter 1
> + Start node1 in Standalone mode from datacenter with IP 192.168.178.31
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.31 -bmanagement=192.168.178.31 -Djboss.node.name=node1
> 2)from datacenter 2
> + Start node2 in standalone mode from datacenter with IP 192.168.178.32
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.32 -bmanagement=192.168.178.32 -Djboss.node.name=node2
> 3)from datacenter 1
> + deploy a distributable application in the running standalone node1 - copy the application into the directory $EAP6_HOME/standalone/deployments
> during the deployment server log shows this infos:
> - Start Server log infos
> 22:26:28,506 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "version3.war"
> 22:26:29,285 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.DatagramSocket@40993028 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.DatagramSocket@40993028 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.MulticastSocket@928b33a was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,288 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.MulticastSocket@928b33a was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,303 INFO [stdout] (MSC service thread 1-1)
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) GMS: address=node1/web, cluster=web, physical address=192.168.178.31:55200
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:31,359 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-4) JBAS010207: Number of cluster members: 1
> 22:26:31,781 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
> 22:26:31,971 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups Channel
> 22:26:31,972 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-4) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@6b7fb9d5) but now it is being overridden
> 22:26:31,972 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view: [node1/web|0] [node1/web]
> 22:26:31,973 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Cache local address is node1/web, physical addresses are [192.168.178.31:55200]
> 22:26:31,976 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1
> 22:26:32,077 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,145 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010301: Started registry cache from web container
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010301: Started repl cache from web container
> 22:26:32,347 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /version3
> 22:26:32,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "version3.war"
> - End Server log infos
> 4) From datacenter 2
> No action deployment in node2
> - Start Server log info
> ...
> 22:25:36,179 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /192.168.178.32:9999
> 22:25:36,233 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /NotBackedUp/spagop/EAP6_TRAINING/my-labs/clustering/standalone-lab/node2/jboss-eap-6.0/standalone/deployments
> 22:25:36,986 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 8096ms - Started 152 of 259 services (102 services are passive or on-demand)
> - End Server log info
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3161) FileCacheStore ISPN000064: Problems creating the directory
by Radoslav Husar (Created) (JIRA)
FileCacheStore ISPN000064: Problems creating the directory
----------------------------------------------------------
Key: AS7-3161
URL: https://issues.jboss.org/browse/AS7-3161
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.0.Final
while AS7 logs
{noformat}
[JBossINF] 05:03:55,074 WARN [org.infinispan.loaders.file.FileCacheStore] (MSC service thread 1-7) ISPN000064: Problems creating the directory: /tmp/hudson/jboss-as-7.1.0.Final-SNAPSHOT/standalone/data/repl/repl
{noformat}
the directory has been created in the end (at different time so it looks)
{noformat}
[rhusar@perf20 repl]$ ll /tmp/hudson/jboss-as-7.1.0.Final-SNAPSHOT/standalone/data/repl/repl
total 12
drwxrwxr-x. 3 hudson hudson 4096 Jan 3 05:17 org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB
drwxrwxr-x. 3 hudson hudson 4096 Jan 3 05:17 org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl
drwxrwxr-x. 2 hudson hudson 4096 Jan 3 05:17 repl
{noformat}
any thoughts why this is?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3589) CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3589?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry resolved AS7-3589.
-----------------------------------
Fix Version/s: 7.1.0.Final
(was: 7.1.1.Final)
Resolution: Rejected
> CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3589
> URL: https://issues.jboss.org/browse/AS7-3589
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.0.CR1b
> Environment: RHEL 6, JBoss EAP 6 DR12
> Reporter: Serge Emmanuel Pagop
> Assignee: Paul Ferraro
> Fix For: 7.1.0.Final
>
>
> I create multiple IP Addresses on a single NIC for this use case.
> Use-Case: Clustering in Standalone mode with 2 nodes installed in different Datacenter
> Action: deployment of a distributable web application in the node 1 from datacenter 1
> Expectation: consequence should be also the deployment of the distributable application in the running node2 from datacenter 2
> Result: no deployment of application in the running node2 from datacenter2
> Info: find the web application example as attach
> All the steps:
> 1) from datacenter 1
> + Start node1 in Standalone mode from datacenter with IP 192.168.178.31
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.31 -bmanagement=192.168.178.31 -Djboss.node.name=node1
> 2)from datacenter 2
> + Start node2 in standalone mode from datacenter with IP 192.168.178.32
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.32 -bmanagement=192.168.178.32 -Djboss.node.name=node2
> 3)from datacenter 1
> + deploy a distributable application in the running standalone node1 - copy the application into the directory $EAP6_HOME/standalone/deployments
> during the deployment server log shows this infos:
> - Start Server log infos
> 22:26:28,506 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "version3.war"
> 22:26:29,285 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.DatagramSocket@40993028 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.DatagramSocket@40993028 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.MulticastSocket@928b33a was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,288 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.MulticastSocket@928b33a was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,303 INFO [stdout] (MSC service thread 1-1)
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) GMS: address=node1/web, cluster=web, physical address=192.168.178.31:55200
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:31,359 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-4) JBAS010207: Number of cluster members: 1
> 22:26:31,781 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
> 22:26:31,971 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups Channel
> 22:26:31,972 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-4) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@6b7fb9d5) but now it is being overridden
> 22:26:31,972 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view: [node1/web|0] [node1/web]
> 22:26:31,973 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Cache local address is node1/web, physical addresses are [192.168.178.31:55200]
> 22:26:31,976 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1
> 22:26:32,077 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,145 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010301: Started registry cache from web container
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010301: Started repl cache from web container
> 22:26:32,347 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /version3
> 22:26:32,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "version3.war"
> - End Server log infos
> 4) From datacenter 2
> No action deployment in node2
> - Start Server log info
> ...
> 22:25:36,179 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /192.168.178.32:9999
> 22:25:36,233 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /NotBackedUp/spagop/EAP6_TRAINING/my-labs/clustering/standalone-lab/node2/jboss-eap-6.0/standalone/deployments
> 22:25:36,986 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 8096ms - Started 152 of 259 services (102 services are passive or on-demand)
> - End Server log info
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months